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-wtpReasonDeauthenticated 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) BSSNominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
I am having the same issue with the FAP 321C, I have few of them standalone.. Did you find any solutions?
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
Action | client-leave-wtp |
Reason | Disassociated because sending STA is leaving (or has left) BSS |
2024-03-13 | 07:46:02 | logid="0104043574" | logdesc="Wireless client disassociated" | channel=165 security="WPA2 Enterprise" | encryption="AES" | action="disassoc" | reason="Reserved 0" |
2024-03-13 | 07:46:02 | logid="0104043574" | logdesc="Wireless client disassociated" | channel=165 security="WPA2 Enterprise" | encryption="AES" | action="disassoc" | reason="Reserved 0" |
2024-03-13 | 07:41:59 | logid="0104043574" | logdesc="Wireless client disassociated" | channel=165 security="WPA2 Enterprise" | encryption="AES" | action="disassoc" | reason="Reserved 0" |
2024-03-13 | 07:41:59 | logid="0104043574" | logdesc="Wireless client disassociated" | channel=165 security="WPA2 Enterprise" | encryption="AES" | action="disassoc" | reason="Reserved 0" |
2024-03-13 | 07:41:25 | logid="0104043574" | logdesc="Wireless client disassociated" | channel=132 security="WPA2 Enterprise" | encryption="AES" | action="disassoc" | reason="Reserved 0" |
2024-03-13 | 07:41:25 | logid="0104043574" | logdesc="Wireless client disassociated" | channel=132 security="WPA2 Enterprise" | encryption="AES" | action="disassoc" | reason="Reserved 0" |
2024-03-13 | 07:41:15 | logid="0104043574" | logdesc="Wireless client disassociated" | channel=165 security="WPA2 Enterprise" | encryption="AES" | action="disassoc" | reason="Reserved 0" |
2024-03-13 | 07:41:15 | logid="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> |
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.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1633 | |
1063 | |
751 | |
443 | |
210 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.