Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 33 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 42016 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

AP55 - WLAN interruption every x minutes since firmware 11.0.014

DanielGl�ser

Hello,

since I installed the firmware 11.0.014 the network interrupts every x minutes.


Behavior:
The SSID is not visible for 1-2 seconds and all devices disconnected.

Does anyone have an idea? Is a downgrade of the firmware possible? 

I have added the device completely new to Sophos XG

awed.log:

2020-10-22 23:00:21 [A4002D6F0FD716C] device not authorized yet, dropping.
2020-10-22 23:00:35 [MASTER] start processing configuration change
execute_command_tcp: read(): Interrupted system call
execute_command_tcp: read(): Interrupted system call
2020-10-22 23:00:42 [MASTER] AP A4002D6F0FD716C: Local metadata updated
2020-10-22 23:00:42 [MASTER] AP A4002D6F0FD716C: Configuration change detected
2020-10-22 23:00:42 [MASTER] end processing configuration change
2020-10-22 23:00:42 [MASTER] start processing configuration change
2020-10-22 23:00:49 [MASTER] end processing configuration change
2020-10-22 23:00:49 [MASTER] start processing configuration change
2020-10-22 23:00:56 [MASTER] end processing configuration change
2020-10-22 23:00:56 [MASTER] new connection from 192.168.0.46:59060
2020-10-22 23:00:56 [MASTER] new connection from 192.168.0.46:59061
2020-10-22 23:00:56 [A4002D6F0FD716C] AP55 from 192.168.0.46:59060 identified as A4002D6F0FD716C
2020-10-22 23:00:56 Could not read from file '/tmp/awed/A4002D6F0FD716C.pid': No such file or directory
2020-10-22 23:00:56 [A4002D6F0FD716C] AP55 from 192.168.0.46:59061 identified as A4002D6F0FD716C
2020-10-22 23:00:56 Could not read from file '/tmp/awed/A4002D6F0FD716C.pid': No such file or directory
2020-10-22 23:00:56 [A4002D6F0FD716C] (Re-)loaded identity and/or configuration
2020-10-22 23:00:56 [A4002D6F0FD716C]The connection is closed.
2020-10-22 23:00:56 [A4002D6F0FD716C] error while writing to socket, dropping.
2020-10-22 23:00:56 [A4002D6F0FD716C] (Re-)loaded identity and/or configuration
2020-10-22 23:01:30 [MASTER] updating DB for AP A4002D6F0FD716C with new channels (0,0 -> 6,100)

Best regards



This thread was automatically locked due to age.
  • 0 in reply to Daniel Luyckx

    Hi Daniel,

    that was my issue with the AP55s Apple devices would sit between 6mb/s and 24 mb/s. They would ramp up if under a sustained load. I raised this issue a number of years ago and got no positive answers. It is not an issue on 2.4ghz. I thought it was an apple power saving issue because my w10 devices all run high connection speeds. Since moving to the APX120s the apple devices regular connect at over 100mb/s when sleeping and around 300-600 when active on the 5ghz band.

    it is a very poor design as far as I can determine. At one stage I pulled an AP50 apart and was not impressed with the quality.

    ian

  • 0 in reply to rfcat_vk

    Hello rfcat,

    For me the performance is okay. With my iPhone I also get >200mb/s.
    Our main problem is that after a few minutes all devices are disconnected from the AP for 1-2 seconds.

  • 0 in reply to Daniel Luyckx

    So.. Cables are reseatet, everything multiple times restarted, Sophos Firmware rolled back and updated again, Accesspoints were deleted and readded, Accesspoints were activated only partically... I dont know where the Problem is, for me it can be almost only in the Firmware of the Access points..

  • 0 in reply to DanielGl�ser

    The Problem was, that we used special letters in our SSIDs (Gäste instead of Gaeste, so a Ä as special letter).

    The Incompatiblity is there since the Firmware Upgrade from 012 to 014.

    Greetings

  • +1

    The Problem was, that we used special letters in our SSIDs (Gäste instead of Gaeste, so a Ä as special letter).

    The Incompatiblity is there since the Firmware Upgrade from 012 to 014.

    Greetings

  • +1 in reply to Daniel Luyckx

    Hi All, following up with Daniel's resolution.

    As mentioned, this issue is related to the use of special characters in the SSID. As a result, frequent disconnections may occur. I'm following up with the team to gather more information as to when this issue will be fixed.

    In the meantime as a workaround please note the following:  

    1. Avoid the use of special characters
      1. Ex: -, _, =, +
    2. Avoid using umlaut characters in SSID names
      1. ä, Ä , etc.
  • 0 in reply to FloSupport

    even "-" should be avoided? I guess this hits a lot of customers, us included.

    Having permanently restarting radios due to WPA2 Enterprise with RADIUS with 11.0.012, waiting for a fix and the (probably) fixed firmware 11.0.014 has an other bug that lets SSIDs restart due to "special" characters like the commonly used -

    Then at the same time there was the issue with unsupported spaces in the SSID name, also causing restarting radios in loop. Something that any consumer WiFi router that I know is capable of.

    What's going on with the WiFi product development?

  • 0

    Hello All,

    The fix for this issue is tentatively scheduled to be included in the next pattern update. More information to come soon.

    Regards,

  • 0 in reply to FloSupport

    Hi folks,

    having removed the '-' from my SSIDs appears to have fixed connection issues with  5ghz SSIDs. I have not checked the 2.4ghz SSIDs yet.

    ian