I don't think you understand the meaning of the word

[rbuckthal]

'Enforced".

I have a network ‘Enforced’ to a WAN, yet I continue to see traffic on a different WAN.

Yet there is traffic on not the ‘Enforced’ WAN!!

Just what does Enforced mean?

Roger

[MartinLangmaid]

If it wasn’t specifically IPSEC traffic I would say that it was likely the session traffic existed before rule was applied - in which case you need to break the sessions somehow so that when they are recreated the outbound policy kicks in.

As its IPSEC its much more likely that you hve IPSEC NAT-T enabled in Network > Misc Settings Service Passthrough. Go there and put a check in the Route IPsec Site to site VPN box and pick the WAN you want the NAT-T to be applied to.

[jmjones]

good old UDP port 4500. It has something to do with SIP. Peplink puts that on whatever is on WAN1. Here is a thread that discusses it and how to move it to the other WAN

M-cell config - UDP 4500

I have an AT&T M-Cell. It seems to want to use port 4500 UDP, but I see that other devices besides that M-Cell are able to use that port at the same time. I have an enforced outbound policy by Source IP for port 4500 UDP for WAN2, yet I have seen this device with its connection on WAN1. I have now set the enforced policy to just Source IP, and I continue to find this M-Cell device with an Active session from it to the internet on WAN1. How is that happening? Whatever is going on is possibly ca…

[cgreen]

Try the passthrough setting as Martin suggested it may well cure the problem.

Recently I had a similar issue even with the default policy rule to send all traffic down the PEPVPN, I was still seeing traffic breaking out locally on cellular connections.

That was until I created a custom rule to catch ESP protocol traffic and force that down the tunnel, it then resolved the issue I had but I would try what Martin has suggested first.