4 ms·
What the given article does not address is when to choose 10.x.x.x, 172.x.x.x and 192.168.x.x and why it's important to choose the right one. Here is the presc
by garganzol 8y ago
What the given article does not address is when to choose 10.x.x.x, 172.x.x.x and 192.168.x.x and why it's important to choose the right one.
Here is the prescribed solution:
- Use 10.x.x.x for office/enterprise LANs
- Use 192.168.x.x for home LANs
- Use 172.x.x.x for supplementary services like guest networks, DMZ etc
Why so? The reason is VPN.
When you connect to office VPN from home, you connect from 192.168.x.x to 10.x.x.x. This makes it very easy for routers to avoid address range clashes.
If you break that rule then you may end up with a weird situation when you connect from a home network 10.0.1.1/24 to an office network 10.0.1.1/24. Good luck trying to connect to that specific 10.0.1.12 machine: there is no easy way to determine where the packet should be routed.
- deleted 8y ago[deleted]
- keshav_ 8y agowhat if I have two homes?
- forapurpose 8y agoOr if you are visiting someone else, you're in a cafe, a hotel ...
- limeyx 8y agoOr your home is in a hotel but you walk down to the cafe ... should you renumber ?
- forapurpose 8y agoHmmm ... it's easy to avoid clashes by choosing somewhat unique addressing schemes in those ranges. For example, the 10. private network allows 255 different addressing schemes if you use a 16 bit subnet mask (10.0/16, 10.1/16, 10.2/16 .. 10.254/16), and ~64,000 schemes with an 24 bit subnet mask (10.0.0/24, 10.0.1/24, 10.0.2/24 .. 10.254.254/24). Just don't choose the common ones: 10.0/16, 10.0.0/24, 192.168/16, 192.168.0/24, etc.