> 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.md). # Hacking WiFi WiFi hacking notes for wireless fundamentals, WPA/WPA2 PSK assessment, WEP networks, packet analysis, wireless tooling, and defensive validation. WiFi security notes for scoped assessments: wireless fundamentals, WPA/WPA2 PSK attacks, WEP network weaknesses, traffic analysis, password recovery workflows, and defensive checks. ## Main Areas

:circle-info:

Introduction

Scope, prerequisites, lab setup considerations, and WiFi assessment overview notes.Introduction

:book-open:

Basic Concepts

Network interfaces, wireless adapters, IP addressing, and MAC address fundamentals.Basic Concepts

:key:

WPA/WPA2 PSK Network Attacks

Monitor mode, Airodump, handshakes, deauthentication, Evil Twin, Bettercap, hcxdumptool, WPS, and cracking workflows.WPA/WPA2 PSK Network Attacks

:lock-open:

WEP Networks

Legacy WEP network attack notes and common weakness review.WEP Networks
## Objectives * Understand basic WiFi communication elements and protocols. * Identify different WiFi network security mechanisms. * Perform basic WiFi network attacks against approved targets. * Extract information from detected networks to identify weaknesses. * Protect networks against common WiFi-based attacks. * Use tools to assess and harden WiFi communication systems. ## Wireless Research Tooling Use this area for tools that complement WiFi security testing with research, sensing, signal analysis, or defensive validation workflows.

:wifi:

RuView WiFi Sensing

WiFi CSI sensing notes for ESP32-based experiments, presence detection, movement research, room activity analysis, and privacy-aware validation.RuView WiFi Sensing
--- # 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.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.