- Create a monitor port.
- In the Port Mgr tab, select a wiphy device that you wish to sniff with (this example will use wiphy1, an ath10k radio).
- If the wiphy device is down, click the up arrow to enable it.
- Click Modify.
- Select the channel you wish to sniff. Channel 36 will be used for this test.
- Click OK.
- Back in the Port Mgr tab, with the wiphy device still selected, click Create.
- Select the WiFi Monitor option at the top.
- Set the Quantity to 1.
- Set the STA ID to 0.
- Click Apply and close the Create Port window.
- In the Port Mgr tab again, modify moni0.
- You can disable HT40 and HT80 here if needed.
- Click OK to close the window.
- For this current setup, traffic will be generated with a layer 3 UDP connection between two stations.
For more information see Generating Traffic for WLAN Testing
- Use Wireshark to sniff moni0.
- If you are running the LANforge GUI from a Windows machine without x server installed, you will need to connect remotely to the LANforge system via rdesktop or vnc.
- To connect via rdesktop, type the following command into a console (replace LANforge-IP with the IP of your LANforge system):
- The login info is username/password lanforge/lanforge
- To connect via vnc, type the following command into a console (replace LANforge-IP with the IP of your LANforge system. Don't forget to add the ':1' after the IP):
The password is lanforge.
- Once you have accessed the LANforge system via rdesktop or vnc, open the LANforge GUI with the desktop icon shown below.
- Select moni0 in the Port Mgr tab.
- Click the Sniff Packets button. Wireshark will now open and automatically start scanning for packets. If you get a window that warns about running as user root, click OK.
- To use a filter, simply add the filter constraints to the filter text box as seen below and click Apply to the right. The below screenshot has wireshark filtering on a specific IP.
- If you'd like to only see traffic to/from a single AP use the filter wlan.addr == [bssid]
- There are many filters that can be used in Wireshark. Some handy ones include:
wlan MAC: wlan.addr==xx:xx:xx:xx:xx:xx
Association request wlan.fc.type_subtype eq 0
Association response wlan.fc.type_subtype eq 1
Probe request wlan.fc.type_subtype eq 4
Probe response wlan.fc.type_subtype eq 5
Beacon wlan.fc.type_subtype eq 8
Authentication wlan.fc.type_subtype eq 11
Deauthentication wlan.fc.type_subtype eq 12
- Filters can be combined to specify if packets should match all filters (with &&) or any filters (with ||).
For example, if you wanted to view packets that only contain both IPs 18.104.22.168 and 22.214.171.124 you could use the following: ip.addr==126.96.36.199 && ip.addr==188.8.131.52
Or, if you want to see all packets containing 184.108.40.206 and all packets containing 220.127.116.11, you could use the following: ip.addr=18.104.22.168 || ip.addr==22.214.171.124
- You can visit https://wiki.wireshark.org/DisplayFilters for more tips on filters.
A handy 'cheat sheet' with most filters can be found here.