I am hoping someone with multi wan experience can help us. I believe its down to routing.
So we have 3 WAN's in operation, see our diagram attached, the copy monitors all sorts of different types of alarms and also has a phone app you can use to turn your alarm on and off.
Some alarms use TCP, some UDP. With NZ having a massive weather event at the start of the year, a Starlink was purchased as an additional WAN. It runs a business account and has a public/static ip address. Public address is 126.96.36.199
So initially when we turned the Starlik on, we had Alarms using UDP not polling successfully, they were coming from clients who had Alarms and also running Starlink connections, the client IP's are DHCP assigned by Starlink and for example could be 188.8.131.52 and 184.108.40.206. I setup some routing rules. The Alarms typically come thru Port 2 or Port 3 WAN connections. One as a primary and one as a backup.
Port 3 is where the Phone app would connect to. The phone app uses HTTPS.
So a rule was set for those alarm products and phone app to route the traffic for Port 3 connection, under Configure>Routing>SD-Wan Routes.
The Rule would identify the Server IP and force any traffic out of a Primary WAN or secondary WAN.
For example when a client connects there mobile phone to there Starlink home wifi and trys to use the app from the IP's 220.127.116.11 and 18.104.22.168 for example, they are unable to log into the phone app, if they switch there phone to 4G cell internet then it connects.
So I think there is a routing issue of some kind. I have tried routing rules where it trys to cover any destination traffic.
We did try and setup an additonal WAN in the past and had similar issues with another provider, we ended up just using it double nated for a while so not to disrupt traffic.
[edited by: Raphael Alganes at 5:44 AM (GMT -7) on 14 Sep 2023]