topic Re: Clients keep getting Disassociated from AP = Reason 8 in Access Points - Indoor and Outdoor

Clients keep getting Disassociated from AP = Reason 8

jason_sparrow — Tue, 13 Oct 2015 10:28:51 GMT

Well, the on-going saga continues.

I have an R600 that for some reason disassociates clients giving 'reason 8' that i found in the web UI log.

Could someone tell me what reason 8 is please?

Also, could someone maybe explain what the AP classes as 'interference'?

I am confused as to why the AP all of a sudden starts to SmartSelect to find a clearer 5G channel when there no other rogue 5G networks anywhere nearby.

Plus, the 2.4G network is perfectly stable and that has plenty of reason to hop about as there quite a fair few nearby networks.

Re: Clients keep getting Disassociated from AP = Reason 8

seanmuir — Tue, 13 Oct 2015 10:40:48 GMT

Reason Codes are here:

http://www.aboutcher.co.uk/2012/07/linux-wifi-deauthenticated-reason-codes/

Reason Code 8 is due to client leaving the BSS by means of AP moving the client to another access point using non-aggressive load balancing.

In regards to Channel selection do you have Channel Fly turned on?

Re: Clients keep getting Disassociated from AP = Reason 8

jason_sparrow — Tue, 13 Oct 2015 10:45:21 GMT

Hi Sean, and thanks.

Interesting about the load balancing as there were only two clients connected at the time to the AP 5G network.

Yes, I have ChannelFly (smart select) turned on for 2.4 & 5 but the 5 just seems to drop everything and jump channel randomly, with no other networks nearby. (After checking, the 2.4 has done it a bit but not as much).

I am using the basic NetSpot to keep an eye on whats going on, and im the only 5G network that even gets picked up by that. This is why im wondering why the AP is channel flying.

Re: Clients keep getting Disassociated from AP = Reason 8

seanmuir — Tue, 13 Oct 2015 10:56:01 GMT

Is this a home network?

Re: Clients keep getting Disassociated from AP = Reason 8

jason_sparrow — Tue, 13 Oct 2015 10:57:34 GMT

Yes it is.

Re: Clients keep getting Disassociated from AP = Reason 8

seanmuir — Tue, 13 Oct 2015 11:09:39 GMT

The way Channel Fly works is that it is always trying to find the best channel to deliver throughput to the client by using predictive capacity management.

You can alter the mean time between channel changes using this cli command:

set channelfly wlan0 mtbc 500

In my opinion I would turn off Channel Fly is it can be destructive in nature to certain clients; I have a home network which is all Ruckus, and I don't use Channel Fly as my Sky Box does not like it.

Re: Clients keep getting Disassociated from AP = Reason 8

jason_sparrow — Wed, 14 Oct 2015 19:18:23 GMT

Thanks Sean,

I have turned off Channel Fly and everything seems to be settled for now.

Its a shame really as i'm sure its a great idea to keep the wifi availability as clean and clear as possible.

With regards to the non aggressive load balancing, would it still perform this even if there were only two clients connected to one AP?

I have noticed a couple of times, that with both near one AP, one has hopped to another but i havent thought about checking the log until recently, or even realised the load balancing feature.

Re: Clients keep getting Disassociated from AP = Reason 8

michael_brado — Thu, 15 Oct 2015 22:37:11 GMT

Channelfly uses all 11 available 2.4G channels, while Background Scanning uses only channels 1/6/11, and should provide ~33% better client throughput.

Using the 'set channelfly wlanX mtbc 200' (mean time between changes) will decrease the frequency that you see APs change channels to avoid interference.

Only if you have clients which don't change channels well (Sky Box?) or VoIP badges, would we recommend turning off Channelfly, or better yet, run CF for a period of hours with default settings, then freeze your APs to those current channels when you disable it.

