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

WLAN willkürliche Verbindungsabbrüche (deauthenticated due to inactivity) - SSID Sonderzeichen

Hallo zusammen,

 

ich habe die letzte Zeit (vermutlich aber schon länger existent) ein etwas merkwürdiges Verhalten im WLAN beobachtet.

Und zwar kam es hier (auch bei Android - Geräten) immer wieder mal zu kurzen Abbrüchen der Verbindung, teilweise kaum zu bemerken; wo ich es nun allerdings verstärkt bemerkt habe, das war, wenn ich mit dem Windows 10 Notebook via RDP oder auch Teamviewer hier intern im Netz auf einem Gerät remote verbunden war. Hier brach dann einfach die RDP Session ab; das WLAN aber war laut Windows weiterhin verbunden.

Beim Android Handy konnte ich es vermehrt schon beobachten, dass während dem Surfen einfach kurz die WLAN Verbindung abbricht und direkt wieder neu aufbaut.

Also habe ich mir mal die Wireless Logs angeschaut und konnte dort seitenweise das folgende beobachten:


2020:07:07-00:58:51 A400259E76BFF80 hostapd: wlan2: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
2020:07:07-00:59:15 A400259E76BFF80 hostapd: wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
2020:07:07-00:59:34 A400259E76BFF80 hostapd: wlan0: STA yy:yy:yy:yy:yy:yy IEEE 802.11: disassociated due to inactivity
2020:07:07-00:59:35 A400259E76BFF80 hostapd: wlan0: STA yy:yy:yy:yy:yy:yy IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)

 

Nun habe ich etwas gegooglet und auch etwas gefunden; es scheint so, als würde es wohl ein Problem mit Sonderzeichen innerhalb der SSID geben.

Allerdings war der Thread bereits von ca 2015, also hätte man hier eher annehmen können, dass dieses ursprüngliche Problem zwischenzeitlich behoben sein könnte.
Dem scheint aber nicht so zu sein, denn ich habe nun mal Sonderzeichen (es handelte sich um ein Ausrufezeichen) aus den SSIDs entfernt und seitdem ist das Problem nicht mehr aufgetreten; davor war es mit den RDP Abbrüchen ca. alle 10-15min der Fall.

Komischerweise findet man im Web nicht allzu viel zu diesem Thema...


Ich werde das mal weiter beobachten.


Beste Grüsse,
Andy



