/31, looking shady since 3021
comments
According ding the the law of minimal keystrokes, there's actually only 9 to choose from.
After applying the law of minimal motion, you're down to even fewer.
Then you go a step further to just using 127.1 (or your preferred last digit)

By adding a host, or /32, route to the gateway you should then be able to use it as the default gateway on your main subnet. I was not being serious when I suggested it, as another comment says, it's a pretty stupid idea, and there really isn't any sane usecase for it, except possibly one of those 1am "if it's stupid but it works it's still stupid, but it'll do until morning" type fixes that you shudder to recall years later.
I have had to deal with a lot of companies where they did the opposite, acted like 192 was a /8 and did stuff way out of the private range.
The real nightmare when someone puts two ip addresses on the same host through different interfaces. Now that makes for some confusing troubleshooting and explanations in various applications.
What really gets me is in about 3/4 networks in the last couple of weeks I've been asked to help troubleshoot, the problem has been duplicate IP addresses. I don't know what is going on with people...
It can be made to work, just really really stupid.
Ultimately the 'gateway' is really a mac address, and the IP is just the thing to ARP to get the mac address. And you can do some gnarly things to pull off things like off-subnet gateway addresses.
You should never ever do it, but you can if you hate yourself enough.
Becomes easier in IPv6 to do these shenigans too.
I recently had a ticket for a university that had a /12 of public IPs. They gave every computer, printer, etc. a public IP on their whole network. Nothing has NAT. It was insane. They could buy an entire other university building with the money they'd make selling some of that address space down to even a /24.
Everyone knows you need to be using a network like fd25:c74c:a5e9::/64. So much more fun that way.
Depends on the equipment. I prefer cidr because its simpler, and ipv6 uses CIDR. Do you want to spell out a /64 in a netmask format? It would look like this: 255.255.255.255.255.255.255.255.0.0.0.0.0.0.0.0
Thatβs mostly because it violates established standards, but you know that already. Lol.
Hey, for all you know he might actually be the proper owner of that subnet.....
I know if by some crazy coincedence I had that in my subnet I'd be using it for fun.
That's another private range that was added for Carrier-Grade NAT that is part of RFC6598. It's a non-Internet routable 100.64.0.0/10 subnet for things like WISPs, Satellite providers like Starlink, Tailscale, and cellular providers that are strapped for IPv4 addresses.
Ok one last question: did tailscale have to buy the 100.100.100.x range, or is that available to anyone and they are just the only user i know?
Thanks, that rule about which masks are allowed was definitely not clear to me at first, thank you
0.0.0.0 is usable, not routable, but still very usable
https://github.com/zhoreeq/meshname/blob/master/protocol.md :
IPv6 address is converted to its binary form {...}; The binary value is encoded to base32 (RFC 4648) {...}; Padding symbols "======" are removed from the end of the string.
You can now put text into the address like with .onion sites, or session messenger nicks.
also servers
Your question is already answered here, but it also reduces traffic by keeping packets within a network defined by the subnet mask. It establishes guardrails so packet broadcasts aren't sent everywhere. The Internet is a single network. But not all of it can communicate with other parts without the right access permissions. Subnet masks are one very basic aspect of that access control.
Haha all good homie.
Fwiw, I now use 10.10.220.0/24. I now know what class A, B and C are. I didn't then.
Hopefully that offers you some comfort.
That's mostly because it violates established standards, but you know that already. Lol.
Also, if you're talking to a network engineer, they probably have PTSD dealing with a client that did this with a 1.0.0.0/8 used internally or some shit and now huge swathes of the internet doesn't work, but somehow it's "our fault" that they can't load random web sites.
Danny John-Jules?!
Like I said ... Basically everybody.
Also it's always the fault for every problem.
Mostly to make the next sysadmin (or yourself in 6 months) weep. There's nothing preventing there being multiple IP subnets on a single network segment, but you'd usually handle that with separate VLANs, or at least an interface alias, so the machine saw both subnets. About the only reason I could see for just adding a static route would be if you're in the middle of reconfiguring your network to a new subnet but you still need the hosts you haven't updated to be able to route.