Ruckus Zap and Speedflex test setup
-
Buid zap tool. link
-
Install Ruckus Speedlflex on Node #1 and #2.
-
Test basic connectivity between Node #1 and #2 using the app Speedflex itself
.
-
On the control(laptop), run zap client
$ ./bin/linux/zap -s192.168.1.3 -d192.168.1.4
./bin/linux/zap version 1.83, Copyright ( C ) 2004-2009 Ruckus Wireless, Inc. All Rights Reserved.
Built Jul 29 2020 at 10:29:36
Engaging default options -p50000 -n1000 -l1472 -q0x0
0: 192.168.1.3->192.168.1.4 233=rx 0=dr 0=oo 0=rp 233=rx in 51.7ms 53.0mbps 53.0 | 53.0 53.0 53.0 53.0 53.0 53.0
1: 192.168.1.3->192.168.1.4 546=rx 0=dr 0=oo 0=rp 313=rx in 50.3ms 73.2mbps 63.1 | 73.2 53.0 53.0 53.0 53.0 53.0
2: 192.168.1.3->192.168.1.4 628=rx 0=dr 0=oo 0=rp 82=rx in 59.6ms 16.2mbps 47.5 | 73.2 53.0 16.2 16.2 16.2 16.2
3: 192.168.1.3->192.168.1.4 769=rx 0=dr 0=oo 0=rp 141=rx in 68.1ms 24.4mbps 41.7 | 73.2 24.4 16.2 16.2 16.2 16.2
4: 192.168.1.3->192.168.1.4 1081=rx 0=dr 0=oo 0=rp 312=rx in 50.7ms 72.5mbps 47.9 | 73.2 53.0 16.2 16.2 16.2 16.2
5: 192.168.1.3->192.168.1.4 1337=rx 0=dr 0=oo 0=rp 256=rx in 50.3ms 59.9mbps 49.9 | 73.2 53.0 16.2 16.2 16.2 16.2
6: 192.168.1.3->192.168.1.4 1547=rx 0=dr 0=oo 0=rp 210=rx in 51.2ms 48.3mbps 49.6 | 73.2 53.0 16.2 16.2 16.2 16.2
7: 192.168.1.3->192.168.1.4 1790=rx 0=dr 0=oo 0=rp 243=rx in 71.9ms 39.8mbps 48.4 | 73.2 48.3 16.2 16.2 16.2 16.2
8: 192.168.1.3->192.168.1.4 1909=rx 0=dr 0=oo 0=rp 119=rx in 50.8ms 27.6mbps 46.1 | 73.2 48.3 16.2 16.2 16.2 16.2
9: 192.168.1.3->192.168.1.4 2097=rx 0=dr 0=oo 0=rp 188=rx in 85.8ms 25.8mbps 44.1 | 73.2 39.8 16.2 16.2 16.2 16.2
10: 192.168.1.3->192.168.1.4 2104=rx 0=dr 0=oo 0=rp 7=rx in 80.1ms 1.0mbps 40.2 | 73.2 39.8 16.2 1.0 1.0 1.0
11: 192.168.1.3->192.168.1.4 2127=rx 0=dr 0=oo 0=rp 23=rx in 96.3ms 2.8mbps 37.0 | 73.2 27.6 2.8 1.0 1.0 1.0
2 comments
test
Wednesday, Aug 12, 2020
name2
Wednesday, Aug 12, 2020
Say something
Thank you
Your post has been submitted and will be published once it has been approved.
OK
OOPS!
Your post has not been submitted. Please return to the page and try again. Thank You!
If this error persists, please open an issue by clicking here.
OK