Changes between Initial Version and Version 1 of 802.11/Resources


Ignore:
Timestamp:
Jul 28, 2013, 9:56:01 PM (11 years ago)
Author:
murphpo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • 802.11/Resources

    v1 v1  
     1[[TracNav(802.11/TOC)]]
     2= 802.11 Reference Design: Resources =
     3== Wireshark ==
     4
     5[http://www.wireshark.org/ Wireshark] is a tool for capturing and analyzing all kinds of network traffic. On PCs with supported Wi-Fi NICs Wireshark can use [http://wiki.wireshark.org/CaptureSetup/WLAN#Monitor_mode monitor mode] to capture and analyze all 802.11 traffic, including control and management frames. This is very useful for analyzing and debugging interactions among 802.11 nodes and a WARP node running the 802.11 Reference Design.
     6
     7In our experience Wireshark works very well on OS X machines. Monitor mode is supported on most newer Macs. We have used it successfully with the integrated 802.11 interfaces on 2010 and 2013 MacBook Pros.
     8
     9Based on the Wireshark docs, monitor mode is also supported on Linux machines, but not Windows. We have not tried either platform.
     10
     11The [http://www.riverbed.com/products-solutions/products/performance-management/wireshark-enhancement-products/Wireless-Traffic-Packet-Capture.html AirPcap devices] claim to enable monitor mode capture on Windows. We haven't tried these.
     12
     13== 802.11 Devices ==
     14
     15The 802.11 Reference Design should work with any device that implements 802.11g. We obviously can't guarantee this, given the enormous variety of devices out there.
     16
     17For the majority of our testing during development we used Linksys WRT54GL with the [http://www.polarcloud.com/tomato Tomato firmware]. With the right cable/adapter (RP-TNC - SMA) and sufficient attenuation (>50dB) the WRT54GL can be connected directly to the WARP v3 node RF interface. The Tomato firmware also enables forcing the Tx rate of the WRT54GL (some versions of the Linksys firmware may support this as well). Eliminating interference and forcing the Tx rate greatly simplify PHY debugging. In our experience even when connected directly a nearby laptop running Wireshark can still capture most frames being exchanged between the WRT54GL and WARP node.
     18
     19== Oscilloscope ==
     20
     21The 802.11 Reference Design routes a number of useful MAC/PHY signals to the WARP v3 debug header. These signals can be observed in real-time with an oscilloscope (probably also with a fast-running self-clocked logic analyzer; we haven't tried this).