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

Thread Info
  • State Verified Answer
  • +10 person also asked this people also asked this
  • Locked Locked
  • Replies 82 replies
  • Subscribers 61 subscribers
  • Views 50702 views
  • Users 0 members are here
Options
Suggested
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

[BUG] XG v16/17 PPPOE doesn't endlessly tries to reconnect

guillaume bottollier

Hi All,

i have a weird issue concerning clients with xDSL lignes, with a modem bridged and connected to wan port of the XG.

There are more and complains about internet failures (different clients, different DSL providers, different modems), and in most of the cases the pppoe Wan port status is "Disconnected".

Just by clikcing on "connect" connection goes up immediatly !

Is there a way to force the XG to retry enlessly to reconnect ?! (which should be a basic thing !!!!)

Thanks !



This thread was automatically locked due to age.
Parents
  • 0

    I now have another customer who is having this issue. They run a XG135 with V18.0.1 MR1. 

    The Sophos unit has worked perfectly for 3 years now, until about 1 month ago.

    This unit is doing PPoE through a 50Mbps Fibre service.

    The unit is in a COVID lockdown in Melbourne Australia, and all the staff are working from home through this unit via SSL VPN. 

    There is no one in the office to restart it, so I have to rush into the city to press the CONNECT button. This has happened twice in 24 hours.

     

    The unit has a 4G WWAN USB dongle on it, exactly for this type of issue. However, when this fault occurs the 4G link is NOT started up.

    I don't have any issues with other Sophos unit on ADSL or EFM connections with PPoE. I suspect that the issue relates when the PPoE link quickly goes down and up. (1-2 seconds). The PPoE will terminate, but the Sophos unit thinks that the exiting PPoE session is still going. With the slower technologies such as ADSL the link speed is slow, and so the PPoE service does notice the session dying.

    I have open Sophos cases 03041322 and 03041326

  • 0 in reply to Andrew Carra

    This is a concerning development.

    I did see this issue once only on a V18.0.0 unit which I was using for testing, but since upgrading that unit to MR1 396, it has not exhibited the issue again.

     

    Regards,

    Gavin Daniels. DipIT(Networking)

     

     
  • 0 in reply to GavinDaniels

    Gavin,

    My failure this week was with a customer running SFOS 18.0.1 MR-1-Build396.

    So it isn't fixed in this release!

  • 0 in reply to Andrew Carra

    Andrew,

    That is why it is concerning.

    I just got 2 XG125 Rev3 devices which I plan to use as interim staging devices for upgrades to V18. Essentially load their current configuration onto the XG125, default the customers unit and upgrade to V18.0.MR1 and then rewrite the config, as I have experienced issues with the migration on the couple of units I have tested this on, and have ended up reverting to V17.5

     

    Even the upgrade from 18.0.0 to MR1 has butchered the NAT rules attaching some 13 digit number to the descriptions of them all, and completely screwing the name of 1, or it generated a new rule with some self generated name.

    BUT SINCE THERE IS NOT A CONFIGURATION DOCUMENTATION TOOL AVAILABLE FOR SOPHOS XG DEVICES! you either have to screenshot every entry and every change, so you can see what has been done.

    Regards,

    Gavin Daniels. DipIT(Networking)

     

     
Reply
  • 0 in reply to Andrew Carra

    Andrew,

    That is why it is concerning.

    I just got 2 XG125 Rev3 devices which I plan to use as interim staging devices for upgrades to V18. Essentially load their current configuration onto the XG125, default the customers unit and upgrade to V18.0.MR1 and then rewrite the config, as I have experienced issues with the migration on the couple of units I have tested this on, and have ended up reverting to V17.5

     

    Even the upgrade from 18.0.0 to MR1 has butchered the NAT rules attaching some 13 digit number to the descriptions of them all, and completely screwing the name of 1, or it generated a new rule with some self generated name.

    BUT SINCE THERE IS NOT A CONFIGURATION DOCUMENTATION TOOL AVAILABLE FOR SOPHOS XG DEVICES! you either have to screenshot every entry and every change, so you can see what has been done.

    Regards,

    Gavin Daniels. DipIT(Networking)

     

     
Children
No Data
Unfiltered HTML