On a Google Cloud node, listening on an IPv6 address triggers a lot of listener errors

[tomaka]

When listening for example on /ip6/::/tcp/30333, there seems to be a periodic ListenerError whose message is something like:

::ffff:10.128.0.9 does not match any listen address

rust-libp2p/transports/tcp/src/lib.rs

Line 469 in bbed28b

let msg = format!("{} does not match any listen address", socket_addr.ip());

This only happens on my Google Cloud node, and not on my local machine.

[tomaka]

I logged the output of calling the host_addresses function:

2020-04-20 08:54:53.207 tokio-runtime-worker DEBUG libp2p_tcp  host_addresses = [(V4(127.0.0.1), 127.0.0.1/8, "/ip4/127.0.0.1/tcp/30333"), (V4(10.128.0.9), 10.128.0.9/32, "/ip4/10.128.0.9/tcp/30333"), (V4(172.17.0.1), 172.17.0.1/16, "/ip4/172.17.0.1/tcp/30333"), (V6(::1), ::1/128, "/ip6/::1/tcp/30333")]
... (unrelevant logs here) ...
2020-04-20 08:54:55.611 tokio-runtime-worker DEBUG libp2p_tcp  host_addresses = [(V4(127.0.0.1), 127.0.0.1/8, "/ip4/127.0.0.1/tcp/30333"), (V4(10.128.0.9), 10.128.0.9/32, "/ip4/10.128.0.9/tcp/30333"), (V4(172.17.0.1), 172.17.0.1/16, "/ip4/172.17.0.1/tcp/30333"), (V6(::1), ::1/128, "/ip6/::1/tcp/30333")]
2020-04-20 08:54:55.611 tokio-runtime-worker ERROR sub-libp2p  Error on libp2p listener ListenerId(1): ::ffff:10.128.0.9 does not match any listen address

The problem just seems to be that V4(10.128.0.9) doesn't compare equal to IpV6Addr(::ffff:10.128.0.9), but there might be a smarter way to fix that than adding a custom equality function.

[twittner]

#1555 separates IPv4 and IPv6 listeners, so this mixed comparison should not happen anymore.