> For the complete documentation index, see [llms.txt](https://documentation.hak5.org/wifi-pineapple-pager/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.hak5.org/wifi-pineapple-pager/pineapple-open-ap.md).

# Pineapple Open AP

Open Wi-Fi networks offer no encryption and no verification of the connection. Despite the inherent risks, open networks are still in use everywhere - airports, coffee shops, corporate guest networks, and more.

The Pineapple Open access point can not only mimic a Wi-Fi network, it can mimic *any* Wi-Fi network. At the same time.

### How mimicry works  <a href="#how-mimicry-works" id="how-mimicry-works"></a>

Whenever a Wi-Fi client joins a network, it sends a special packet - a *probe request*. An access point willing to accept that connect then responds with a *probe response* packet.

Under normal circumstances, an access point only responds with the SSID (network name) it is providing - usually a one-to-one relationship.

Using a Wi-Fi attack called `karma`, a Pineapple in mimicry mode will answer any request for a network name with a response - for that same name. Once connected, the client considers the connection to be completely normal!

The SSIDs allowed to connect are controlled by the Pineapple filter system - keep reading for more information!

### Enabling Pineapple Open AP mode  <a href="#enabling-pineapple-open-ap-mode" id="enabling-pineapple-open-ap-mode"></a>

The WiFi Pineapple has four controls which impact Pineapple Open AP mode:

1. Enabling the Open Wi-Fi access point itself. To mimic an Open access point, the open access point must - unsurprisingly - be turned on. The Open AP configuration can be found under `PineAP` > `Open AP`.
2. Enabling mimic mode. With this disabled, the Open AP is just an Open AP - it will function for the configured SSID but nothing more. Mimic mode is found under `PineAP` > `PineAP` > `Mimic Open Networks`
3. The Client filter. The Client filter controls what clients are allowed to join the Pineapple Open AP network. The Client filter can be found in `PineAP` > `Filters`.
4. The Network filter. Network filter controls what network names the Pineapple Open AP responds to. The SSID filter can be found in `PineAP` > `Filters`.

<figure><img src="/files/sztgKIq832V77S2gE0ol" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/wN4KBSsrqjK58ujtwJMO" alt=""><figcaption></figcaption></figure>

### Pineapple filters  <a href="#pineapple-filters" id="pineapple-filters"></a>

The Pineapple filter engine is the main mechanism for scoping the WiFi Pineapple behavior for an engagement. Properly configuring your filters is a crucial part of impacting only the devices and networks you intend to!

**Filter modes**&#x20;

Pineapple filters operate in two modes:

1. Allow mode. In allow mode, **only devices and networks in the allowed list may connect**. All other connections are rejected.
2. Deny mode. In deny mode, any device or network **not in the deny list** may connect.

So, for example, to allow *any client* to connect to the Pineapple Open AP using the SSIDs `Test network` and `Free Wi-Fi`, you would set:

1. The **device filter** to `deny` mode, with no filter list (this allows **any** client to connect, useful with MAC address randomization)
2. The **network filter** to `allow` mode, with the allow list containing the two SSIDs in the engagement.

**Default filters**&#x20;

By default, the Pineapple ships with Client and Network filters both set to `allow` mode, with empty lists. This blocks all associations, which prevents a new Pineapple from interfering with nearby devices or networks unintentionally.

<figure><img src="/files/BgyEUqMijpFHwUc4Q966" alt="PineAP Client Filter"><figcaption><p>PineAP Client Filter</p></figcaption></figure>

<figure><img src="/files/qia7FFJA9ZoHgqYFocUj" alt="PineAP Network Filter"><figcaption><p>PineAP Network Filter</p></figcaption></figure>

### Pitfalls <a href="#pitfalls" id="pitfalls"></a>

1. Remember filters!

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.hak5.org/wifi-pineapple-pager/pineapple-open-ap.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.