Pete Keen
@mdavis I picked a /24 in 10.0.0.0/8 that I figured would be unique enough, and so far it has been. I'm much more on the #ipv6 train these days though.
Feb 14 at 2:25amWeb
Show threadHugo Slabbert ⚠️Feb 14

@zrail yep. I decided to start at 10.128/16. Figured that avoids even common conflicts in the lower half of 10/8 and gives me plenty of options.

v6 makes it so I just never have to worry.

Show threadsubnetspiderFeb 14
@zrail @mdavis Ah yes. IPv6, the 25 year old solution to a 40 year old problem. 😁
Show threadPete KeenFeb 14
@subnetspider it's true, but also it pretty much just works now, at least for dual stack. I haven't pushed my v6-mostly experiment forward for a few weeks but I think that's my next project.
Show threadJdeBPFeb 14

@zrail

Yes. After doing it once one always has the lurking suspicion that one day one will come up against the LAN of someone else who has had the very same idea — whose birthday, or lucky numbers, or CRC16, or whatever just happen to make the same octets in the network part.

Then there are things like having an ISP that uses various parts of 10.0/8 for its internal infrastructure. Even my own ISP uses 192.168.100.0/24 for its own purposes on customer-premises equipment.

@mdavis
#RFC1918 #IPv6 #IPv4 #SiteLocalAddresses #PrivateUseAddresses #LANs #NetworkAdministration