> 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/mac-address-spoofing-and-tips.md).
# MAC Address Spoofing and Tips
Safely inspect, change, verify, and restore an adapter MAC address in an scoped wireless assessment.
Changing an adapter's MAC address can support privacy testing and scoped wireless assessments. Keep testing limited to equipment you own or are authorized to assess.
{% hint style="warning" %}
Do not use a MAC address to impersonate another device or bypass access controls.
{% endhint %}
### Before you start
Record the adapter's permanent MAC address. You need it to restore normal operation later.
Replace `wlan0mon` with your active wireless interface throughout this guide.
### 1. Inspect the current address
View the current and permanent MAC addresses:
```bash
macchanger -s wlan0mon
```
The permanent address belongs to the adapter hardware. The current address can change temporarily.
### 2. Change the address
Bring the interface down before changing its MAC address:
```bash
ip link set dev wlan0mon down
```
Assign a random MAC address:
```bash
macchanger -r wlan0mon
```
Bring the interface back up:
```bash
ip link set dev wlan0mon up
```
### 3. Verify the change
Confirm the new address:
```bash
macchanger -s wlan0mon
```
### 4. Restore the permanent address
Restore the hardware MAC address after the lab:
```bash
ip link set dev wlan0mon down
macchanger -p wlan0mon
ip link set dev wlan0mon up
```
### Operational notes
* The changed address usually resets after restarting the adapter or system.
* Changing the MAC address can interrupt existing WiFi or DHCP connections.
* Use locally administered or randomly generated addresses for scoped tests.
---
# 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/mac-address-spoofing-and-tips.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.
