Why is mangling required at all??
Can you explain more clearly how external traffic is entering your router (for presumably some work, lets say to reach a server on a lan subnet) is not able to then go out the same WAN in response.
How the heck does this have anything to do with traffic originating from the LAN going out the wireguard tunnel.
Nothing makes sense...
A diagram would be helpful but is it fair to assume you have a MT device at home and want to use mullvad VPN for either
one of the lan subnets behind your router, or some specific IPs on subnets behind the router FOR INTERNET TRAFFIC.
If this is the case mangling is NOT required.
There should be no interference from external users coming into the router to access servers and your use of the VPN for internet traffic.
Also is there a reason that the MT router could not also be a server (to allow you to connect to the router remotely and securely for example)?
Hello,
If I simply deactivate the mangle rule, I just cannot browse the Internet at all.
I'm not a networking expert, therefore I found this guide very helpful in my case
http://littlefool.de/posts/mullvad-wire ... outeros-7/ ; I guess, the mangle rule is correlated to the routing rules added which are required to route the traffic through the Wireguard Interface as Mullvad/ProtonVPN is giving some IP address to use on the interface created previously.
If there is another way to do the same, without mangle rule, why not, in my case it's
now working well. I just want to pass my Internet traffic from my LAN through a wireguard Interface. However I still want to have my server hosted on the LAN reachable from the Internet using the dedicated IP my ISP gave to me. That's it
There is no need to be "rude" or anything like this. Thank you.