1 ACCEPTED SOLUTION
Aviv,
Finding a way to determine the time a roaming event can be a little subjective in that it depends on when YOU determine the point at which point the roam event actually starts. (Some might say that the roam begins with the client starts probing the new AP, but doing so means you are including the time that it takes for the client to probe for APs and get responses. Do you care about that?).
For someone who is more concerned about actual delays between roams for data/time sensitive applications, maybe your timer begins when the last data frame is sent by the client (ACK’d also maybe?) and stops when the client sends its first data frame using the new AP.
Specifying when the roam event events is usually easier. Usually it’s the end of the 4-way handshake (signifying the end of the association process with the new AP) or when the client first sends a data frame when using the new AP that it roamed to.
Personally, I would START the ‘timer’ when the authentication request frame is seen from the client that is roaming and would then END the timer when message-4 of the 4-way handshake is transmitted by the AP.
So in the messages you posted, it looks like you would start at the first “AUTH” message from the client...which SHOULD be the authentication request.
From the messages you posted though, I don’t see the 4-way handshake messages.
Use this filtered syntax to only show what we’re looking for here.
#remote-debug wireless rf-domain <RFD> clients all events management wpa-wpa2
A roam should look similar to this.
