On all my servers running bitcoin core, I see that all IPv6 addresses are "network is unreachable", and I'm not sure how to fix this - is there a bug, or is this there some documentation that could be included on how to set up IPv6?
-
rebroad commented at 3:22 AM on August 9, 2016: contributor
-
ghost commented at 12:48 PM on August 9, 2016: none
If you're sure that you have ipv6 connection, you can force IPv6 using
-bind [host]:port. - jonasschnelli added the label P2P on Aug 9, 2016
-
rebroad commented at 11:43 PM on August 14, 2016: contributor
Can't my node determine whether I have ipv6 by testing some ipv6 addresses that it knows will be up and if it doesn't have ipv6 then it shouldn't even be wasting time trying to connect to them.
-
pstratem commented at 3:23 AM on August 15, 2016: contributor
The best way to discover whether an address is reachable is to simply try.
Other mechanisms tend to return false negatives.
On Aug 14, 2016 4:43 PM, "R E Broadley" notifications@github.com wrote:
Can't my node determine whether I have ipv6 by testing some ipv6 addresses that it knows will be up and if it doesn't have ipv6 then it shouldn't even be wasting time trying to connect to them.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub #8491 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AAl4Q-0nYmM_PYRXDUVmt2GwklP4eNSYks5qf6g0gaJpZM4Jfrga .
-
rebroad commented at 6:51 AM on September 1, 2016: contributor
@pstratem I agree with that statement. My suggestion is that if a type of address (e.g. IPv6, Onion) always comes back as unreachable (not connection refused), then would it not be apt to recognise that it is the network type that is unsupported rather than it simply being a coincidence. I.e. the node can learn which network types are working and therefore cease attempts to connect to network types currently unavailable.
-
rebroad commented at 11:30 PM on September 15, 2016: contributor
I'll explain further why I think this is an issue. Currently more than 99% of addresses advertised are unreachable and I foresee that we need to add better logic for pruning these unreachable addresses. I have various ideas in mind, but once this code is added then this would cause addressed from whole networks to be lost between nodes due to them not being able to determine that the node itself is not connected to the network (e.g. IPv6). The node therefore needs to be able to distinguish between whether the node it's trying to connect to is down, or whether it's unable to connect to all types of that address.
-
pinheadmz commented at 4:51 AM on April 26, 2017: member
I'm getting a log full of
Network is unreachablefor ipv6 addresses, as well. It would be nice if there was a-noipv6option. -
sipa commented at 5:14 AM on April 26, 2017: member
@pinheadmz Try
-onlynet=ipv4. -
MarcoFalke commented at 12:25 AM on April 27, 2020: member
Is this still an issue with a recent version of Bitcoin Core? If yes, what are the steps to reproduce?
- MarcoFalke closed this on Apr 27, 2020
- DrahtBot locked this on Feb 15, 2022
