Dual-stack adds tcp to discovery-addresses, does not list ip4

[yorickdowne]

Describe the bug

Configure Lodestar for dual-stack v4/6. The eth/v1/node/identity route shows discovery_addresses correctly containing an ip6 udp port, but also the ip6 tcp port. The ip4 udp port is missing.

Expected behavior

discovery_addresses lists the ip4 and ip6 udp port. Afaik discovery is strictly udp in p2p, and all transport is tcp

Steps to reproduce

Run Lodestar on a dual-stack host with --listenAddress 0.0.0.0 --port ${CL_P2P_PORT:-9000} --listenAddress6 :: --port6 ${CL_IPV6_P2P_PORT:-9090} --enr.ip6 ${__public_v6}

Additional context

"discovery_addresses":["/ip6/2001:1234:5678:9abc::/tcp/9090","/ip6/2001:1234:5678:9abc::/udp/9090"] (actual ip6 redacted)

Operating system

Linux

Lodestar version or commit hash

v1.22.0/c26cc63

[wemeetagain]

Thanks for reporting this, will take a look

[nflaig]

• Unused p2p_addresses & missing ipv6 address in disvoery_addresses in identity fields #6532 might be related