The VPN tunnel are not persistent!
I imported a second Mullvad config file specifically for a US server. Then assigned that new config to the Pluto tunnel's. It worked for 30 min and then it started pointing to the Primary tunnel.
restart second tunnel, then no more internet and then I reboot the modem ??!!!
The priorities also determine the order in which the rules should be processed.
If you always want to route Pluto via us-nyc-wg-301, this must have priority 1. In addition, to avoid leaks here, you should then exclude the device in the other priority and/or set the global kill switch as well.
To be explicit about your rules: Priority 1 matches all your devices to any destination except one. So all that traffic goes to VIenna if the tunnel is up. Then Priority 2 matches one device to the one destination excluded, and that goes to NY. If there is no kill switch, then all the other devices going to that one destination go out the WAN, and if the tunnels are down everything goes out the WAN.
If you swap them, then one device will always go to NY if the tunnel is up. Then the second rule will route all devices (including the one device), to any other destination but that one, to Vienna. Then any device going to the one destination will go out the WAN (including the one device if the tunnel is down).
The priority “Pluto“ has it’s own vpn config file, why does priority matter?
Because that's how the rules work. The config files are just how to connect to the VPN, the rules will decide which device uses which VPN in what order.
OK, thank you for the explanation and it seems to work.
You can also exclude your one device from the VPN tunnel you don’t want it to use. My personal devices go through one tunnel. Then my work devices go through another. I exclude the work devices from the personal tunnel and then include them in the tunnel I want them to use. My work devices are in the priority 2 tunnel, since they are excluded in the priority 1 tunnel they bypass it.
Now Devices connected to WiFi periodically lose internet connectivity. The only fix is manually toggling the WireGuard VPN tunnel off and on in the admin panel.
Is there an issue with dnsmasq is being killed
23:09:45 dnsmasq[22443]: exiting on receipt of SIGTERM
23:10:12 dnsmasq[16047]: exiting on receipt of SIGTERM
23:10:36 dnsmasq[18863]: exiting on receipt of SIGTERM
23:12:35 dnsmasq[21611]: exiting on receipt of SIGTERM
23:12:51 netifd: Network device 'wgclient1' link is down
23:12:55 netifd: Interface 'wgclient1' is now up
Is this a known issue in 4.8.4? Is it fixed in 4.8.5 Beta?
