User's Manual

98 Tools
Performing a packet file trace
To perform a packet file trace.
1. S e l e c t Tools > Network trace.
2. Select a Trace interface. The following M220 interfaces are available for packet trace:
• radio1: 802.11 traffic on the radio.
• eth0: 802.3 traffic on the Ethernet port.
• wlan0: Traffic for the default wireless community.
• wlan0vapx: Traffic for wireless community x, where x is the community ID and can
be from 1 to 7. Wireless community IDs are shown in the first column of the
Communities table on the Wireless > Communities page.
• brtrunk: Traffic that is forwarded among different wireless communities, the Ethernet
interface, and WDS interfaces.
• wlan0wdsx: Traffic for WDS interface x, where x is the WDS interface ID and can
be from 1 to 4. Configured WDS interfaces are shown on the Wireless > WDS page.
3. Specify the following parameters:
• Trace duration: The time duration in seconds for the trace (range 10 to 3600).
• Max trace file size: The maximum allowed size for the trace file in KB (range 64 to
4096).
If you change either of these values, you must select Save before initiating a trace.
4. Select Start Trace.
The trace session will run for the specified duration. You can view the trace status in the
File trace status section. Select Refresh to see updated trace time and file size values.
You can also select Stop Trace to stop a trace before the specified duration has elapsed.
Remote packet trace
Remote packet trace enables you to specify a remote port as the destination for packet
captures. This feature works in conjunction with the Wireshark network analyzer tool for
Windows. A packet trace server runs on the M220 and sends the captured packets via a TCP
connection to the Wireshark tool.
A Windows PC running Wireshark enables you to display, log, and analyze captured traffic.