Getting tired of typing 192.168. Why doesn't everybody use something simple like 1.1.1.x in a small LAN? What about 0.0.0.x?

Because 1.1.1.x and 0.0.0.x aren't in the reserved address space for private networks. As soon as your machine tried to access a public server that happened to be in the 1.1.1.x subnet, the connection would fail, since your machine would attempt to find that server on your local network.

Meanwhile, 192.168.x.x is reserved for private networks, which makes it OK to use as you wish. You will NEVER run into a remote server with a public IP of 192.168.x.x, or 10.x.x.x, or 172.[16-31].x.x, so those are "safe" IP ranges to use for private networks.

https://en.wikipedia.org/wiki/Privat...address_spaces

Because those blocks are not meant for that use, and if APNIC ever changes their policy for 1.0.0.0/8 you'll be fubar'd.

Use 10.0.0.0/8 for this because it's specifically meant to be used in the same way 192.168.0.0/16 is.

1 members found this post helpful.

What are 1.1.1.x addresses currently used for? Typed http://1.1.1.1 on a browser and it never loaded anything, it failed after a while.

http://whatismyipaddress.com/ip/1.1.1.1
http://serverfault.com/questions/339...tp-1-1-1-1-bmi

Netgear routers use 10.0.0.x by default. Much easier than 192....

This answers OP's question most thoroughly: http://www.ralphb.net/IPSubnet/ipaddr.html

I have been using 1.1.1.0/24 subnet for 15+ years on my home LAN and have never found a single instance where any computer in my house ever tried connecting to any address inside the 1.1.1.0-255 range outside my house.

Yes, I realize these are 'publically allocated addresses' but I too got very sick and tired of typing 192.168.blah.blah all the time. I do extensive lab stuff for work where I have servers I build and test in my LAN and am constantly typing IPs all the time.

I still have no regrets about using this subnet. In fact, today in my lab work, I also use 1.1.2.0/24, 1.1.3.0/24, 1.1.4.0/24, 1.1.5.0/24, 1.1.6.0/24, 1.1.7.0/24, 1.1.8.0/24, 1.1.9.0/24 and for the 1.1.2. to 1.1.9. range those are only for lab equipment (have no gateways) for things like iSCSI, vMotion, VSAN and stuff like that so I don't care about them anyway.

You know, if everyone in the world started using 1.1.x.x addresses for home and private LAN use then maybe the industry would change their standard and re-allocate these for official private LAN use, since if someone put a web server on those nobody would ever find their way there. They would be unpopular. Or I guess they are already unpopular because I don't see anyone really using them anyway.

The address you are using is legally owned by some other company/person. It may be easy or lazy to use 1.1.1.1 but you are in effect making it difficult possibly for others on the web that own and have paid for that range. You should conform your system to current standards. Geeze, how hard is it to type 10.x.x.x ??

You can't force a change to the IP ranges based on bad manners. The world is moving to IPv6 anyway and you'll have to type a lot more then.

2 members found this post helpful.

It does not matter if anyone owns it or not. I am not interacting with their IP in any way on the Internet since it is a /24 on my network. The home NAT router converts it to public subnet once the outbound packet goes through the gateway, and the only net effect to the world is that there are 255 addresses I cannot get to from my home LAN (I probably didn't want to see those websites anyway).

If I ever did find a site (like if I was at work on their gateway), and really wanted to see it at home, I could just visit it from my phone on 4g, or if I really felt I needed to go there from my home gateway I could just set up a one-to-one NAT rule to allow routing out my gateway to the one IP hehe..

BTW, IPv4 isn't going away anytime soon.. Most likely IPv6 will be used mostly to free up IPv4 addresses on more complex equipment where humans don't normally interact with. I have IPv6 in my labs but they are only used for backend server processes to communicate multicast to and receive from and they assign their own internal DHCP so I never interact with those much unless I need to ping something (then I just use copy/paste in putty in those rare events, even that is annoying)..
.

If typing ONE more character to use a compliant 10.1.1.X subnet rather than an allocated 1.1.1.X subnet is too much of a chore for you then you're beyond help.

2 members found this post helpful.

See RCF 1918 section 3.

I was the one asking for help. He was answering/opining. It will be a useful job skill to make the distinction. Not that I agree with his suggestions.

And it's you my comments are aimed at.

I think you have your answers. What concerns do you have aside from just arguing and disagreeing?

1.1.1.1 is public space, yes.

Yes you can use that range in your private network with the correct routing.

Yes you can specifically route any 1.x.x.x ip addresses that you actually want to get to in asia.

Why doesnt *everyone* use 1.1.1.1 or 0.0.0.0 instead of 192.168, 10, or 172? Because everyone has different methods. Some don't want to risk something going awry. Some are used to using private addresses as intended.

1 members found this post helpful.