
comments
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
Thatβs the kind of overengineering I was hoping for!
There are no windows in your house.
https://vlipsy.com/clips/dr-tran-there-are-no-windows-in-your-house-aoFRHS2T
10.0.0.0/8 address space with a gateway address that gets randomized every 24 hours. Tomorrow's address is advertised on a HTTP server local to the network that cannot be externally accessed. For security reasons.
Iβm quite fond of 10.0.0.0/8. That gives you a lot of wiggle room, just in case.
How big of an IP scope do you use at home?
Do you really need something larger than a /24?
10.233.213.255 is broadcast, 10.233.212.255 is a usable address ..
My soho setup is:
1-100 = DHCP
101 = Default gateway
102 - 199 = Unused
201-254 = Static, manually assigned IPs (if any)
I came up with it before I got my Net+. I told myself I'd change it as soon as it caused any problems. That was 12 years ago.
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
Gonna use 10.233.212.254 on my 10.233.212.0/23 π
Why not 255?
.254
Anything else is mental illness. .1 is sus but acceptable in a pinch. But why cut into the DHCP pool like that. 1-100 is DHCP, obviously.
Shhh!!! Altman will hear you. Only he can download more RAM.
Even projects that expressly prohibit AI code still have AI code in them. It's damn near impossible to actually enforce. I don't like AI code but I know I can't avoid it so I don't see the point in trying.
In some usecases SELinux is less flexible:
You have two applications installed which bring their own labels and rules, lets say app_a_t and app_b_t.
Now you want to give AppA read access to only one specific directory of AppB data (which is labeled app_b_t).
How to do that? Writing a rule allowing acces between the labels would give AppA access to all of AppB data. Creating a new label for this specific dir would break AppB as it relies on the rules for app_b_t.
My biggest issue with SELinux is that files and applications can not have multiple types at once (like with a role based model).
I use AIrch, btw
ZorAIn OS
Boo Steven chrowder booo
AIrch and MAInt
UbAIuntu derived from DAIbAIn
SUSSAI
FAIdora
No. GNUnAIx
LAInus TorvaldAInus OS π€