Alright, I was able to resolve this through some research and time spent reading. If anyone else needs it, here is what I found.1.) Something changed when Wireguard moved into the kernel in v23. This something broke many previously implemented Wireguard to private VPN service tunnels.2.) The initial part of the WireGuard MullvadVPN Road Warrior Setup guide can still be followed, with one small change.Follow "Step 1" of the above, except when configuring your "instance" be sure to check the box "disable routes". If you don't it will create an automatic route that breaks external traffic over the wan.Also, the guide above tells you to add a DNS server in the Peers section. This no longer appears to be possible. It is also not needed, as long as you used the version of the Mullvad Curl script that hijacks your DNS, as you will use Mullvads DNS either way, at least when connected to Mullvad.Once step 1 is complete, shift to this video at timestamp ~8:39 Note that the youtuber is using the older WireGuard-go plugin which is now deprecated. You can still follow his instructions, but whenever he uses the WireGuard config tab labeled "Endpoints" use the tab labeled "Peers" instead. And whenever he uses the tab labeled "Local" use the tab labeled "Instances" instead.Follow the youtubers guide to setting up firewall rules NAT rules. He splits his video into two parts. The first for forwarding ALL traffic through the VPN, and a second for setting up a gateway to later use firewall rules to decide which traffic goes through the VPN.The first "everything through VPN" setup he configures will not work, but set up the rules as he does anyway, as they are needed in the second part. If you complete the second part you should wind up with a second gateway just for Mullvad. You can then use firewall rules to pass traffic through to whichever gateway is appropriate, Mullvad or wan to bypass Mullvad.I usually set up a rule at the end of each networks firewall ruleset that passes all traffic through to the Mullvad gateway. Then if I want specific exclusions, I add pass rules above that, to pass specific traffic types or traffic from specific hosts to the wan interface bypassing Mullvad. I hope this saves someone else some time as I was about to tear my hair out.I suspect (but I am not sure) that there is a bug in the current kernel implementation of WireGuard that creates a faulty, non-functional default route, unless you check the box to disable it during the creation of the instance, and that is what is causing all of this trouble.
Hi,Can't get it to work. I'm using a vlan tag (added interface) to pluck the internet traffic out of my fiber connection. Are there additional steps I must take? Would you consider a complete step by step write-up (verbose) please?Kind regard.
