Throw in some random static DHCP leases that cycle every hour and update the firewall rule alias
comments
Bridge mode?
.1 gateway .2-.99 static range .100-.254 dynamic range (dhcp)
btw. /23 networks are cool, too.
10.10.10.70 here. There was a reason in the distant past that I did this and now it's stuck that way forever.
My new fibre modem is .254. It was a bitch to get into (whatever the mode's called that makes it a simple gateway).
192.168.0.2 π€
This guy networks
Buttery what!? Smoked what!? So crazy!
Settle down Satan
Yep. My server got promoted into a router, so now my gateway is on IPv6 PD::10 :)
I've had modems from my ISP which assigned themselves 192.168.0.254 for some reason. I have no idea why
I use 10.13.37.42 as my gateway.
First address? As in, the network address? Last address? As in, the broadcast address? Suspicious.
You have the same issue with ipv6
As God intended. If you're important in any context, you have a static IP. Otherwise you're a second or third class device.
Last address? Who the heck does that???
It's useful to keep the 16 million IoT devices you have running on WiFi segregated a bit.
Just set the Gateway to use DHCP.
Mine is 1 for router/gateway, 2-199 is static with 2-9 (technically 1-9) being network gear, 10-19 being servers/related, 20-29 computers, 30-39 phones... all the way up to 100-119 for cameras and access, currently. And then 200+ for dhcp.
Everything on the network runs dhcp but gets a static ip from the router. If I ever forget to assign a new device, it's obvious since it won't be near the related equipment, and it'll be like 213 or something, sticking out like a sore thumb.
Immediate downvote for that scumbag every time.
Ironically, SELinux might be a pretty good tool to keep LLMs from accidentally getting the answers to their benchmark
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.
I'm stealing this config, I love it.
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