Client Load Balancing, which tries to equalize the number of clients on the same band of adjacent APs, will never disconnect already connected clients. It will withhold probe responses and association responses from new clients, if the AP already has 20 or more clients connected. Note: Client Load Balancing does not function if less than 20 (default) clients connected to AP radio.

Re: Clients keep getting Disassociated from AP = Reason 8

itdept_head_me — Fri, 16 Oct 2015 00:46:08 GMT

I have the same problem, staff go for lunch and the osx clients show they are connected but they cannot get external access.

16 days of support and counting.... I am NEVER going to buy any more ruckus equipment after this.

Re: Clients keep getting Disassociated from AP = Reason 8

jason_sparrow — Fri, 16 Oct 2015 05:56:30 GMT

Thanks Michael,

I did indeed let the AP's settle on a channel and then manually locked them to those and all seems to be ok so far for the 5G band.

I have left the 2.4G with smart select for now as that is quite stable.

However, surely it would be better for the AP to look for clearer channels before it decides to change?

Its a bit of pain that it decides to hop around and keep disconnecting clients.

Re: Clients keep getting Disassociated from AP = Reason 8

seanmuir — Fri, 16 Oct 2015 09:19:55 GMT

Sky+HD Box: http://www.sky.com/shop/tv/equipment/

Re: Clients keep getting Disassociated from AP = Reason 8

seanmuir — Fri, 16 Oct 2015 09:25:56 GMT

Channel Fly does asses all channels prior to changing.

Here is the feature sheet:

http://c541678.r78.cf2.rackcdn.com/feature-sheets/fs-channelfly.pdf

I have also heard that there is also a new version of Channel Fly coming out soon, who knows what that will bring 🙂

Re: Clients keep getting Disassociated from AP = Reason 8

jason_sparrow — Fri, 16 Oct 2015 09:28:39 GMT

I have just checked the log and its shows a Reason 8 many times, and these are clients on the 2.4G network.

I do not have that many wifi clients in the house so maybe there is a firmware issue?

Just to point out that i had the same issue on the 5G network, and that was with only 2 clients connected.

One of them from the log...

"RuckusAP daemon.warn Eved: STA-DISASSOC-REASON,nimac=2c:f0:ee:06:ab:96,func=ieee80211_recv_mgmt,line=7033,hint=recv disassociate (reason 8),rx_rssi=59,ack_rssi=0,reason=8,freq=2472,chan=13,stats=(841,94534,940,228925)"

Would this show when a client has disconnected from the AP after leaving the house?

Re: Clients keep getting Disassociated from AP = Reason 8

seanmuir — Fri, 16 Oct 2015 09:42:38 GMT

Is this Apple device still in your network: 2c:f0:ee:06:ab:96?

If it is not, then the reason code 8 is purely down to the fact that the STA has "Disassociated because sending station is leaving (or has left) BSS"

Here is an extract from Ruckus Support:

When disconnecting from an AP, what does reason code X mean?

Summary

This article provides insight into the reason codes for why an unsolicited notification management frame of type Disassociation, Deauthentication, DELTS, DELBA, or DLS Teardown was generated for a UE. This article lists the various reason codes along with a basic description.

Question

When disconnecting from an AP, what does reason code X mean?

Customer Environment

The customer operates any WIFI access network, where the 802.11 standard is adhered to by access points and UEs.

Root Cause

An AP may disconnect a UE for any number of reasons. These reasons are provided to the client by way of a reason code supplied in an unsolicited management frame.

Troubleshooting Steps

In a Ruckus AP Support File, note the disconnect reason cited for the particular disconnect in question, for example:

