> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/hacking-wifi/wpa-wpa2-psk-network-attacks/fundamentals/configuring-the-wireless-card-in-monitor-mode.md).
# Configuring the Wireless Card in Monitor Mode
Prepare, enable, verify, and restore a wireless adapter in monitor mode.
Use this workflow on an approved wireless adapter. Monitor mode can disrupt the adapter's normal network connection.
{% hint style="warning" %}
`airmon-ng check kill` stops services that may affect connectivity. Save active work first.
{% endhint %}
### 1. Identify the wireless interface
List the available network interfaces:
```bash
ip a
```
Identify the wireless adapter name. This example uses `wlx00c0cabd0890`.
### 2. Stop conflicting processes
Stop services that can interfere with monitor mode:
```bash
airmon-ng check kill
```
This can stop NetworkManager and disconnect the system from WiFi.
### 3. Enable monitor mode
Start monitor mode on the selected adapter:
```bash
airmon-ng start wlx00c0cabd0890
```
The tool may create or rename a monitor interface. Do not assume a fixed name.
### 4. Verify the interface
Confirm that the adapter reports `Mode:Monitor`:
```bash
iwconfig
ifconfig wlan0mon up
```
Use the monitor interface name shown in the output for subsequent lab tasks.
### 5. Restore normal operation
Stop monitor mode when the assessment ends. Replace `wlan0mon` with your interface name:
```bash
airmon-ng stop wlan0mon
```
Restart NetworkManager to restore normal network management:
```bash
sudo systemctl restart NetworkManager
```
If the connection does not return, reconnect through NetworkManager after it restarts.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/hacking-wifi/wpa-wpa2-psk-network-attacks/fundamentals/configuring-the-wireless-card-in-monitor-mode.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
