Clients keep getting Disassociated from AP = Reason 8

[jason_sparrow]

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.

[michael_brado]

Hi Sean, if you have any negative experience on Unleashed to lead you to think it's "buggy", can you please open a ticket with Tech Support?
What "problems" have you seen please, with how many APs in what type of physical environment?  With all type of clients or just some, etc?

[seanmuir]

Hi Michael,

I work for a carrier and I cant dedicate resource to opening tickets for unleashed when its not a product we will be using

As you know the second you open a ticket, you end spending a lot off time helping with debugging the issues.

However when it does, there will no doubt be tickets galore 😉

Sean

[michael_brado]

Great, thank you.

[michael_brado]

Did I see someone else reply about 3 Standalone APs?  You can run Channelfly for a period of hours
during daily use, then statically save/assign the channels that were last selected.  Avoid the DFS/radar
channels in 5G, but you can advertise the same SSID(s) on both radios of all APs in a small business
or home environment.  From the title of this topic though, it is not unusuall, in fact expected, to see
dissassociated from AP msgs as clients move between APs.

[jason_sparrow]

I haven't opened a ticket, however, I have asked a question in the Unleashed forum.