FrederikNJS

If you want to migrate to Linux, I would strongly suggest you set up a dual boot, and start playing with it to gain experience. Being able to switch back to something you know is a massive benefit when you are still learning.

While Linux has come a very long way, you are sure to experience some hitches along the way. If not because of Linux itself, then because you are not familiar with how to do "that one thing" on Linux.

Jellyfin has supported Music and TV shows since the start

Many accounts can go in the red

Yes, but Google would not have done that if nobody used Firefox

Agree on both parts, but the second part can still be achieved from an unconnected car, you just can't do it remotely

IPv6 does not require you to open your machine to the Internet, even without making use of a NAT. Sure you get an IP that's valid on the whole internet, but that doesn't mean that anyone can send you traffic.

Are these restrictions set out by the ISP or the dorm?

If you don't do business with the ISP, then you don't have to agree to and follow their terms.

So as long as the dorms doesn't have rules against setting up your own WiFi, then you should be well within your rights to purchase an Internet connection from another provider, but since you are likely not allowed to get your own line installed, you are probably restricted to ISPs that provide a service over the cellular network.

Of course using a cellular connection will give you worse latencies for online games, but at least you can have your own WiFi with low latency for your VR.

If you want to be nice, you could then run as much of your Internet network over ethernet as possible, so you congest the air waves as little as possible, possibly only running the VR headset over WiFi, and maybe even only enabling the WiFi radio when you want to play VR. If all your WiFi devices support 5GHz, you might also completely disable your 2.4GHz WiFi, to leave the most congested frequencies alone.

To lower the chance of someone complaining about your WiFi, you should configure it as a "hidden network", such that it doesn't broadcast an SSID, and therefore doesn't show up when people are looking for WiFi networks to connect to.

It kinda depends a bit on the user's background... For someone who is used to windows and how computers in general works, I would probably agree with you.

But for people who are more phone/tablet native, I don't think something like Fedora Silverblue is actually that bad of a choice. It comes natively with Gnome 3, which isn't too dissimilar to Android or iOS. Updates are installed in one fell swoop with a reboot, just like Android or iOS. Flatpaks behave much more like an App on Android or iOS, they are self contained, and don't affect eachother.

I just set up my daughters (9 y/o) first school laptop, and picked Fedora Silverblue, and apart from learning about the save icon, and learning how to store files in a filesystem, she was pretty much instantaneously functional, having most of her prior computing experience on an Android phone.

I really don't see much benefit to running two clusters.

I'm also running single clusters with multiple ingress controllers both at home and at work.

If you are concerned with blast radius, you should probably first look into setting up Network Policies to ensure that pods can't talk to things they shouldn't.

There is of course still the risk of something escaping the container, but the risk is rather low in comparison. There are options out there for hardening the container runtime further.

You might also look into adding things that can monitor the cluster for intrusions or prevent them. Stuff like running CrowdSec on your ingresses, and using Falco to watch for various malicious behaviour.

No need for a physically separated network, that's what VLANs are for

That sound like you need a more serious setup, where you can control the network priorities and set a QoS, so the devices that you use interactively get priority over the other devices.

So as far as I understand, you have

• Outer router (Comcast), which has WiFi enabled
• Inner router (your own), which has WiFi enabled, and further meshes with other WiFi mesh devices (or is the mesh separate?)
• A plain switch, for stuff you want cabled and fast

Is that correct?

Why not get the WiFi in the Comcast router disabled, and use your inner network exclusively, such that both WiFi and ethernet devices are on the same network?

That's what I did with my network, and I even got the ISP to put their modem/router into bridge mode, so it's completely transparent.