New Blog!
There is lots of RFC1918 space out there, yet most people use the same 10 /24 subnets
I ended up having my OOB LAN collide with someones home network a few weeks ago, and decided to find a new subnet to use that won't collide backed up with actual usage data!
Picking uncontested private IP subnets with usage data
https://blog.benjojo.co.uk/post/picking-unused-rfc1918-ip-space
@benjojo Loved the blog! I like that you had some data. I picked a 10.random.random.0/24 LAN a while ago, to avoid collisions, but then thought "Is this a tracking vector somehow?" (My local IP would be unique if it leaked) so I renumbered back to 192.168.1.0/24 to blend in with the normies!
Also I blogged about my internal subnet experience from 10 years of corporate life (pre-cloud!)
https://blog.amen6.com/blog/2024/04/internal-network-numbering-the-good-the-bad-and-the-ugly/
Introduction The Good The (Mundane) Bad The (Creative) Bad - IP Squatting The Ugly - Being Too Clever Postscript - What About IPv6? Introduction This is kind of a #storytime post, but also not. It’s a retrospective of the Good, the Bad, and the Ugly choices I’ve seen over my twenty years of work, in regards to how companies choose to use and abuse their internal network numbering. It should be fairly simple, but it’s one of those choices that can come back to bite you if you choose wrong (even if you do follow RFC 1918).
benjojo
MacKenzie