'Option in', and 'dest' are clear, but what does 'lookup' and 'table'? I would really love to understand this and avoid asking noob questions next time. Why this helps here? Also, my new firewall rules only say, that routing from LAN2 to VPN is fine, but why the routing from the VPN server Phone) works? Can you explain this to me in some simple words? Especially the routing rules. So now all my devices are part of a new virtual LAN (eth0.3). See: in different forums (like in the one from my link) it's said the firewall don't like to route from WAN to VPN. There are two things I have to find out now: how to let some devices not use the tunnel (this already worked with VPN PBR plugin for me, but I am not sure if this can be combinated with your rules easily) and then I really need some time and maybe explanation, why this works. Also can access my devices over LTE! Man, thank you so much! Holy sh*t!!! It works!!! Connecting over WLAN in my network:mullvad says it is connected Connecting via LTE: Mullvad say connected. I added forwarding from LAN2 zone to Mullvad zone and accepted forwarding.

Here again a screenshot from the new firewall view.

The fw zones are: Lan contains lan interface (eth0.1), wan contains eth0.2, wg_mv contains wg_mv interface, lan2 contains eth0.3 and wg0. My Phone Wireguard interface is called wg0, so I replace phone_vpn.

So I think this is a routing rule issue.Īs you wrote. Mullvad seems to work nevertheless (VPN PBR shows me valid IPs for all interfaces) and I also see packages in the interface view. Unfortunately internet access stopped for everyone in the nework. I got a new Ip from the new range, and LAN stopped sending packages, LAN2 became active.

Mullvad vpn android