You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am testing simple loadbalancing scenario in different channels.
While doing it, I found that switching AP seems not working properly. To test it in details, I am checking mobile station first disconnect original AP after receiving CSA message. However, I found that it seems hard to confirm whether mobile station actually dis-assoc original AP or not. Please kindly let me know if there is a convenient way.
Many thanks in advance.
The text was updated successfully, but these errors were encountered:
One thing we have seen is that, when the STA receives the last CSA, it switches to the new channel, but it waits for a number of beacons (maybe 2, 3 or 4) in the new channel. Once it receives them, it starts working in the new channel.
The next step in our plans is to release a channel assignment application for the APs, and to develop a new load balancing application. We will upload them as soon as they are ready.
I think it was confusing you because of the inaccurate question.
I have been testing the reference you sent.
The CSA and Beacon messages could be seen in monitoring mode (by Wireshark), but the up /down stream traffic did not flow to the channel (AP1 -> AP2) handover by the station.
Odin Agent(AP2) debugging can see add_lvap and station list increase.
However, the station didn't associate. It just repeats the authentication.
Hi folks,
I am testing simple loadbalancing scenario in different channels.
While doing it, I found that switching AP seems not working properly. To test it in details, I am checking mobile station first disconnect original AP after receiving CSA message. However, I found that it seems hard to confirm whether mobile station actually dis-assoc original AP or not. Please kindly let me know if there is a convenient way.
Many thanks in advance.
The text was updated successfully, but these errors were encountered: