You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although Core's IP schema seems to support IPv6 addresses as well as IPv4 addresses, in practice it doesn't work because Core considers most IPv6 addresses to be part of the same subnet (specifically :: which is wrong often :: but not always) so you theoretically cannot add much more than 5 IPv6 nodes to any network.
However, it all breaks down totally because to connect to IPv6 sockets you have to enclose the address in square brackets, but Core does not do this. So to recap, although the schema supports IPv6, Core cannot successfully connect to IPv6 addresses, and even if it could, it uses a faulty CIDR check that does not process IPv6 addresses properly.
This affects both Core 2.7 and 3.0 and although I don't expect this to be fixed in 2.7, I hope it will be addressed in 3.0.
The text was updated successfully, but these errors were encountered:
Although Core's IP schema seems to support IPv6 addresses as well as IPv4 addresses, in practice it doesn't work because Core considers most IPv6 addresses to be part of the same subnet (
specificallyoften::
which is wrong::
but not always) so you theoretically cannot add much more than 5 IPv6 nodes to any network.However, it all breaks down totally because to connect to IPv6 sockets you have to enclose the address in square brackets, but Core does not do this. So to recap, although the schema supports IPv6, Core cannot successfully connect to IPv6 addresses, and even if it could, it uses a faulty CIDR check that does not process IPv6 addresses properly.
This affects both Core 2.7 and 3.0 and although I don't expect this to be fixed in 2.7, I hope it will be addressed in 3.0.
The text was updated successfully, but these errors were encountered: