NWA/WAC Series CLI Reference Guide 68
CHAPTER 10
Wireless Frame Capture
This chapter shows you how to configure and use wireless frame capture on the NWA/WAC.
10.1 Wireless Frame Capture Overview
Troubleshooting wireless LAN issues has always been a challenge. Wireless sniffer tools like
Ethereal can help capture and decode packets of information, which can then be analyzed for
debugging. It works well for local data traffic, but if your devices are spaced increasingly farther
away then it often becomes correspondingly difficult to attempt remote debugging. Complicated
wireless packet collection is arguably an arduous and perplexing process. The wireless frame
capture feature in the NWA/WAC can help.
This chapter describes the wireless frame capture commands, which allows a network administrator
to capture wireless traffic information and download it to an Ethereal/Tcpdump compatible format
packet file for analysis.
10.2 Wireless Frame Capture Commands
The following table identifies the values required for many of these commands. Other input values
are discussed with the corresponding commands.
Table 37 Input Values for Wireless Frame Capture Commands
LABEL DESCRIPTION
ip_address The IP address of the Access Point (AP) that you want to monitor. Enter a
standard IPv4 IP address (for example, 192.168.1.2).
mon_file_size The size ( in kbytes ) of file to be captured.
It stops the capture and generates the capture file when either it reaches this
size or the total combined size of all files in the directory reaches the maximum
size which is 50 megabytes (51200 kbytes.)
file_name The file name prefix for each captured file. The default prefix is monitor while
the default file name is monitor.dump.
You can use 1-31 alphanumeric characters, underscores or dashes but the first
character cannot be a number. This string is case sensitive.