What Subnet Do You Use At Home?

Which subnet do you use on your home networl?


  • Total voters
    102

/usr/home

Supreme [H]ardness
Joined
Mar 18, 2008
Messages
6,160
I'm curious since I'm changing my home subnet to a 10.10.10.0 /24 range due to having some issues when using the VPN on clients that had the same old subnet as me (192.168.1.0 /24) Curious as to which subnet you guys use. and why.
 
I use 192.168.0.x. Why? Well, because that's just what the tutorial used when I first started learning about how to setup a LAN with TCP/IP. It just sort of stuck with me since then, even though most routers out of the box come configured to use 192.168.1.1, I'll still go through the hassle of changing them over to use 192.168.0.1 because it just looks "right" to me.
 
I use 192.168.0.x. Why? Well, because that's just what the tutorial used when I first started learning about how to setup a LAN with TCP/IP. It just sort of stuck with me since then, even though most routers out of the box come configured to use 192.168.1.1, I'll still go through the hassle of changing them over to use 192.168.0.1 because it just looks "right" to me.



Same here pretty much. I'm not a fan of dealing with 172.x.x.x or 10.x.x.x unless I have to. It's more of a comfort thing and since that's the network address I predominately started off on when learning networking/IP subnetting.
 
192.168.10.0/24

My work is 192.168.1.0/24 (will be changing) so when I connect to VPN I would have issues connecting to devices since both the network gateways were 192.168.1.1
 
10.1.1.0/24

We used this subnet in school and I stick to it since...

Its also quick to enter and I avoiding the typos.
 
192.168.1.x or 192.168.1.x.

Much easier since thats what I have always used.(and the setup of a lan, etc long ago.)
 
192.168.0.x. Same deal as with others, learned on this, just looks right to me.
 
at home I use:
10.10.1.0/24 management network
10.10.25.0/24 for local
10.10.50.0/24 VPN Site 1 local network
10.10.75.0/24 VPN Site 2 local network
10.10.100.0/24 VPN Site 3 local network
10.10.200.0/24 assigned when VPN into local network
192.168.5.0/30 VPN tunnel Site 1
192.168.10.0/30 VPN tunnel Site 2
192.168.15.0/30 VPN Tunnel Site 3
 
172.29.187.x

I found at colleges that they either have Class A or Class C in use, but never B. So, I made my home / dorm router Class B, and just kept it there.
 
192.168.0/21. Makes it easier to remember what a device is without having to do any routing. VPN is 192.168.8/24

I may eventually move to something else more conventional but there's not really a reason to do so. unless I get something that doesn't support CIDR which I actually use unlike my old mac os and I never go on the internet on those so it makes no difference.
 
Same here pretty much. I'm not a fan of dealing with 172.x.x.x or 10.x.x.x unless I have to. It's more of a comfort thing and since that's the network address I predominately started off on when learning networking/IP subnetting.

what is the difference between a 192.x.x.x/24 and a 10.x.x.x/24? nothing. you would set your ips the same way

router 192.x.x.1 10.x.x.1
dhcp scope 192.x.x.2-254 10.x.x.2-254

with any /24 your only dealing with the last octet.

i use 10.0.0.0/24. 10.0.0.10-20 for static address and 10.0.0.100-120 for dhcp scope.
 
At home I KISS... At work, we use all 3 classes.

Same here. Work uses all three, but at home I use 192.168.1.x/24. Works great for my needs.

Of course, the Cisco lab uses all different ones when it's in use.
 
127.0.0.1/24

J/K
I use 10.0.0.0/24 to mirror what I use at the shop, but I also keep a small lab, so I'll use the 3 different private ranges.
When creating networks for clients, I like to use 172.16-31.x.x and 10.x.x.x because most want VPN access from home.
For the Home LAN itself I like to keep it pretty simple, I just throw a pfSense box and managed switch on if I need to bring work home.
 
i use 10.x.x.x me and a bunch of buddies had setup a large VPN at one point, we decided to make the first x represent the order in which states became part of the US, and then the 3rd part for each person in that state to claim the /24 of that. So myself i operate on 10.19.130.0-10.19.140.255(VLANS in use)
 
10.x and 172.x is what I use. Here is my public static IP in case anyone wants to know ...

1.2.3.4/30
 
10.1.0.0/16 :D

I don't need all those IPs, I just like to keep it organized.

10.1.1.0-254: server range

10.1.2.0-254: client device/test VMs etc range

10.1.3.0-254: server remote management range... this is where it gets nice to have this setup. Ex: 10.1.3.10 would be the management for 10.1.1.10. I only have one server that has IPMI though (Supermicro) and it does not work at all in Linux, so it's kinda pointless for me to have, but it's there.