Mar 23 08:54:21 RuckusAP-kla daemon.info hostapd: @@204,clientDisconnect,"apMac"="xx:xx:xx:xx:xx:xx","clientMac"="64:76:ba:98:27:de","ssid"="MySSID",
"bssid"="54:3d:37:d8:9c:a8","wlanId"="49","tenantUUID"="839f87c6-d116-497e-afce-aa8157abd30c",
"apName"="RuckusAP-kla","apLocation"="My Test","clientIP"="10.2.12.2","vlanId"="100",
"radio"="b/g/n","encryption"="None","hostname"="macbookair","firstAuth"="1427100759",
"associationTime"="1427100759","ipAssignTime"="1427100766","disconnectTime"="1427100861",
"sessionDuration"="102","disconnectReason"="8","rxFrames"="305","rxBytes"="21118","txFrames"="85",
"txBytes"="13640","peakRx"="19934","peakTx"="13640","rssi"="25","receivedSignalStrength"="-69",
"Instantaneous rssi"="17","Xput"="0"

In this example, the disconnect was issued due to the sending station leaving (or having left) the BSS (reason code 8):

Resolution

When an Access Point (AP) disconnects a UE, according to the 802.11 standard, it must provide a reason code for why this event took place. Below is a table of the reason code numbers and their associated descriptions.

Outside of the above, what Firmware are you running and how do you have you WLAN configured?

Also please note that just because you see something in the log, does not make it an issue.

I would start with the approach of are you experiencing any connectivity issues (other than what you see in a log), if so then i would start to look at each of the mac addresses that are having the issues

Note: Reason codes are not all bad and Reason Code 8 in my eyes is one of these, as is Reason Code 4.

Re: Clients keep getting Disassociated from AP = Reason 8

jason_sparrow — Fri, 16 Oct 2015 11:52:06 GMT

Hi Sean, thanks for all the information!!

Yes, that particular device has indeed left, however, when i originally posted, this was two clients on the 5G network, with both of them right in front of me with one AP virtually above me on the ceiling.

With regards to the ChannelFly (however, I am using SmartSelect), when i initially had the problem, it was jumping every few minutes to a different channel and disconnecting clients that were associated with it. It was as if the AP had been rebooted (which it hadnt) and was doing the initial scan for the cleanest channel.

Therefore, because i was actually having random reboots i decided to drop the firmware back to 100....128 and so far so good.

Re: Clients keep getting Disassociated from AP = Reason 8

seanmuir — Fri, 16 Oct 2015 12:10:31 GMT

Hi Jason,

No worries, your welcome.

If you are seeing issues where clients are dropping from the AP then that is certainly unusual behaviour.

I cant really offer any comment on the base 100 images, as I only use these to migrate AP's to our SCG and ZD platforms.

Good luck with it all

🙂

Re: Clients keep getting Disassociated from AP = Reason 8

jason_sparrow — Fri, 16 Oct 2015 12:23:11 GMT

Ok thanks anyway!

Re: Clients keep getting Disassociated from AP = Reason 8

michael_brado — Fri, 16 Oct 2015 16:43:41 GMT

Client devices determine when to roam and troubleshooting client connectivity is a common need.

The log message included the key bits "hint=recv dissassociate (reason 8)", so the AP reported
receiving the dissassociate from the client. APs will follow these leaves with a clean-up sending
a dissassociate from the AP the client left (probably a few lines further in your logs).

Regarding 5G behavior specifically, if you live anywhere near a public airport or military base, you
can program your APs to avoid the middle UNII bands that have Radar/DFS associated with them.
APs seeing radar have to change channels and go silent, which can be disruptive for the brief
period.

Avoid this by setting your ZoneDirector's Configure/System, Country Code -> Channel Optimization
to Optimize for Compatibility choice. All 5G wireless clients should have no problem operating on
the channels available for Channelfly/Background Scanning selection, when you have this set.

Re: Clients keep getting Disassociated from AP = Reason 8

jason_sparrow — Sat, 17 Oct 2015 06:19:05 GMT

Thanks Michael,

However, i am running the three in standalone without a ZD so i dont have this option.

Would the Unleashed controller give me this function?

Re: Clients keep getting Disassociated from AP = Reason 8

seanmuir — Mon, 19 Oct 2015 08:11:31 GMT

I would not consider Unleashed at the moment as it is very buggy.