Why have a non-'guest' network? Force anything secure over a proper VPN E.G. wireguard.

Streaming services block VPNs, many sites like Wikipedia impose restrictions (no editing allowed from a VPN), and geoloc based services act oddly (I live in London and my VPN server is in a London data center, but Google thinks we are in Dubai and G.Apps default to Arabic).

Hadn't really considered that. A bit inconvenient, I don't know that I'd want to VPN inside my own network just to access my servers.

Surely this is desirable while away from home too?

Not sure I could enforce QoS priority on the wireguard traffic. Easier with a non-guest SSID. Is there a huge performance benefit if there's just one SSID running in my airspace?

Also, for the OP, sounds like it's time to put the kids on the guest network.

You can QoS tag by whitelisted mac addresses if it's just priority to known devices generally. At best your router may be able to slightly shape devices on the network (strategically dropped packets). QoS over the air doesn't really work as there's zero control of any devices tying up RF spectrum, and zero ability to defend against DoS attacks (E.G. neighbor trying to stream 4K over wifi).

> sounds like it's time to put the kids on the guest network

I have considered that, for sure.

It definitely asks for permission, and only prompts mutual contacts to begin with, as far as I know.

It asks the sender for permission, which is not the same as asking the WiFi owner. My kids have their friends as contacts, so it happily shares with them.

My wording was probably a bit wrong but there is no concept in wifi of ownership so by owner I meant the person who set it up but not exclusively them, just that they would have it.