"Quote from: pete.magnusson on July 27, 2024, 06:33:51 PMJust a awesome amazing guide!
Works like a charm!
I just got one question if you dont mind.
Following these steps i get it working so i get my traffic over Mullvad and can access my "LAN" devices ( as per my Interface i selected in 6.1 ) but i am not able to connect to any of my "IOT" devices in a different vlan.
Do you have any recommendation for this?
Cheers
Hi Pete,
I had the exact same challenge as you. Here's how I solved it:
- Create an alias for your VLANs under Firewall --> Aliases. In my case I named it "PrivateNetworks" and assigned the content of "192.168.0.0/16" because my different VLANs resolve into subnets within 192.168.10.0/24, 192.168.20.0/24, etc. (this is just my case, yours might be different)
- Adjust the "Destination" in step 6.1: Select the checkbox "Destination / Invert" and select your previously created alias "PrivateNetworks" as "Destination". --> Save & Apply
This will result in only allowing traffic to the new (mullvad/wireguard) gateway if the destination address is not within a private range, in my case within 192.168.0.0/16
In other words internet traffic will use the new mullvad/wireguard gateway, whereas internal networks will continue to be routed internally.
Hope this helps. If it doesn't feel free to ask again.
Cheers,
Ed
