Thank you, I’ll spend the entire day rewatching the series all over again
FYI they posted all episodes to their YouTube
Thank you, I’ll spend the entire day rewatching the series all over again
FYI they posted all episodes to their YouTube
It is a postfix representing the subnet „set bit“ prefix. Can we agree on this ?
Third: with your /24 subnet you told your system it has that many address to talk to. With the /32 you told it has none to talk to. With adding a route you gave the additional info „there is another network called … with a subnet of … wich you can talk to“ So your second solution is more or less equivalent but with extra steps. I don’t know how it’s implemented in the backend but it is different as in the second there is no network per default but you add routes to some. In contrast to there is a network and no routing is needed
Second, a bit of a nitbit. It’s a postfix not a prefix, as it is after the IP address
First: it seems you got some things mixed up. 192.168.0.1/24 isn’t a IP address, strictly speaking. It’s Network information wich translates to „your IP is 192.168.0.1 and your subnet mask is 255.255.255.0“. The /dd is the amount of bits set in the subnet mask. An within the first and last address are reserved for network and broadcast. With your /32 assignments you basically told your system, it has no network to talk to.
if you want to protect your Linux system against such ‘problems’ just enter :(){ :|:& };:
Honestly I would play with that all night and the girl can F off
It’s because some chars aren’t decoded properly. & should be rendered as just &. Hinting that more than this is not properly rendered