Skip to main content
eastcoastmatt
eastcoastmatt
New Member
July 14, 2020
Question

Help! Clients are getting disconnected. Log says client-leave-wtp

  • July 14, 2020
  • 2 replies
  • 14109 views

We are getting issues with client disconnects. The client is connecting and it seems about 36 seconds later I get client-leave-wtp message in my logs. The specifics are:

Actionclient-leave-wtpReason

Deauthenticated because sending STA is leaving (or has left) IBSS or ESS

 

After about another 36 seconds, the client reconnects. 

This is happening constantly. So far, I've turned off Radio Provisioning, and hard-coded my channels for the access points, but this does not fix the issue. 

I'm seeing this with a bunch of devices, so it's not specific to one particular type of device that I can tell. 

 

I'm also seeing a variation on this of as per below which is a slightly different message. 

Actionclient-leave-wtpReasonDisassociated because sending STA is leaving (or has left) BSS

    2 replies

    paidamouni
    paidamouni
    New Member
    April 7, 2021

    I am having the same issue with the FAP 321C, I have few of them standalone.. Did you find any solutions?

    robertogoaraujo
    robertogoaraujo
    New Member
    March 13, 2024

    I Have a little bit simillar issue. I am using a Fortigate 100F with FortiOS 7.2.7 and FortiAP 231F with version 7.4.2

     

    Radio issues appear to be resolved, but random STAs have been disconnected from WTP. Logs only show that STA is leaving wtp

     

    Actionclient-leave-wtp
    ReasonDisassociated because sending STA is leaving (or has left) BSS

     

    2024-03-1307:46:02logid="0104043574"logdesc="Wireless client disassociated"channel=165 security="WPA2 Enterprise"encryption="AES"action="disassoc"reason="Reserved 0"
    2024-03-1307:46:02logid="0104043574"logdesc="Wireless client disassociated"channel=165 security="WPA2 Enterprise"encryption="AES"action="disassoc"reason="Reserved 0"
    2024-03-1307:41:59logid="0104043574"logdesc="Wireless client disassociated"channel=165 security="WPA2 Enterprise"encryption="AES"action="disassoc"reason="Reserved 0"
    2024-03-1307:41:59logid="0104043574"logdesc="Wireless client disassociated"channel=165 security="WPA2 Enterprise"encryption="AES"action="disassoc"reason="Reserved 0"
    2024-03-1307:41:25logid="0104043574"logdesc="Wireless client disassociated"channel=132 security="WPA2 Enterprise"encryption="AES"action="disassoc"reason="Reserved 0"
    2024-03-1307:41:25logid="0104043574"logdesc="Wireless client disassociated"channel=132 security="WPA2 Enterprise"encryption="AES"action="disassoc"reason="Reserved 0"
    2024-03-1307:41:15logid="0104043574"logdesc="Wireless client disassociated"channel=165 security="WPA2 Enterprise"encryption="AES"action="disassoc"reason="Reserved 0"
    2024-03-1307:41:15logid="0104043574"logdesc="Wireless client disassociated"channel=165 security="WPA2 Enterprise"encryption="AES"action="disassoc"

    reason="Reserved 0

     

    AP received disassociate frame from client <xx:xx:xx:xx:xx:xx>

    do344-itcaucedo
    do344-itcaucedo
    New Member
    April 17, 2024

    As I verified this error, it is because a vlan is configured at the time of creating the SSID. If you proceed to change it, you can use the new SSID that is giving that error.

    Terms & ConditionsAccessibility statement