Anton Aylward wrote:
James Knott said the following on 09/10/2010 09:37 PM:
Per Jessen wrote:
I can't personally blame NAT for that - the range of RFC1918 address is so vast that the risk of a clash is minimal - unless you choose to use a commonly used range. My VPN runs on 10.221.78.0/22.
Choose whatever you want, you cannot guarantee someone else won't choose it.
Indeed. And that's why they have the randomization algorithm for choosing an address range for the local addresses in IPv6. Implicit in that is the assumption that people _will_ do something like NAT and try to connect from one unroutable range to another unroutable range via a mechanism that may or may not be called NAT.
The problem is the subnet address, not the individual computer. With IPv6, you can use the mac address to form part of the IPv6 address, use a random address, configure one manually or DHCP. With RFC1918, there are only so many subnet ranges to chose from.
If course there's nothing forcing people to use that randomization algorithm and even if they do, despite the expanded range, there's still the possibility of a clash, given a large enough population and enough time.
Actually, the IPv6 random address generators have a method to check for that, but of course it only applies on the local lan.
Chose whatever you want - however you want, you cannot guarantee someone else won't choose it.
Get a globally unique IPv6 address (and there's an incredibly high number of those) and you'll never have to worry about that. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org