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 Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 24 replies
  • Answers 1 answer
  • Subscribers 45 subscribers
  • Views 5237 views
  • Users 0 members are here
Options
Suggested

Huawei 3372 LTE stick not working in SFOS 20.0.2 MR-2-Build378

Steven Lew

Hi everyone,

I am using a Huawei 3372 LTE stick on my SG-125 with SFOS for a couple years now. It is configured in DHCP mode as a failover WAN connection when the main connection goes down. Up until now this worked as intended but after upgrading the firmware to SFOS 20.0.2 MR-2-Build378 it does not connect anymore. The error message appearing on connection attempt is:

"The modem doesn t support the configured network adapter method (DHCP)."

Also when on Build 378 i noticed that the dongle is recognized as usb0 additionally to WWAN1 which is not the case on the older version.

I just downgraded the firmware back to SFOS 20.0.1 MR-1-Build342 to confirm and it is working again.

Please tell me if you need more info.



Edited TAGs
[edited by: emmosophos at 5:33 PM (GMT -7) on 12 Sep 2024]
Parents
  • 0

    Hi All,

    We confirm we are seeing this issue too, its taken us a little to narrow it down and confirm our suspicions. 

    We have been using Huawei E3772 sticks configured to present as 12D1:1506 or 12D1:14FE for many years across our fleet of XG (various Gen's) and XGS (Gen 1) units.

    We recently started to upgrade some customers through the V20 MR's and some to 20.0.2 and in that process, we believed we lost access to the dongles on upgrade so paused our rollout.

    We had a XGS108 arrive today, and it confirmed our suspicions straight out of the box.

    XGS108 arrived with SFOS 20.0.1 MR-1-Build342
    We connected our stick and it worked
    Upgraded to 20.0.2 MR-2-Build378 and it failed.
    We also upgraded to SFOS 21, and it is still failed.

    We now have this confirmed this on an XGS87, XGS116 and XGS108.

    We have an order open with out disti for 50 XGS, but have it on hold until this issues resolved.  Our experience with the SOPHOS modules have been disappointing for both reception and SOPHOS support (our mobile carriers not listed as supported, so they just close the cases!), so we don’t particularly want to transition to the 5G modules as our dongles have been very reliable to date.

    I haven’t yet logged it with support, but will do so on Monday.

  • 0 in reply to Andrew Hurl

    Hello there,

    Adding to what Raphael has mentioned when opening the case, please mention NC-142427, as it looks like you’re being affected by this.

    DEV would need to confirm if you’re affected by NC-142427, but if that is the case, DEV is currently testing a fix.

    Regards,

     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support Videos | Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
  • 0 in reply to emmosophos

    I've also logged the issue (case# NC-142427) as its affecting half a dozen or so customers running XGS125 and XG126.

    Below is an excerpt from the reply received from Sophos support today.

    "The issues with ... not working with SFOS 20.0.2 is still being investigated by our DEV team and on the process of testing a fix.

    To get the latest updates for this issue, you may reach out to Sophos Support by referring to the case or checking the updates in the Sophos Community(this post specifically)
     

    • Will the issue be fixed in the next release of SFOS?
      • For now, we cannot confirm if the issue will be fixed in the next release of SFOS. To check if any issues are resolved on a specific SFOS version, you can refer to the Sophos Release Notes page (Sophos release notes)"

    With the impact to customers in either a) knocking out their internet connection failover, or b) running out-of-date firmware to retain it, you'd think Sophos will get it resolved next release.

  • 0 in reply to Tim Laurie

    Maybe be even create a hot fix outside of a planned MR update.

    Ian

    XG115W - v20.0.3 MR-3 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to Tim Laurie

    Our case was escalated to the GES 2 days ago, expecting an update today.

  • 0 in reply to Andrew Hurl

    Update just in: The issue of WWAN not working after upgrading to v20.0 MR-2 is being discussed with the development team with the reference number below. It seems like a known issue based on the logs and development team is already working on it.
     

    Development reference number:

    NC-142427

    Current Status:

    Escalated to Development

    Issue type:

    Investigation 


    Your issue has been escalated to our development team with the above reference number. Issues are prioritised based on severity and customer impact. We will discuss your case with development and provide preliminary analysis and next steps by Nov 13, 2024.

Reply
  • 0 in reply to Andrew Hurl

    Update just in: The issue of WWAN not working after upgrading to v20.0 MR-2 is being discussed with the development team with the reference number below. It seems like a known issue based on the logs and development team is already working on it.
     

    Development reference number:

    NC-142427

    Current Status:

    Escalated to Development

    Issue type:

    Investigation 


    Your issue has been escalated to our development team with the above reference number. Issues are prioritised based on severity and customer impact. We will discuss your case with development and provide preliminary analysis and next steps by Nov 13, 2024.

Children
Unfiltered HTML