12/19/2023 0 Comments Mullvad vpn arch linuxI reset the config file, connect to mullvad and check what routes are actually being pulled. # ip route show dev tun0ġ0.15.0.0/16 proto kernel scope link src 10.15.0.3 turns out PIA gives a simple address, but mullvad gives a subnet. # ip route replace default via 10.15.0.0 table vpn GATEWAYIP=$(ip route show dev $VPNIF | egrep -o '()' | head -n1 # Niftiest Software – # Modified version by HTPC Guides – VPNIF="tun0" I believe the error lies with the routing table. The rest of my setup follows this with only a few changes (notably I'm on arch and I use ip instead of ifconfig).Īgain this works fine with PIA, so I know there's no typos or omissions. I also commented out the up /etc/openvpn/update-resolv-conf line and added up /etc/openvpn/iptables.sh instead. I edited the mullvad config file to include the line: route-noexec. With no changes to the downloaded openvpn config files, the connection works and all my traffic goes through the VPN. I have confirmed that in the default configuration, mullvad works fine. I had used the HTPCGuides split tunnel guide in the past with PIA to route traffic through the VPN based on the user, but I can't seem to get it working with mullvad using openvpn, iptables and static routes. As one of the refugees from the PIA sale, I have moved to mullvad and am trying to get everything working the way it did before.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |