Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 24 replies
  • Answers 2 answers
  • Subscribers 9 subscribers
  • Views 58053 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

115w - WiFi failing every day after firmware update

ipzipzap

Hello,

I am running a 115w on 9.411-3 with the internal WiFi at 2.4GHz and bridged to AP LAN for over a year now with no problem at all, but since about one week I have noticed that the wifi keeps failing almost every day on almost the same time (19:00-21:00 in the evening). Changing the configuration to force the AP to get reconfigured hasn't helped. The only solution I found is to reboot the whole device.

The only thing I did in the past was the firmware updates, so I blame Sophos for it. Has anyone noticed problems with one of the latest firmwares and the internal WiFi?

If necessary I can provide my logs.

 

Any help would be greatly appreciated.

Dino



This thread was automatically locked due to age.
  • 0 in reply to Humberto Garcia

    Hi, Humberto - you've apparently been around for awhile, but welcome to the UTM Community!

    Thanks for sharing that!

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to Humberto Garcia

    Humberto Garcia said:

    Had same issues and found in a German forum to add athk9 (my case) or athk10 to /etc/modules file and reboot unit....

    working fine now on 9.5...

     
    Many thanks Humberto, 
     
    will give this a shot...
  • 0 in reply to R V

    R V said:

    The upgrade (Up2Date) to UTM 9.500-9 earlier this week (May 8, 2017) has completely broken WiFi on my SG-115w:

    ... 

    Anyone else experiencing similar issues? I'm still investigating, will post findings here.

     

    Yes. I did the update today and can confirm that 9.500-9 has also broken the WiFi in my SG115w.

  • 0 in reply to ipzipzap

    I had the same issues when upgrading to 9.5 on my SG105W. 

    I tried to add both athk9 and athk10 with no success. 

     

    After looking in the Active Access Points list, I could see my AP listed as "ath9k", instead of "athk9"

     

    After adding ath9k to the /etc/modules file, followed by a reboot, my WLAN came back to life. 

    // Sophos UTM Certified Architect

  • 0 in reply to ØyvindErga

    Same here:

     

    So it seems that the root cause of this bug is a simple typo. 

    I will not add it manually to /etc/modules and wait for a new firmware. Luckily I also have an AP30 which I can use until there is an update.

     

  • 0 in reply to ipzipzap

    Ok, ath9k is correct. It's the Linux driver for Atheros 802.11n PCI/PCI-E devices

    https://wiki.debian.org/ath9k

    Maybe Umberto just had a typo in his post.

  • 0

    Adding those lines did not work for me.

    With two external AP and the internal AP all on one bridged interface, any devices that connect to the internal AP do so successfully but then can't connect to the Internet, even though they are connected to the internal AP. VERY ANNOYING SOPHOS!

    Devices that connect to the external APs do so successfully and then do connect to the Internet normally as expected.

    Everything was working fine but then 9.50 BROKE it!!! I had to just remove the Internal AP from the SSID and WAIT until this gets fixed.

    I'm not even sure if these 2 problems are related but does anyone know if 9.502004 released today 7/18/2017 fixes either/both?

    These were the fixes:

    Fix [NUTM-6950]: [WiFi] APs displayed as inactive in WebAdmin while clients connect to SSIDs which are still being broadcasted
    Fix [NUTM-7495]: [WiFi] Wireless client IP in Webadmin not updated after changing the SSID
    Fix [NUTM-7962]: [WiFi] Split traffic not working for wireless clients on RED15w after upgrade to v9.5

    Best Regards - HTG
    Frustrated Sophos Partner seeing all the things
    that brought me to Sophos slowly slip away.
    RIP astaro.org

  • 0 in reply to Humberto Garcia

    I'm glad this works for you but it doesn't work for me.

    I have tried all the items in the below article even though I did have everything set up in the 1st place.

    How to configure the UTM SG-W series internal wireless card with Bridge-to-LAN

    https://community.sophos.com/kb/en-us/122080

    I've got a bunch of these units that were upgraded to 9.5 and they are now all broken. I opened a case with Sophos support and the only theory they had was to try adding the wireless devices to the /etc/modules file. In other words they don't have a clue but they recommended your suggestion.

    All they would confirm was that they broke their own piece of hardware with their own software and they have not got a fix yet. The tech was hoping that it will be in the next 9.5 up2date release in the next 2 or 3 weeks.

    In the meantime can you or Bob or any of the other UTM super techs offer me some other suggestions on how this thing might be made to work or is downgrading to 4.9 or waiting out their malfeasance the only true options?

    Best Regards - HTG
    Frustrated Sophos Partner seeing all the things
    that brought me to Sophos slowly slip away.
    RIP astaro.org

  • 0 in reply to htguru

    I've read that adding the ath9k to modules isn't enough.

    Edit:

    /etc/hostapd/hostapd.conf-default

    look for:

    ht_capab = [<HT_CAPAB>]

    change to:

    ht_capab = [<HT40 +>] [<SHORT-GI-40>] [<TX-STBC>] [<RX STBC1>] [<DSSS_CCK-40>]

    then edit:

    /etc/modules

    add:

    ath9k

    Restart the MDW services using "/etc/init.d/mdw restart"

    I had not had a chance to try this yet but if you already have the 9.5x release then it's worth it to try.

    Update:

    After trying the above procedure on my own UTM, it didn't work initially. Found another post on Sophos Community with the following ht_capab:

    ht_capab=[HT40+][SHORT-GI-40][TX-STBC][RX-STBC1][DSSS_CCK-40]

    After a reboot, wifi is back up and running.

  • 0 in reply to Exp3371

    Thanks Exp3371.

    Seems worth a try.

    Can you link us to where you read this from further reading?

    Also, Can anyone explain what this actually doing?

    Also, can anyone confirm success after having tried this?

    Best Regards - HTG
    Frustrated Sophos Partner seeing all the things
    that brought me to Sophos slowly slip away.
    RIP astaro.org

Unfiltered HTML