Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

WAN/Internet failover confusion and Starlink

I've got our firewall (XGS2100) connected to 2 Internet connections. One is a local wireless internet provider we've been using for years (as its a very good deal) and recently a Starlink connection to replace the woeful DSL and 4G connections.

I had the Starlink tested by itself, routed to my dekstop alone with an SD-WAN route, and it worked flawlessly for 2 months. No issues at all. I removed the DSL and 4G from the existing failover and added in the Starlink connection. I tested it by physically unplugging each connection and noted using Speedtest.net that indeed my connection had shifted from one ISP to another. Great.

Lately though I'm noticing that after the overnight reboot that Starlink likes to do for whatever reason, the failover doesn't work any more. The firewall will report reasonable ping/jitter/loss times as expected and give it the green light, but when asked to take over by the firewall there's no Internet connection on any computer on the network. I forcing my desktop to Starlink doesn't work either, in the same SD-WAN configuration I had when I was testing it.

I have literally just now gone and unplugged the Starlink router, waited 10 seconds, plugged it back in, and the manual SD-WAN route to my desktop is working again. I can choose the Starlink or wireless and they both work fine.

It is only a residential Starlink connection (it's a small business) and not on a static IP, is the IP change overnight causing issues? I've yet to fully determine if I'm actually seeing an IP change, i have noted today's IP and will see what happens. But it does change rather frequently, certainly more often than my dynamic IP on my home connection.

I do have an active case on this (07442319) but I'm just throwing it out there to see if anyone else has had a similar experience?



This thread was automatically locked due to age.
Parents
  • Hello,

    Incase if the issue occurs again, kindly take observation of below steps:

    1. Perform Arp ping using command

     console>system diagnostics utilities arp ping interface Port2 172.16.16.1

    Here, Port2 should be WAN interface and 172.16.16.1 is gateway IP address.

    If this does not fix, go ahead and perform step 2.

    2. Go to the Network -> Interface -> Edit the Starlink interface and save.

    Mayur Makvana
    Technical Account Manager | Global Customer Experience

    Sophos Support Videos | Knowledge Base  |  @SophosSupport | Sign up for SMS Alerts |
    If a post solves your question please use the 'Verify Answer' button.

Reply
  • Hello,

    Incase if the issue occurs again, kindly take observation of below steps:

    1. Perform Arp ping using command

     console>system diagnostics utilities arp ping interface Port2 172.16.16.1

    Here, Port2 should be WAN interface and 172.16.16.1 is gateway IP address.

    If this does not fix, go ahead and perform step 2.

    2. Go to the Network -> Interface -> Edit the Starlink interface and save.

    Mayur Makvana
    Technical Account Manager | Global Customer Experience

    Sophos Support Videos | Knowledge Base  |  @SophosSupport | Sign up for SMS Alerts |
    If a post solves your question please use the 'Verify Answer' button.

Children
No Data