[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [OT] IP address collisions (was: Accessing a host with variable IP addresses / connection types)



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Nicholas Geovanis wrote:
> On Thu, Apr 18, 2019 at 7:57 AM Michael Stone <mstone@debian.org> wrote:
>
>>
>> No, the ULA is the IPv6 equivalent of RFC1918 space--you can use it
>> internally without central registration by choosing a subnet from
>> fd00::/8. The space is so much larger that it's much less likely that
>> two sites would pick the same prefix, but there are no guarantees.
>>
> But isn't it irrelevant whether they pick the same prefix or not? Routers
> that respect ULA and RFC1918 shouldn't route any traffic destined to them
> off the logical subnet. Right?

No.  RFC1918 / ULA are merely "unroutable on The Internet" (as in, they
cannot be directly accessed from the public internet).  You can freely
route between them on "private" networks to your heart's content.

For example, I have the RFC1918 subnets

 - 192.168.1.0/24, .2.0/24, .10.0/24, and .20.0/24  (LAN networks)
 - 10.90.0.0/16 (VPN[1])

[1] way overkill, but lets me move around a bit in case a hotel is using
part of that range. (I only have the server hand out a /24 out of that
range, but the LAN's routing table uses the full /16).

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAly4kEMACgkQjhHd8xJ5
ooEtPwgAkNULTlTgrX/BBf05jekTkQdINI8Q9CxO+ghG+a9cxOZJWszq9nZmz5QX
aTmy7bHGFA9hYyTb9Ty5+uDDhVLLOvsFY7GaDDLQv+NM+mHWmBlerd+tbMj8k64I
mT3jCxXHdDm23eoCHfNdZpOP1Yv9UBbRcbhjCOt/e4paMx1vde3ZQ71cISjnBsQQ
+GaE2vqtL5hfvss9BOpfoWqpR5PVexVuRg8TtFt/1cgYe5TjawBsgl2ZVYHR+CqS
m1C4uX09RiJnro15JH5NwI1sHwu/ssrTvYAN+Lpx93ybOeSk7gRaaFqCPrTl7Y2T
/Mjie8A6RfSd+Gi7QeaV+br5ttkbhw==
=K64f
-----END PGP SIGNATURE-----

-- 
|_|O|_| 
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281


Reply to: