Mullvad selective routing doesn't work

Started by Qwertylala, July 19, 2026, 11:42:21 AM

Previous topic - Next topic
Hi,

It seems like OPNsense 26.7 broke something related to how I do selective routing through Mullvad VPN. I used this guide to set it up:

https://forum.opnsense.org/index.php?topic=38550.0

I followed the guide a few months ago and it has been working perfectly with several devices but now none of them can reach the internet. I updated to 26.7 a few days ago and today was the first time I used a device that should be routed through Mullvad. I haven't changed any settings since the update except migrate the firewall rules. I can ping the devices on my LAN so they have network access at least.

The status page shows that the Mullvad tunnel is up and running and some data is sent and received (a few MB). According to Mullvad's server status page the server I'm using is working too.

Any idea where I could look for the problem?

You didn't mention whether you've performed the NAT migration or not but I would start with verifying Source NAT rules (previously Outbound NAT).
26.7|Intel N150|4x3.6GHz|8GB|256GB NVMe
Cisco L3 switch OSPF->FRR+BFD
Chrony|DoT|HAProxy+NAXSI|Suricata+Wazuh|NetFlow->Akvorado
IPSec|OpenVPN|Wireguard
MultiWAN: 1Gbit fiber dual stack + Cellular failover (PPP)

--
Available for private support.

Quote from: sorano on July 19, 2026, 12:16:02 PMYou didn't mention whether you've performed the NAT migration or not but I would start with verifying Source NAT rules (previously Outbound NAT).

Yes, there it was! I did migrate the firewall rules after the update and now when i checked the Source NAT page it was set to Automatic Source NAT rule generation, when it needs to be Hybrid. I changed to hybrid and my old Mullvad rule showed up again. Now everything works.

Is this a bug in the migration or did I miss something in the instructions?

Thanks for pointing me in the right direction.

Quote from: Qwertylala on July 19, 2026, 02:25:00 PMor did I miss something in the instructions?
You missed this : https://forum.opnsense.org/index.php?topic=52257.0

Basically that already needed to be changed in (one of) the last release(s) of 26.1.x to avoid future issues ;)
Weird guy who likes everything Linux and *BSD on PC/Laptop/Tablet/Mobile and funny little ARM based boards :)