This thread was automatically locked due to age.
  • Abschliessend kann ich nun zwischenzeitlich sagen, dass die Abbrüche seit der Entfernung der Sonderzeichen aus der SSID nicht mehr vorgekommen sind.

    Seitdem läuft das WLAN einwandfrei, also lag es hiermit wohl echt an den Sonderzeichen innerhalb der SSID.

  • Hello Zusammen,

    Thank you for contacting the Sophos Community

    What UTM Firmware are you running?

    Do you happen to have the link to the thread you mention?

    I will try to replicate this issue anyway. I created the following SSID SS!Dforu and left a ping and a remote session running. 

    I let you know my findings and if the issue is the same I can report to GES.

    Regards,


     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support VideosProduct Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
  • Also hello and thank you for replying. :)

     

    I am running 9.702-1 but the problem I have a longer time before. I don't know how long exactly but sometimes I recognized suddenly disconnects on my mobile phone - which is solved now.

     

    One of my old SSIDs was like "SuraKaes!" also the second one had the "!" at the end. 

    There are an AP55 and an AP100 in use.

  • here two threads according to that failure and ssid special characters:

    https://community.sophos.com/products/unified-threat-management/f/hardware-installation-up2date-licensing/30268/wireless-ap55-crashing

    https://community.sophos.com/products/unified-threat-management/f/wireless-security/56538/wpa2-authentication-failures

     

    ...not excatly the same, but similar to. ;)

    Since removing special characters it seems to be solved and works without any interruption.

  • Hello ND,

    Thank you for the follow up!

    Yesterday I tried to replicate, but I didn't get any disconnection, but maybe it was because I didn't put the ! at the end of the SSID, so I will be doing  that today.

    May know exactly the SSID you use.

    Regards,


     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support VideosProduct Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
  • Yes, also my idea that the sign at the end could cause that behavior.

    The exact ssid was "Floischsalat!"

    Thanks :)

  • Lustig - Du bist ein Witzbold !  Do I recognize that as a Wienerisch accent?

    MfG - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • You are not so bad, it's an accent called "schwäbisch" from the south of germany. But maybe Floischsalat is also known in "wienerisch", austrian sometimes sounds similar... But more in the regions near Bayern, Baden Württemberg and near behind the border.

    Floisch = Fleisch = Meat

  • My fencing (Fechten) coach in Berlin was from Wien and could speak with the accent of the street there.  I remembered him saying Floisch instead of Fleisch.  In Berlinerisch, it's Fläsch.

    Cheers - Bob 

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Hello Nd,

    I actually haven't been able to replicate exactly! Or at least I don't see the same log as yours.

    Just another question do you see anything or did you happen to see any logs like the following:

    2020:07:27-17:37:00 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d MLME: MLME-DELETEKEYS.request(f8:2d:7c:93:35:4d)
    2020:07:27-17:37:01 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
    2020:07:27-17:37:01 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
    2020:07:27-17:37:01 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d MLME: MLME-DEAUTHENTICATE.indication(f8:2d:7c:93:35:4d, 2)
    2020:07:27-17:37:01 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d MLME: MLME-DEAUTHENTICATE.indication(f8:2d:7c:93:35:4d, 2)
    2020:07:27-17:37:01 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d MLME: MLME-DELETEKEYS.request(f8:2d:7c:93:35:4d)
    2020:07:27-17:37:01 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d MLME: MLME-DELETEKEYS.request(f8:2d:7c:93:35:4d)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d IEEE 802.11: authentication OK (open system)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d IEEE 802.11: authentication OK (open system)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d MLME: MLME-AUTHENTICATE.indication(f8:2d:7c:93:35:4d, OPEN_SYSTEM)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d MLME: MLME-AUTHENTICATE.indication(f8:2d:7c:93:35:4d, OPEN_SYSTEM)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d MLME: MLME-DELETEKEYS.request(f8:2d:7c:93:35:4d)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d MLME: MLME-DELETEKEYS.request(f8:2d:7c:93:35:4d)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: AP-STA-AUTH f8:2d:7c:93:35:4d0
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d IEEE 802.11: authenticated
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d IEEE 802.11: authenticated
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d IEEE 802.11: association OK (aid 3)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d IEEE 802.11: association OK (aid 3)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: AP-STA-ASSOC f8:2d:7c:93:35:4d0
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d IEEE 802.11: associated (aid 3)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d IEEE 802.11: associated (aid 3)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d MLME: MLME-ASSOCIATE.indication(f8:2d:7c:93:35:4d)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d MLME: MLME-ASSOCIATE.indication(f8:2d:7c:93:35:4d)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d MLME: MLME-DELETEKEYS.request(f8:2d:7c:93:35:4d)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d MLME: MLME-DELETEKEYS.request(f8:2d:7c:93:35:4d)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d WPA: event 1 notification
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d WPA: event 1 notification
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d WPA: start authentication
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d WPA: start authentication
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d IEEE 802.1X: unauthorizing port
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d IEEE 802.1X: unauthorizing port
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d WPA: sending 1/4 msg of 4-Way Handshake
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d WPA: sending 1/4 msg of 4-Way Handshake
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d WPA: received EAPOL-Key frame (2/4 Pairwise)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d WPA: received EAPOL-Key frame (2/4 Pairwise)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d WPA: sending 3/4 msg of 4-Way Handshake
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d WPA: sending 3/4 msg of 4-Way Handshake
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d WPA: received EAPOL-Key frame (4/4 Pairwise)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d WPA: received EAPOL-Key frame (4/4 Pairwise)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: AP-STA-CONNECTED f8:2d:7c:93:35:4d
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d IEEE 802.1X: authorizing port
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d IEEE 802.1X: authorizing port
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d RADIUS: starting accounting session 5F1B72D2-0000000F
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d RADIUS: starting accounting session 5F1B72D2-0000000F
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d WPA: pairwise key handshake completed (RSN)
    2020:07:27-17:37:08 utm1 hostapd: wifi0: STA f8:2d:7c:93:35:4d WPA: pairwise key handshake completed (RSN)


     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support VideosProduct Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.