Title: [PULL] IPv6 support Post by: Pieter Wuille on July 24, 2011, 03:18:29 PM See https://github.com/bitcoin/bitcoin/pull/427 (https://github.com/bitcoin/bitcoin/pull/427)
General changes (even when IPv6 support is not compiled in):
Behaviour changes when IPv6 support is enabled:
For internal changes, see the commit message. Title: Re: [PULL] IPv6 support Post by: kokjo on July 24, 2011, 04:25:17 PM Quote The rule that no two connections to addresses within the same /16 should be attempted, was generalized by defining address groups: that just sucks, sorry. i can see why, but it still sucks.IPv4 addresses are grouped in /16 blocks IPv6 addresses are grouped in /32 blocks Quote A local IPv6 address is used instead of an IPv4 one if no routable IPv4 address is available. In this case, it is not advertized through IRC (obsolete). how the hell are nodes going to find each other then? just asking, im trying to make an alternative client.the way im finding nodes now are connecting to the official client at 127.0.0.1:8333 , and send a getaddr. overall: good work! :D Title: Re: [PULL] IPv6 support Post by: Pieter Wuille on July 24, 2011, 04:33:24 PM Quote The rule that no two connections to addresses within the same /16 should be attempted, was generalized by defining address groups: that just sucks, sorry. i can see why, but it still sucks.IPv4 addresses are grouped in /16 blocks IPv6 addresses are grouped in /32 blocks Quote Quote A local IPv6 address is used instead of an IPv4 one if no routable IPv4 address is available. In this case, it is not advertized through IRC (obsolete). how the hell are nodes going to find each other then? just asking, im trying to make an alternative client.the way im finding nodes now are connecting to the official client at 127.0.0.1:8333 , and send a getaddr. Such nodes will still get IPv4 nodes from IRC, and connect to those. It will also advertize its own IPv6 address on the network, which will hopefully propagate that address (current clients don't). Eventually, its address will hopefully end up in DNS seeds, where it can be found by all IPv6-capable nodes. Title: Re: [PULL] IPv6 support Post by: error on July 24, 2011, 07:35:17 PM Quote The rule that no two connections to addresses within the same /16 should be attempted, was generalized by defining address groups: that just sucks, sorry. i can see why, but it still sucks.IPv4 addresses are grouped in /16 blocks IPv6 addresses are grouped in /32 blocks Wait, somebody got an IPv6 /16 block?! That sounds like a monstrous waste of address space. Didn't they learn anything from how fast the IPv4 addresses ran out? Title: Re: [PULL] IPv6 support Post by: kokjo on July 24, 2011, 07:39:44 PM Quote The rule that no two connections to addresses within the same /16 should be attempted, was generalized by defining address groups: that just sucks, sorry. i can see why, but it still sucks.IPv4 addresses are grouped in /16 blocks IPv6 addresses are grouped in /32 blocks Wait, somebody got an IPv6 /16 block?! That sounds like a monstrous waste of address space. Didn't they learn anything from how fast the IPv4 addresses ran out? |