10.1.4.0-254: misc static items. Don't actually have anything active in this range, there's a few DNS records but it's not stuff that's actually on or being used.

10.1.5.0-10.1.9.254: DHCP range... it's ridiculously huge, just because I can.


I also have a 10.11.10.0/24 network which is my external network and wifi. It's a separate port on my firewall. There's also 10.2.1.0/24 which is the VPN range.

Funny thing is, I don't have all that many devices, I just like having a highly scalable network.


I setup a very small network for my church, and the range is 10.3.16.0/24. :D (3.16 for John 3:16)
 
10.0.0.0 because its less numbers to type, sm is still 255.255.255.0 though
 
Its now 192.168.0.x for me but I just use w/e the router is defaulted to. If I run into VPN issues down the road I will change, but at this point I don't really care.
 
For my home I use:
192.168.9.x/24 Main network
10.10.110.x/24 Storage network
10.10.50.x/24 VPN network

My parents network is 192.168.10.x/24

When I setup my parents network I wanted to stay in the 192.168.x.x/24 range but didn't want to have conflicts with the standard 192.168.0.x/24 or 192.168.1.x/24 so I moved to 192.168.10.x/24. When I moved out I had to move my network to 192.168.9.x/24 so when I connected with VPN I would not have conflicts.

I have started to segment my network and using vlan's and I got the idea from work to use the third octet as the vlan id. So 10.10.110.x/24 the vlan id is 110 making it simple to know what vlan you are in.
 
192.168.31.x <-- basic workstation vLAN
192.168.32.x <-- Server vLAN
10.0.31.x <--iSCSI vLAN
 
192.168.11.xxx

I don't like to use .1 because it's the normal default...easier to plug in another router/device/etc to work on, etc without conflicts.

IIRC:

I use .1-9 for my devices, and the xbox
I use .101-120 region for my wife's devices
I use .120+ for family devices (Tivo, HTPC, etc)

Just like to stay organized. Easier when tuning QoS settings too.
 
192.168.25.x /24 for home and 192.168.223.x for my servers
 
192.168.1.x at home, again because I am lazy :p
Have a few static devices (servers and switches), laptops, desktops, and iPhones are DHCP.
 
I'm curious since I'm changing my home subnet to a 10.10.10.0 /24 range due to having some issues when using the VPN on clients that had the same old subnet as me (192.168.1.0 /24) Curious as to which subnet you guys use. and why.

I selected "Other".

I'm using 192.168.80.x. I am doing so for the same reason as you--I will have to VPN with a network that's 10.254.0.x and also has 192.168.1.x traffic on it, plus 192.168.2.x, 192.168.3.x, 192.168.4.x and 192.168.5.x ... I figured I'd get out ahead of all that and just go with 192.168.80.x, LOL. Plus for LAN parties it makes it drop-dead easy to see if people are using DHCP and connecting properly:

"Hey, what's your IP address?"

"192.168.1....."

"Woah, hold on right there, you need to use DHCP buddy!"

*fixed*
 
Im gonna be swiching from ipv4 to ipv6 because I can and all my gear supports it haha
 
I use a 10.x.x.0 with x being somewhere in the middle of the range.

I don't want any conflicts since I do site-to-site VPN's to friends, family or work.
 
Overkill, I know. Not really needed, but mostly it was done for the exercise of doing it.

192.168.1.0/24 for most uses (.10-.20 for statics, .100-.200 for DHCP). Permanent PCs in the house and Wifi using a hidden SSID and a passwords known only to me (not even wife).

192.168.5.0/24 dedicated subnet on a VLAN that never leaves by 10Gbe switch for Server-Server traffic

192.168.10.0/24 semi-exposed traffic (visitors WiFi, Web Server, FTP server, etc). Segregated via VLAN and firewall, Can reach internet via separate NAT but can't get to other machines. WiFi access on visible SSID and simple password known to my kids (and other visitors to the house). Machines on 192.168.1.0 can pierce the Firewall to get to 192.168.10.0 but initial connections the other way are blocked.

192.168.200.0/24 private, VLAN segregated management traffic. All router, switch, WiFi management ports, server IPMI, etc. Can only access via VPN protected route (or one physical switch port at my desk).

192.168.211.0/24 Separate, VLAN segregated for IP phones.
 
At home 192.168.1.x

Don't have a reason to do more than that, one desktop, a couple of laptops, a couple of tablets, nothing major going on.

At work, 10.x.x.x and 192.168.x.x and 172.16-20.x.x
 
Back
Top