Mullvad blocks incoming traffic from LAN

[luojiesi]

Operating system: Windows 10

App version: 2023.4

I don't know whether this is expected or not. I have a PC (192.168.50.100) connecting to a router (192.168.50.1). I have set port forwarding on port 7 and 9 from router to PC to enable wake on wan. However it's not working with Mullvad on. It works if Mullvad is off. I have enabled the local network sharing setting in the app and it's working. One evidence is that I can log in to router management page with Mullvad on.

I know Mullvad removed the support for port forwarding already. But I am not sure whether that includes LAN port forwarding too. This issue has been discussed before (for example #4012). Looking from @pinkisemils's comment, it seems like incoming traffic from LAN should be allowed. So this created more confusion outside whether LAN port forwarding is supported.

Lastly, looks like adding rules to allow incoming traffic will fix the issue. However the current solution is only for Linux. I tried to translate that to Windows 10 but that wasn't successful. Would love some help. Thanks.

[faern]

When you port forward from your router to your PC, the source IP of the packets being forwarded to your PC will be untouched (most likely, depending on router setup). This means that if you send WoL packets from the internet/outside the LAN they will not match the rules allowing LAN traffic. Have you tried sending WoL-packets from within the LAN and see if that works?

I know Mullvad removed the support for port forwarding already. But I am not sure whether that includes LAN port forwarding too

These are two completely unrelated things. We removed the ability to let a random port on our exit relays be forwarded to users through the VPN. Whatever you set up on your LAN etc is something else.

[luojiesi]

Thanks for the information. I don't have access to the PC now. Let me try waking up from lan in a few weeks.

[pinkisemils]

Just to understand this right, you're trying to send a WoL packet over the internet? Have you tried using the vanilla WireGuard client to see if it's our firewall rules or routing that prevent the WoL packet from being received? I struggle to imagine that the Windows firewall will be used to evaluate if a WoL packet should be rejected when the machine is asleep, but I've been wrong about weirder things before 🤷 .

[MarkusPettersson98]

Any update on this? @luojiesi

[Rawa]

Closing issue as stale