Reference Manual
Table Of Contents
- Introduction to RS9116
- Getting Started with RS9116
- Compiling the Driver
- Installing the Driver
- Installation of Modules
- Enabling a Protocol
- Disabling a Protocol
- OneBox-Mobile in Wi-Fi Only Mode
- Installation in Wi-Fi Client Mode (with BSD interface support)
- Installation in Access Point Mode (with BSD interface support)
- Installation in Wi-Fi Client Mode (with NL80211 support)
- Installation in Wi-Fi AP mode (with NL80211 support)
- Installation in Wi-Fi Direct Mode (With BSD Interface Support)
- Installation in Wi-Fi Direct Mode (With NL80211 Support only for Kernel v3.8 or higher)
- OneBox-Mobile in Wi-Fi + Bluetooth LE Coexistence Mode
- Driver Information
- Wi-Fi ioctl Usage Guide
- Configuration Using CFG80211
- Enterprise security using CFG80211
- HOSTAPD and Wi-Fi Protected Setup (WPS)
- ACS with Hostapd
- Antenna Diversity
- Sniffer Mode
- Monitor Mode
- Concurrent Mode
- Background Scan Parameters
- Power save Modes, Profiles and Parameters
- Compliance and Certification
- Wi-Fi Performance Test ioctl usage
- Wake-On-Wireless LAN
- PUF [ Physical Unclonable Functions ]
- GTK Offload
- Steps to connect 802.11R client to AP
- Steps to configure 802.11W
- Update WLAN region based maximum powers from driver
- Bluetooth hcitool and hciconfig Usage
- Android support for RS9116
- Appendix A: Configuration of Kernels from 3.13 and above
- Appendix B: Binary Files for Embedded Platforms
- Appendix C: Using the Bluetooth Manager
- Appendix D: Common Configuration Parameters
- Appendix E: Installation of Missing Generic Netlink Libraries
- Appendix F: Procedure to use latest supplicant with NL80211 interface
- Appendix G: Considerations need to be made during hostapd usage
- RS9116 n-Link Software TRM Revision History
RS9116 n-Link Linux and Android Technical Reference Manual
Version 2.0
August 2019
84
12 Monitor Mode
The Monitor Mode is one of the operating modes that can be set while creating a VAP. It enables capturing of
packets which is transferred over a single or multiple VAPs and are operating in either Access Point or Client or P2P
modes.
The order of the VAPs' creation does not matter. Once it is created, the "tcpdump" command can be used to
display the packets which are being transferred.
Example Scenario 1: Create a Client mode VAP and a Monitor mode VAP and display packets which are being
transferred to/from the Client
./onebox_util rpine0 create_vap wifi0 sta sw_bmiss
./onebox_util rpine0 create_vap wifi1 mon
ifconfig wifi0 up
ifconfig wifi1 up
tcpdump –i wifi1
Example Scenario 2: Create an Access Point mode VAP, a Client mode VAP and a Monitor mode VAP and display
the packets which are being transferred to/from the Access Point and Client.
./onebox_util rpine0 create_vap wifi0 ap
./onebox_util rpine0 create_vap wifi1 sta sw_bmiss
./onebox_util rpine0 create_vap wifi2 mon
ifconfig wifi0 up
ifconfig wifi1 up
ifconfig wifi2 up
tcpdump –i wifi2
Monitor mode VAP should be enabled after enabling all other VAP's.
The difference between Sniffer and Monitor modes is explained below:
Monitor mode displays the packets which are being transferred to/from the device and are configured in
different operating modes like Access_point, Client and so on.
Where as,
Sniffer mode displays all the packets on air depending on the channel and band width configured and
displays them using wire shark tool.