This is not new in b2422 - but I have only just now sat down to sort it out. Balance 30.
outbound policy says all traffic to go out WAN 2 (or 3).
network -> Service passthrough -> IPsec NAT-T set to enable, and default ports.
problem: Peplink always does the initial IPsec NAT-T on WAN 1, and ignores outbound policy rules, but then follows the rules later on, and breaks the connection due to WAN n change.
Client starts IPSec/L2TP connection;
Client sends out initial port 500 UDP keysetup packets. Error Starts here: Peplink should send this per outbound policy rule (WAN2), but ignores that and ALWAYS sends initial port 500 packets on WAN 1 every time.
The key exchange succeeds, despite being on wrong WAN.
Client sends out second part exchange now on port 4500 UDP. Error goes fatal: Peplink now does observe Outbound policy rule (WAN2). But the server ends now sees one session split over two IP’s, and it fails.