0.0.0.0 is usable, not routable, but still very usable
comments
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.
Thanks. I hate it.
That won't work, unless I'm misunderstanding you. You'd still need a gateway within your subnet to handle inter-subnet routing or an additional address on the gateway network.
Who hurt you?
As a Network Engineer: If you did this in my presence, I'd burn you at the goddamn stake. 😂
Well, a network mask is by definition always a sequence of 1s followed by 0s (in other words, you can't arbitrarilly have some bits be 0 in between bits which are 1), so that /24 in CIDR notation is literally "/" + the number of bits in the network mask which have the value 1.
In other words, because of that "sequence of 1s followed by 0s" rule both 255.255.255.0 and /24 are just two different descriptions of the same network mask, first as 4 decimal numbers separated by dots, whilst the second as the count of bits in the binary representation of the mask which have the value 1.
For example, the 255.255.252.0 network mask from my first example in my last post could also be represented by /22 since the mask has 8+8+6 = 22 bits with value 1 and the rest are 0 - 192.168.0.0/22 means the same as 192.168.0.0/255.255.252.0
There is no point in having both that part of the CIDR representation and the decimal mask representation at the same time because they're both different representations of the same thing so having both is redundant.
I shared another post here with how subnetting works. Basically, if you start with 192.168.1.254 on a /24 for your gateway and move to a /23, your usable range goes from 192.168.1.1-192.168.1.254 to 192.168.0.1-192.168.1.254.
In this situation, the gateway address stays the same and since the /24 is contained within the /23, they can still connect to the gateway and keep working while you migrate things. The only thing they cannot talk to is clients in the 192.168.0.0/24 space until they pull new DHCP or have their static address updated. As such, it can make future expansion easier, if necessary.
If you used 192.168.1.1/24 as the gateway initially, you'll notice that in this same expansion plan it's now smack in the middle of the subnet in a /23. Is that the end of the world? No, but it looks like shit and complicates things if you did something like I usually do and allocate certain "sections" of the subnet to non-DHCP space. Also, now you need to manage two DHCP pools, one below 192.168.1.1 and one above it. It's one of those small things that compounds with each bandaid until you're dying by a thousand cuts.
I'm theory you would design your network with a large enough subnet from the get-go for expansion, but sometimes you screw up, so habits like this can make those screw ups less painful.
I used to use 1.2.3.4 as my gateway.
At the time I didn't understand why this offended ... Basically everybody.
Is there a specific reason behind this? Never considered it but I could see it being useful since most specific routes win.
Glad I could help with learning a new thing! If you are curious on anything else networking, I'm a Network Engineer by trade and happy to share knowledge.
Thank you for this explanation! Now i finally understand what the "mask" part means! Any 0s will mask the IP address in the AND operation and tell the computer that address is not part of the network.
Thankyou! So when I see things like 192.168.1.0/24, is that CIDR notation? And does that do a similar thing of the subnet mask by telling you which addresses are part of the subnetwork?
Can you have CIDR and subnet mask at the same time?
Its just descriptor of size of your local network (aka size of address pool you can assign to your devices)
I’ll be everywhere...wherever you look. Wherever there's a fight so hungry people can eat, I’ll be there. Wherever there's a cop beatin’ up a guy, I’ll be there. I’ll be in the way guys yell when they’re mad...I’ll be in the way kids laugh when they’re hungry and they know supper’s ready. And when our folks eat the stuff they raise and live in the houses they build...I’ll be there.
The whole of DNS configuration is just conventions.