IPv6 support: discovery and listeners bind IPv4 only

Aberta
#853 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 6 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
18/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
rust
Domínio
networking

Direção de pesquisa

Start in bin/ethlambda/src/main.rs: run_node builds p2p_socket on 0.0.0.0, and build_swarm listens on /ip4/0.0.0.0 for QUIC/TCP; spawn_discovery hands one UDP socket to ethrex. Read read_ip and Options::validate_ports for ENR and flag handling, plus #825 for the bootnode refusal. Done means IPv6 listeners/discovery (or a documented ethrex dependency), ip6/udp6/tcp6/quic6 read and written, CLI flags validated, and tests covering dual-stack and IPv6-only peers.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Problem

The node binds IPv4 sockets only, so IPv6 works only for outbound connections:

  • Discovery (discv5) is IPv4-only. run_node builds p2p_socket on 0.0.0.0 (bin/ethlambda/src/main.rs) and passes its IP as DiscoverySpawnConfig::bind_ip. spawn_discovery opens one UdpSocket there and hands it to ethrex's DiscoveryServer. An IPv4 socket cannot send to an IPv6 address or receive from one, so discv5 never reaches an IPv6-only peer, whether it was found by discovery or given as a bootnode.
  • The swarm listens on IPv4 only. build_swarm listens on /ip4/0.0.0.0 for QUIC and TCP, so no peer can connect in over IPv6. Outbound dials to IPv6 do work: libp2p-quic opens a [::]:0 dialer endpoint when no IPv6 listener exists, and TCP opens a socket of the target's family.
  • --discovery.advertise-ip accepts an IPv6 address. It writes ip6 into the ENR, but the sockets behind the record are IPv4, so the published record is one no peer can reach.
  • ENRs from peers. read_ip prefers ip over ip6, and the IPv6-specific ports (udp6, tcp6, quic6) are never read or written.

Today this matters only for IPv6-only peers. A dual-stack record carries ip, which wins.

What support would take

Lighthouse runs dual-stack: --listen-address can be given once per family, the IPv6 ports have their own flags (--port6, --discovery-port6, --quic-port6), and discv5 gets one socket per family. Covering that here means:

  1. Discovery on IPv6 too. ethrex's DiscoveryServer takes a single socket, so this needs either a dual-stack socket with IPv4-mapped addresses handled throughout, or ethrex accepting a second socket.
  2. QUIC and TCP listeners on :: as well as 0.0.0.0.
  3. The ENR's ip6/udp6/tcp6/quic6 entries, written for our record and read from peers'.
  4. CLI flags for the IPv6 listen address and ports, and Options::validate_ports rules for them.
  5. Refusing an IPv6 --discovery.advertise-ip until the above exists, or warning that the record is unreachable.

Related

#825 (open) makes beacon --bootnodes refuse an IPv6 entry that is only a discv5 contact (a bare /ip6/.../udp/<port> multiaddr, or an ENR whose only address is ip6 and whose only port is udp) when discovery is bound to IPv4. The caller passes in the bind address, so the refusal lifts on its own once discovery binds IPv6.

Linguagem predominante
Rust
Estrelas
86
Forks
34
Merge médio
9d 20h
PRs com merge (30d)
77

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de lambdaclass/ethlambda

Todas as issues de lambdaclass/ethlambda

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.