Forum Replies Created
You have to first have an 11ax AP and client in order to do the comparison.
Second, you have to have a way to capture 11ax. Today there are no radios for client-side capture, so you would have to use an AP as a radio capture device.
Run an application with 11ac and capture. Then run the same application with 11ax and capture. Compare timing values between the two captures.
11ax has at least a chance to improve latency by creating more contention domains, and therefore less contention.
Any such documents would be immediately refuted by Cisco (and their worshippers) as being technically incorrect (regardless of content), so nobody would bother wasting the time to write it…fortunately. The best we can do in such situations is to help our customers achieve optimal results, regardless of whether RRM is or isn’t in use.
DevinApril 26, 2016 at 7:46 pm in reply to: Apple Channel Utility Test (client induced channel saturation) #3265
Interestingly, you can do the same thing on an Aerohive AP with the following commands:
2.4 GHz radio:
_test interface wifi0 cont-tx
5 GHz radio:
_test interface wifi1 cont-tx
That’s extremely useful. Thanks James!
That rocks, thanks James!
Here’s another cool Apple tidbit:
Apple Channel Utility Test
Client induced channel saturation
Within a terminal window:
To generate traffic on a WiFi interface, pick an available IP on the network.
Set a static arp entry for a fake host on the same network. You may be required to use sudo for the arp command.
arp -s 10.0.1.199 ab:cd:22:22:22:22
! mac is arbitrary
! IP should be on same segment
Send a bunch of traffic out the interface
cat /dev/random | nc -u 10.0.1.199 22
! include port # after ip address
Control-C to quit