this post was submitted on 04 Nov 2026
681 points (99.1% liked)
linuxmemes
33336 readers
445 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry of any kind will not be tolerated. This is an LGBTQ+-friendly community -- if that is a problem for you, you should leave.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves / tolerates / hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
255 is reserved for broadcast.
Edit: Yes, 255 is technically not 'reserved' by itself. I was only thinking about the addresses scoped to /24 for a simple answer. A broadcast address is reserved, though.
When in doubt: https://www.calculator.net/ip-subnet-calculator.html
10.233.213.255 is broadcast, 10.233.212.255 is a usable address ..
How big of an IP scope do you use at home?
Do you really need something larger than a /24?
Iβm quite fond of 10.0.0.0/8. That gives you a lot of wiggle room, just in case.
Just a little bit of wiggle room....
It's useful to keep the 16 million IoT devices you have running on WiFi segregated a bit.
Well technically a 10. network could be a /8 if you really wanted to. But in this case the /23 was specified above. I don't think it's necessary but that's what op was talking about and the 212.255 is a valid address, as is 213.0
Sure, you could. But you'd be going out of your way to setup an internal IP scope you'll never fully utilize.
I suppose it doesn't really matter, but it just feels wrong.
Yeah that's fair. Maybe OP is planning a nonsense amount of IoT devices and cameras? or they just want to use some unorthodox IPs like .255 or .0 for fun π€·
Thanks for the correction on the the broadcast address, btw. The details are important.
At home, I have 172.16/12 scoped out for my cluster subnet and just use the second and third octet to denote service function. It's excessive scoping, but it's an internal scope for a private network and broadcasts are generally contained to the cluster network. It would be trivial to split that into a 172.16/16 if I ever had the desire. (Speaking bluntly, it really doesn't matter much in this case. I'll need to split it out to keep Longhorn traffic segregated later, but it's not an issue now.)
The rest of the network is reasonably scoped out across 192.168 ranges and chopped up across a few VLANs.
My addressing scheme is split into "public" and "stay the fuck out", with most 172 addresses being the latter. At home this is great. In a large network, scoping out such a large 172 subnet could be detrimental. ("It depends" on the detrimental bit and requires proper planning and understanding about why subnets were even built into IPv4 from the get-go.)
Edit: Most addressing is static on my cluster network, with DHCP only handing out addresses based on MAC address. The 172 subnet has very restricted dynamic IP ranges.
Regardless of what is what, it's a scheme I recognize and that is the more important bit.
It might also make you really grumpy if you decide to use a VPN or containers - those often use 10/24 subnets and having an overlap with your LAN can make things spicy.
I could see something like /20 being useful not so much for the number of addresses but to group things by use case, then /8 because you don't care and it doesn't matter. Also 10.0 is quicker to type and cleaner to look at than 192.168