get_enode_for_node returns incorrect ip for reth nodes
corduroybera opened this issue · comments
When using get_enode_for_node it's largely to get the bootnode addresses. However, when calling admin_nodeInfo in reth, it doesn't apply the extip that was set via the --nat flag. Instead, the returned address is always of the format enode://[hash]@127.0.0.1:30303
This means when running a reth-only network you end up with no peering because the bootnode IPs do not reference the proper private IPs in the enclave.
Good catch, however, I think this might be a reth bug, rather than a kurtosis bug.
@barnabasbusa yeah, I was wondering that. Wasn't sure if there was a spec definition for what IP it should return there.
Fixed: paradigmxyz/reth#7181
ethpandaops/reth:main-0a803c4 or newer.