> 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/client-disruption-tests/michael-shutdown-exploitation-remote-router-shutdown.md).
# Michael Shutdown Exploitation - Remote Router Shutdown
Assess router stability during an authorized Michael shutdown test.
This test can cause a router to restart or stop responding. When clients reconnect to the access point, an assessment can observe the reconnection process.
### Technical behavior
1. A crafted network request or packet reaches the router.
2. A firmware flaw prevents the router from processing it correctly.
3. The router may freeze, restart, or stop responding.
4. Connected devices temporarily lose network access.
This does not necessarily power off the router or provide full control. It often causes only a temporary service interruption.
The exact behavior depends on the router model, firmware, and vulnerable service. Some scenarios also require access to the same Wi-Fi network.
{% hint style="warning" %}
Before running this test, confirm the target access point, affected clients, authorization, and recovery plan. It can interrupt connectivity for every client on the target access point.
{% endhint %}
### Run the scoped test
Copy the access point BSSID and use it as the target:
{% code overflow="wrap" %}
```bash
mdk3 wlan0mon m -t 70:4F:57:CA:D9:73
```
{% endcode %}
---
# 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/client-disruption-tests/michael-shutdown-exploitation-remote-router-shutdown.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.
