Capturing 802.11 frames with Ruckus Wireless access points and Wireshark

[keith_redfield]

Spotted on Twitter

Our Community Champ Primoz (@jazzycow81) just posted a very nice howto blog on setting up packet capture with Ruckus products and Wireshark. Have a look http://wlanimp.blogspot.com/2014/04/c...

It should be very helpful in troubleshooting wireless network issues.

BTW, we use Wireshark internally here and so attaching a trace to your case is a great way to accelerate resolution velocity

[primoz_marinsek]

Thanks for the bump Keith :)

I've just modified the post a bit, so it now includes how to change channels on APs which is important when using an AP just to capture frames.

[alberto_de_la_c]

Nice post Primoz!

I want to add that this remote capture feature only works with wireshark for windows (what is very annoying for me)

[alexandra_frinc]

Indeed a useful post for Ruckus clients, thank you for your contribution.

You could also include some info on how to capture on the uplink of the AP (on eth0). Sometimes, when troubleshooting is useful to compare the traffic coming on the uplink of the AP with what it is actually sent on the air side.

Have you notice any impact of enabling packet capture on the AP stability?
I've seen APs crashing after enabling packet capture (whether if it was done from the ZD webUI or from the AP's CLI). We're trying to understand why.

[primoz_marinsek]

Hi Alex

You could capture on the wired side also, but the intended topic of the post was how to capture packets from the air since you can do alot of troubleshooting that way.

I guess if there is any impact on AP stability it is down to some software bug rather than an overload due to the packet capture functionality in general. If capturing from a stand-alone AP I would suggest you use at least 7372 or better a 7982 AP for this since it is a 3x3 radio and the best hardware around so it shouldn't be a problem.