You both repeat the same to a person that insists 1.1.1.1 is better than 10.x and you have both mixed him up with the OP, and I am the OP. If you want to practice advising people, your reading skills need some polishing because it was obvious I did not know 10.x.x.x was ok and never opposed this.

I was replying to three people without quoting because there were only 14 posts. I was assuming everyone had read the whole thread.

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.

One concern is that you are allowed to play teacher to people possibly more experienced than you who are NOT asking you questions but opining and you cannot tell or care about the difference.

Another concern is that if anyone disagrees with those people's opinions (and therefore agrees with you), you perceive it as arguing and it is their fault.

I guess I read the question wrong. When I read lan I assume that it is not a completely isolated subnet.

You are correct that anyone could use an isolated lan with any ip address they wish.

Never tried 0.0.0.x but I get the feeling it won't work.

I'd say the problem with getting used to such ways might lead one to make a huge mistake someday. (don't ask how I know this.)

So let's talk about this... What could possibly go awry? Do you think the Internet is that insecure that you could affect it negatively and take some part of it down?

To illustrate a point here... Let's say for example, you decided to set your WAN IP address (even by mistake) on your home router to 1.1.1.x, well the ISP upstream will not have that subnet/gateway in their BGP routing tables, so any outbound packet would just be dropped as 'no route to host'.

Let's suppose just for a moment that you actually subscribed to an ISP which did have the 1.1.1.x route on their router (super unlikely), if you were to set a WAN IP on your home router that conflicted with any other device inside their gateway, they would just run a trace and figure out yours was the bad IP and block your port (then you would call in to get your Internet fixed). And besides, we're not even talking about setting WAN IP's here. When you set LAN subnet, it in no way interacts with anything on the WAN side unless NAT is turned off (where routing still on), and you can't turn off NAT on home routers.

So again, the ONLY net effect of using 1.1.1.0/24 on your home network would be that you could not reach any website on the Internet between 1.1.1.0--1.1.1.255, and nothing could ever go awry beyond this.

So if you're thinking of selling me a product and are planning to put up a website soon, please tell your ISP provider (where you put your web server), that you don't want a public IP in this subnet, because I will never see it (unless I am at work, or connected to their VPN, or on my 4g phone connection).

Also, some asked why not use 10.x.x.x ? Because 1 and 0 are all the way on each ends of the keyboard and my laptop doesn't have numeric keypad.. When you do labs as much as I do, sometimes you type 100s of IPs in a session of building something like a virtual cloud lab. The amount of time it saves me to do 1.1.1.x is worth it 100-fold (vs the 254 websites I will never see)...

I'm not saying its for everyone, like if you think you may someday want to visit those, up to 254 websites (maybe many of them are just other home routers you never need to ping directly), or if you are a 'standards' based individual who thinks inside-the-box all the time, and college taught you that you need to adhere to the IP address standards always, then I would highly recommend you use 192.168.1.x or maybe if your daring, you might try changing it to 2. or 3. to be different from your peers. But for me, I like 1.1.1.x for the rest of my life, hehe...
.

Back to your original question (haha from a year ago)...

I prefer 1.1.1.x over 0.0.0.x because the '1' is at the left of the keyboard, closer to where you left hand usually sits, and your right hand is close to the '.'

So is fastest to do 1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1


IPv6 will be a bit more challenging because we have to do ':'

1:1:1:1:1:1:1:1 is harder to type, so I think if my ISP ever switches to IPv6 for my public IP, I will always still keep using IPv4 on my LAN til the end of my time here.
.

The standards are there to keep everything working well for everyone under all conditions, anticipated and unanticipated, and to facilitate resolution of conflicts when they do arise.

It isn't about thinking outside any box, it is about observing the published rules of the road for the good of all who use it.

In that regard, it is unimportant whether or not you can think of some case where your actions affect others. The really important thing is that you really just don't care whether your actions affect others.

After all, according to you, if they do affect others they could "just run a trace and figure out yours was the bad IP and block your port (then you would call in to get your Internet fixed)".

You just don't care that this is a totally avoidable inconvenience for all others concerned, it is convenient for you.

Please reconsider that position.

I'm not on any road. I am off-road, in my field with my ATV.. I wouldn't try to use that subnet on the www (it wouldn't route if I tried since my WAN is on a 50. network anyway)..

BTW, I have the utmost respect when it comes to working in public domains. I worked at an ISP for several years and know all about the challenges they face on a daily basis. I would never try and use a public IP address without getting one assigned to me by my ISP.
.

Since you used to work at an ISP, why don't check out my latest thread about possible rogue elements in ISP's and telecoms companies:

https://www.linuxquestions.org/quest...es-4175599327/

Man, am I confused by this thread!

There are three IPV4 private network address ranges to choose from. These are the only ranges that are understood to be "internal only." Therefore, these are the only ranges that should ever be used on anyone's internal network.

Any "outside" router, upon receiving a stray packet with an internal-only IP address, would silently drop the packet, knowing that it cannot be intended for the outside world.

The address-ranges cited in the OP would be presumed to exist "out there on the Internet, somewhere." That is to say, they would be taken as "out there, somewhere" not "in here, somewhere." Why? Because they're not in any of the "private subnet" address ranges.

Now, an "internal network" can indeed become quite large, when many different offices and their respective subnets are connected by (secure or insecure) routers. You can also sometimes encounter problems with the IP-address choices of coffee shops. But the fundamental rule must hold: "here are the [only] address-ranges you may use for internal networks."

2 members found this post helpful.