Skip to content

Improve IPv6 auto-ENR #8808

@yorickdowne

Description

@yorickdowne

Problem description

Currently, on a dual-stack host, Lodestar will auto discover its public IPv4, but not its public IPv6. This is troublesome for home stakers behind CGNAT

Solution description

The good news is that "the network" should be ready now, with sufficient IPv6 nodes. Lodestar may just need a small tweak to its logic.

I say this because both Lighthouse and Grandine are working with auto-ENR on dual-stack, populating both their IPv4 and IPv6 public IPs in discovery_addresses, when looking at eth/v1/node/identity

Maybe their strategy can inform Lodestar's

so from last time I looked at this, the problem was that if the node is reachable via IPv4 then other nodes will just "pong" us on that interface and not on IPv6 which means we do not reach the minimum threshold requires to discover the external IP, right now it's 10

I believe this problem would also resolve itself if there are more IPv6 only nodes on the network

Maybe. We are not likely to see a lot of v6-only nodes any time soon, though. I am hopeful bcs of Lighthouse and Grandine working well with dual-stack

Additional context

Let me know what I can get you, e.g. trace logs

Metadata

Metadata

Assignees

No one assigned

    Labels

    meta-feature-requestIssues to track feature requests.scope-networkingAll issues related to networking, gossip, and libp2p.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions