Solved

How to roaming time WING 5/7

  • 10 May 2020
  • 6 replies
  • 530 views

Userlevel 3

Hello community,

I am convinced that there is some method to check out the client roaming time.

Suggest please

Aviv

icon

Best answer by Chris Kelly 11 May 2020, 17:21

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.

 

 

View original

6 replies

Userlevel 4

Hello Aviv,

You may run command like the following one to collect all packets related to the certain host during the roaming time and then check timestamps.

remote-debug live-pktcap rf-domain default radio all filter ether host AA-BB-CC-11-21-33 

Best Regards,

Nikolay

Userlevel 3

Hello Nikolay,

Thanks

Aviv

Userlevel 6

Aviv,

 

More specifically, the command I use for watching roaming clients are these two.  You can optionally fine-tune what you are capturing with additional filter syntax.

 

#remote-debug wireless rf-domain <rfd> clients <MAC> events management

(Filter out Probe request frames)

#service pktcap on radio all count 9999 filter not dot11 probe and dot11 mgmt and ether host <MAC>

Userlevel 3

Hello Chris,

There is several kinds of messages from the filtered results:

I  ACTION

O  ACTION

I  AUTH

O  AUTH

I  REASSOC_REQ

O  REASSOC_RESP

I  ACTION

O  ACTION

In which conditions I typically should see any of these messages?

What exactly is the start and the end point of the roaming procedure ?

Thanks

Aviv

 

 

Userlevel 6

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.

 

 

Userlevel 3

Hello Chris,

Very informative.

Thanks a lot

Aviv

Reply