6 ms·
Why would you do that though when there are perfectly fine internal address ranges available?
by Havoc 6y ago
Why would you do that though when there are perfectly fine internal address ranges available?
- Godel_unicode 6y agoI suspect there are a decent number of network engineers who think it's funny to use DoD IPs for their internal network, especially given what their logging system will probably tell them by default. If you drive around with a WiFi stumbler running, you'll run into networks with names like "UTAH DATA CENTER" and "SIPRnet", etc for the same reason.
- imwillofficial 6y agoI always hated seeing “FBI Surveillance Van” Made me wanna climb out of my FBI Surveillance Van and have a word with them.
- leesalminen 6y agoHa! “Unmarked white van” is the WiFi name at my local dog daycare. I got a good laugh.
- dwarfsandstuff 6y agoMy wifi is called nsa_net
- ta988 6y agoNow I know who you are.
- Flocular 6y agoYeah, sharing SSIDs isnt such a great idea. Check out https://wigle.net https://wigle.net ... Obviously multiple people around the world use this one, but it narrows it down for dedicated people
- deleted 6y ago[deleted]
- swader999 6y agoMine is your_wife_is_hot.
- imwillofficial 6y agoI have a wife?!? When did this happen?!
- XorNot 6y agoThe main reason (I've done this at a bank previously) is when you need to ensure you don't overlap with other internal IP (RFC1918 was represented everywhere and routeable internally) and when you're trying to dodge 99% of your engineer's default Docker configs to reduce support request load. In that case there's never any chance it'll be needed by people using the public internet there, and never any chance it'll be used suddenly by a deployed internal service somewhere else from an outside vendor.
- trulyme 6y agoDefault Docker configs are atrocious. Most devs/devops don't even know that when it creates a network, it takes a /16 ip range out of 172.[17-31].0.0/16 or 192.168.[0-240].20/20 by default. It is just a matter of time before a restart makes it collide with an existing network range. It does skip networks defined on local interfaces at least, but this only means that devs don't learn about this landmine on their own machines, nuking production instead. The default should reserve a single ip range and simply fail (with a nice message) if more are needed.
- Denvercoder9 6y agoTwo things that come to mind are running out of private address space (a /8 isn't that large), or wanting address space that doesn't clash with other private networks (e.g. to ensure a VPN doesn't overlap with home networks). There's probably more reasons.
- VLM 6y ago> running out of private address space Classic merger "solution". Company A uses 10/8 Company B uses 10/8, company A buys company B and orders new subsidiary B to renumber into 11/8 "All you have to do is change every first octet to 11"
- woleium 6y agoor, you know, use NAT to do so :)
- kenniskrag 6y agoor upgrade to ipv6 :)
- ratsmack 6y agoor maybe ask the question regarding why we're not all running ipv6.
- kenniskrag 6y agowhy?
- deleted 6y ago[deleted]
- twic 6y agoIn our case, we were setting up VPN tunnels to a partner, who for some reason required that the addresses on our side should (appear to be) public IP addresses. So we couldn't use 10/8 or 192.168/16 in (that part of) our network. They didn't actually need the addresses to be routable from the public internet (that was the whole point of the VPN). I think the requirement was really a way of making sure they were unique. I'm sure they had several partners who used 10/8 internally.
- GekkePrutser 6y agoThere's also 172.16/12 :) But yeah I agree. If you're running a VPN for a large company it's kinda hard to avoid such conflicts. In my work we use 10.0.0.0/8 but of course some people use the same at home even though 192.168/16 is way more common. In general I find 172.16/12 the least common in the field.
- jamiek88 6y agoI know the old Apple extreme and time machine routers used to default to 10 rather than 192 ever since then I’ve kept my internal routing within that block. It just looks nicer to me which shows the power of Apple and how easily I am influenced.
- simondotau 6y agoI personally use a range towards the end of the 172.16/12 reservation for my home network for exactly this reason. Ever since I made the change five years ago I’ve never suffered any conflicts when running a VPN in or out.
- bombcar 6y agoVirtually nobody realizes 172.17-172.31 are available. And many are surprised to find that there are 172.* that are routable.
- bombcar 6y agoA trick is to use something in the 10 range but not /8 - 10.185.203/24 will work on a 10/8 network (assuming no actual host overlap) as it’s more specific and will route first. Still gives you fun issues though.
- mrkstu 6y agoIn the case of a managed service provider I worked for, using non-announced gov/mil space allowed us to inject routes for monitoring purposes into the MPLS vrfs of our customers so we could poll the routers without using our own public space.
- Taniwha 6y agoIn my case I got a class C around about 1992 (back then that was the only way to get on the internet), at some point the ISP above my ISP claimed it as theirs without telling me .... I still use it internally why should I change?
- icedchai 6y agoIs it "directly assigned" to you in whois? I got mine around 1993.