> For the complete documentation index, see [llms.txt](https://documentation.hak5.org/wifi-pineapple-enterprise/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-enterprise/ui-overview/settings.md).

# Settings

## Settings

From the main **Settings** page, you can configure the password and timezone and button script. On the second row of cards, you can view the currently mounted file systems and connected USB devices. On the bottom row, you can check for software updates, change the UI theme and configure the device for Hak5 Cloud C².

![Typical settings](/files/2KT5DwXJKQPAqopu2Vqr)

## **Networking**

The **Networking** tab shows easy to use cards for configuring a Client connection to another Access Point, set the interface used for Recon as well as listing the current interfaces and routing table.

![Typical Network Settings](/files/a8hDpxvOrDd01v7Kf1tk)

#### Client Mode

The most common method for connecting the WiFi Pineapple to the Internet is to use client mode networking.  This allows the WiFi Pineapple to connect to an existing WiFi network as a typical client, in the same fashion as a laptop or smartphone would.

#### Recon Interfaces

The recon interface is used by the WiFi Pineapple when scanning for WiFi networks and clients, and for deauthing networks and clients.

The default recon interface is `wlan2`, which is a built-in dual-band 2.4 GHz and 5 GHz radio.

#### Ethernet

The WiFi Pineapple Enterprise supports WAN and LAN Ethernet.

LAN Ethernet provides a DHCP server and is equivalent to connecting to the USB-C or WiFi Management networks.

WAN Ethernet allows the WiFi Pineapple Enterprise to connect to a physical network and will be used for Internet access when required.

## **WiFi**

The Manangement Network SSID and password can be configured on the WiFi settings page.

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

## **LEDs**

The WiFi Pineapple Enterprise has 4 LEDs, each of which have Red, Green, and Blue components which can be independently configured.

* Default Off\
  The LED remains off.
* Default On\
  The LED is always on.
* Heartbeat\
  The LED pulses regularly.  The speed of the heartbeat is tied to the overall system load - the higher the CPU load of the Pineapple, the faster the LED will pulse.
* Network device\
  Packets seen on a network device will cause the LED to blink.

<figure><img src="/files/mdhNjkDKvwLBgGbgaTmt" alt=""><figcaption><p>WiFi Pineapple Enterprise LED configuration</p></figcaption></figure>

## **Advanced**

The **Advanced** tab shows options to change the current update channel for opting into Beta firmware releases. From here you can also access experimental features such as Censorship (hiding sensitive information in the UI) and Cartography (2D or 3D map of Recon data).

![Advanced Settings](/files/jbvsmaI4DBxRgZcESsBJ)

#### Alternative Updates

To participate in the WiFi Pineapple Beta Program, select the "Beta" channel from alternative updates.  When new firmware is available, it will show up as an update in the beta channel!

#### Censorship Mode

Attempt to obfuscate MAC addresses, SSIDs, and other identifiable information in the UI.  This option is predominately for streamers, educators, and anyone taking screenshots or making presentations using the WiFi Pineapple.&#x20;

*Remember - always be safe when broadcasting data which could be used to perform location lookups, such as MAC addresses and unique SSIDs.  Always review your content before streaming and posting to make sure that no identifiable information is being shown despite censorship attempts.*

#### Cartography Mode

Enable an optional view of network topology and connected clients, found in the Recon panel.

#### Hotkeys

Enable single-press hotkeys to navigate the web UI

#### Management Access

By default, the WiFi Pineapple allows access to the management interface (the WiFi Pineapple UI) and the SSH server by default on all interfaces.

To prevent users on the Open and EvilWPA networks, or other users on the WiFi and Ethernet networks the WiFi Pineapple is connected to, from accessing the management interfaces, they can be excluded here.

The management interfaces are *always* available via the USB-C connection and the Management wireless network.

#### Hostname

Change the default host name of the Pineapple device.  This changes the name as shown in the SSH and web shells, and the host name used in DHCP requests sent in WiFi Client mode or over USB Ethernet.

## **Help**

The **Help** tab is split into 3 sub-pages: **Help & Information**, **Diagnostics**, and **Licenses.**

The **Help & Information** page offers links to more resources like this and Hak5 community outlets.

![](/files/-Mi2AlXrQbtEeDdnntHl)

The **Diagnostics** tab lets you generate a convenient diagnostics file that can be used to help troubleshoot any issues you may be experiencing with your WiFi Pineapple.

![](/files/-Mi2AQjwbNtpzG2ARraX)


---

# 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-enterprise/ui-overview/settings.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.
