Yoto wireless device will only connect to one of many SSIDs on WLC

jsharkey_elgincounty · ‎03-30-2022

We have 10 Yoto Players and about half of them will not connect to the preferred SSID. Through testing I found that it would connect to one specific SSID. I created a test SSID and applied it to the same WLC interface that mysteriously worked and I was able to connect the device. If I then move the SSID to any other interface it fails to connect. I have compared the two interfaces and their is no differences aside from vlan #, subnet and gateway. I also compared the vlan interfaces on the core switch and their is again on IP differences no other differences that I can see. I setup a monitoring session and used wireshark to compare the packet captures. I applied a filter to the output to view only activity with the MAC address of the yoto player. On the working SSID, the first thing I see is a broadcast message then the device syncs up and communicates. On any non-working SSID there is simply no traffic showing from that filtered MAC.

Anyone run into anything like this before?

ammahend · ‎03-30-2022

whats the policy manager state when it does not connect ?

also share the wireshark capture that you did.

share controller model and version, can suggest few debugs to do additional checks.

-hope this helps-

jsharkey_elgincounty · ‎03-30-2022

Controller = 2504

Version = 8.5.182.0

from clients view, Status = Associated and Auth = Yes

Prince.O · ‎03-30-2022

Hello,

It seems the issue may be related to the interface/vlan configuration on the controller or possible communication issue on the switching side for that subnet

What controller model and code are you running ?

On the controller, what state do we see the client in when they encounter the problem ?

I would validate the following :

- The dynamic interface configuration is correct on the controller configuration ( ip address, subnet, gateway, DHCP server , etc)

- In the packet capture, I would filter on "dhcp" to validate the client is able to get an ip address or see where the communication fails.. if you see a DHCP broadcast being sent out and no respond back then may be a DHCP issue

Leo Laohoo · ‎03-30-2022

@jsharkey_elgincounty wrote:

Through testing I found that it would connect to one specific SSID.

Update the firmware of these machines because this has all the hallmark of a poorly-written wireless NIC code.