I have checked if others have suggested this already
[X] I have checked this issue tracker to see if others have reported similar issues.
Feature description
I installed mullvad linux client for the future use and left it as is without account configured. My computer usually is in sleep mode and not shut down, so the mullvad daemon wasn't started in a week or so.
But when I rebooted the computer my networking seemed to be broken. I spent 30 minutes debugging drivers and networking manager and trying to fix things. And only after I spent some time in htop I found mullvad daemon and decided to check if it has any effect on networking.
So what I suggest is to only enable lock down mode after explicit interaction with mullvad client.
I have checked if others have suggested this already
Feature description
I installed mullvad linux client for the future use and left it as is without account configured. My computer usually is in sleep mode and not shut down, so the mullvad daemon wasn't started in a week or so.
But when I rebooted the computer my networking seemed to be broken. I spent 30 minutes debugging drivers and networking manager and trying to fix things. And only after I spent some time in htop I found mullvad daemon and decided to check if it has any effect on networking.
So what I suggest is to only enable lock down mode after explicit interaction with mullvad client.
Alternative solutions
I don't know, but the experience was very bad.
Type of feature
Operating System