Mullvad VPN needs manual interface configuration each boot
-
I followed the Mullvad VPN guide for pfSense and got it working, but I discovered that it only works if I go into the Interfaces GUI menu and do the following:
uncheck Enable interface -> Save -> Apply Changes -> re-check Enable Interface -> Save -> Apply Changes
For some reason, disabling and renabling the Mullvad OPT1 interface fixes the problem. Does anyone know why this might be occurring? Does anyone know how I can make this occur programatically?
I'd like to run a shell script at startup, but in testing shell commands, I found that running reboot commands in the shell like "ifconfig mullvad down/up" and "/etc/rc.linkup stop/start mullvad" don't seem to do the trick like the GUI menu does. It appears as if unchecking and then checking the "Enable interface" option is doing more than it might appear, but I have no clue what is going on behind the scenes. Does anyone know how I might replicate this GUI behavior programatically?
-
J jupitersetting referenced this topic
-
I fixed this by messing around with alternative settings, but I'm not sure exactly sure which ones fixed this.
Possible things I did that could have helped fix it:
I tried adding a separate wireguard configuration, changed the listening port to a non-standard port and then back again, and added another dns server. Not sure if any of those things were responsible for the fix.
Privacy Policy · Cookie Policy