In trying to solve a problem with a nintendo Switch Lite and NAT-PNP / UPnP (see UPnP port forwarders for VLan gateways ) I ended up solving it a using NAT Mapping rule.
However, I was still getting weird behavior, and I realized there’s something unexpected about NAT Mapping.
Here is my setup:
And when using this setup, you can see that outgoing traffic is going out on WAN2:
This is very unexpected to me: Isn’t the entire point of NAT Mapping to lock one device to one IP address?
I solved this by adding a second Outbound Policy rule to force that specific IP address to use only WAN1:
And now it works.
However, this seems weird - why cant I simply disable WAN2 using the NAT Mapping UI? Why do I have to add this second rule?
It seems a simple solution would be to give a “None” option on the popup menu for Outbound connections inside the NAT Mapping UI.