this post was submitted on 04 Nov 2026
691 points (99.1% liked)
linuxmemes
33336 readers
281 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
There are reasons to put it at the end. For example, 192.168.1.254/24 can be expanded to /23 and have the same gateway address while you migrate clients that are statically assigned or while waiting on DHCP leases to expire, since /23 is a supernet of /24.
What am I missing here?
192.168.1.1/24 would also be a valid gateway for a /23, with the benefit of not having a gateway in the middle of your /23 network?
I feel like this example is a greater justification for putting the gateway on the network/CIDR + 1, like a civilized person.
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.
Bleh, gotchu, I was getting the bit boundary wrong (192.168.0.0/24 > 192.168.0.0/23; NOT 192.168.1.0. that's not how bits work)