old, stupid
honestly, i expect this behavior with a kill switch.
but i switched to an easier to manage prevention mechanism; you run your vpn connection in its own container using gluetun, and then run your torrent client (or whatever app youre locking down) in a container with its network defined as the vpn container. your lan access the downloads via the docker host.
no muss, no fuss, no bleeding
well, im not as im not using interfaces that are affected by the vulnerability (im using named, containerized network interfaces), but i appreciate the info!
it was initially reported as ‘linux & android’ were not affected.
i stand by my statement that this isnt about the VPN provider, its a client problem. so the question about Proton is moot.
but it’s correct in that it’s ’All mail [you actually want to see]’.
this is my point. the term ‘all mail’ was not subjective, is now subjective. the labels purpose has changed fundamentally. it should be changed to match this new paradigm.
and no, i personally never expected anything to be excluded from ‘all’ considering its historic use and freakin label.
i use jellyfin also, but i dont hide it behind my VPN… no real reason to. it already has valid SSL cert, and user credentialing. so my jellyfin container uses the hosts network.
i only really care about my ISP detecting torrent activity as they can shut me down.