Technical data

314 Meru System Director Configuration Guide © 2012 Meru Networks, Inc.
Capturing Packets
For a detailed explanation of all packet capture commands, see the Troubleshooting
chapter of the Meru System Director Command Reference.
Packet Capture Profile Example - WireShark
To do this, you need an external system running WireShark. This example creates the
packet-capture-profile named Sniffer on a controller and then forwards the captured
packets in layer 3 mode from AP-16 to WireShark on port #17777. Port 17777 is the
port where WireShark is listening for incoming packets in L3 mode on a remote
machine with IP address 1.1.1.1.
MC3K-1#
MC3K-1# configure terminal
MC3K-1(config)# packet-capture-profile Sniffer
MC3K-1(config-pcap)# mode l3 destination-ip 1.1.1.1 port 17777
MC3K-1(config-pcap)# ap-list 16
MC3K-1 (config-pcap)# enable-profile
MC3K-1(config-pcap)# exit
MC3K-1(config)# exit
MC3K-1# show packet-capture-profile Sniffer
AP Packet Capture profiles
Packet Capture Profile Name : Sniffer
Packet Capture profile Enable/Disable : off
Modes Allowed L2/L3 : l3
Destination IP Address : 1.1.1.1
UDP Destination Port : 17777
Destination MAC for L2 mode : 00:00:00:00:00:00
Rx only/Tx only/Both : rx
Rate Limiting per station or cumulative : station
Token Bucket Rate : 10
Token Bucket Size : 10
AP Selection : 16
Extended Filter String :
Interface List :
Packet Truncation Length : 0
Rate Limiting : off
Capture frames sent by other APs in the network : on
MC3K-1#
For a detailed explanation of the packet capture profile commands, see the Trouble-
shooting chapter of the Meru System Director Command Reference. (This cannot be
done from the Web UI.)
Limit bandwidth used. token-bucket-size sets the token bucket size.
Download the configuration to
the APs and start capturing
packets.
enable-profile turns on a packet capture profile.
To Do this: Using this command: