- deauth/kick: use full PINEAPPLE_DEAUTH_CLIENT hak5cmd app name (BUG 1)
- _allow_all_ssids: PINEAPPLE_NETWORK_FILTER_MODE deny so karma lets
clients associate after deploy (BUG 2)
- enterprise inner EAP (BUG 3), two root causes found by live experiment:
- hostapd never wildcard-matches a bare `*` identity for phase-2
lookups; eap_users now uses quoted empty prefix `""* ... [2]`,
which prefix-matches any inner identity
- pineape_auth_pass=1 forwards inner EAP to pineapd, which has no
standalone responder; deploy forces 0 and stop restores 1
Residual: plaintext MSCHAPv2 capture is firmware-blocked on 24.10.1
(MSG_DEBUG compiled out of the karma wpad; `-f` silently ignored);
documented in code comments and the validation report.
- ISSUE 4: point pineapd.@hostapd[0].mgmtiface at wlan1wpa during 5 GHz
WPA deploys so handshakes/loot populate; cleared on stop
- ISSUE 5: radio0 set_ap path polls 90 s across the wifi-reload window
and retries set_ap once if the iface still has not appeared
- ISSUE 6: skills docs use `llc && eth.type == 0x888e` (firmware tcpdump
matches 0 frames on `eapol`)
- ISSUE 7: capture state helper detects dead-pid / iface-down, cleans up,
status reports {running:false, stale:true} instead of zombie running
- tests: fix global os.path monkeypatch leaks between test modules that
broke test_mk8_events/test_reliability_api under discovery; add
regression coverage for all fixes above (463 tests green)
Live validation evidence and newly discovered firmware quirks
(DEVICE_FILTER_DELETE no-op, dropbear rate limiting) recorded in
docs/validation/2026-08-23-pineap-validation-report.md.
Mark VIII
A Mark VII-style web management UI that runs on the WiFi Pineapple Pager at
http://172.16.52.1:8080/. Packaged as a native Pager payload.
Features: Dashboard (live), PineAP (settings, SSID pool, filters, clients/kick),
Recon (scans from recon.db), Handshakes/Loot, Payloads (embedded stock Pager
Portal), Logs, Settings (hostname/NTP/password/prefs), and a bottom-docked xterm
terminal.
- Rogue AP on the second radio (5GHz / 6GHz Wi-Fi 6E): Open AP and Evil WPA
(WPA2-PSK/WPA3-SAE/WPA3-OWE) on
radio1, band-aware channel pickers, 6GHz requires WPA3. While a radio1 AP is enabled the stock monitor-hopping (wlan1mon) is paused and resumed on disable; 2.4GHz PineAP is untouched.
Requirements
- WiFi Pineapple Pager, firmware
Pineapple Pager 24.10.1 python3on the device (factory 24.10.1 may not ship it;scripts/deploy.shinstalls OpenWrtpython3-lightfrom offline ipks)- Python 3.11 on the development machine
Install (sideload)
macOS/Linux:
# Recommended: key authentication
./scripts/deploy.sh --ssh-key "$HOME/.ssh/pager_key"
# Password authentication requires sshpass
brew install hudochenkov/sshpass/sshpass
./scripts/deploy.sh --password '<device-password>'
Windows:
# deploy.ps1 needs either an SSH key or sshpass for password auth:
& .\scripts\deploy.ps1 -SshKey "$HOME\.ssh\pager_key"
# or set up a key and add it: ssh-copy-id root@172.16.52.1
The deployment scripts build build/pager-webui/payload-<b64>.zip, upload it,
extract it to /root/payloads/user/remote_access/pager-webui/, and refresh the
portal index.
Then on the Pager menu, run Mark VIII:
- Yes to "Run as background service?" -> procd service (respawns on crash, boot-persistent via rc.d symlinks).
- No -> foreground mode; press B to stop.
- Re-run the payload while running to Stop the service.
PAYLOAD_GET_CONFIG pager_webui auto_mode/run_modeskip the prompt.
Every payload run (and every service startup) first runs an environment
check that prints on the payload screen / /tmp/pagerwebui.log: daemon
reachable, pineapd alive, monitor interfaces up, and recon DB readable. On a
healthy pager it does not rewrite live PineAP or wireless UCI (SSID pool,
hopping, dummy_radio0 STA, Open AP). Crash-prone settings are reported as
warnings. Startup aborts only if a core dependency fails. The health monitor
will restart a dead pineapd and re-raise dropped monitors; it will not clear
the SSID list or disable pool broadcast.
Browse http://172.16.52.1:8080/ and log in with the device password.
Uninstall / recovery
Re-run the payload and confirm "Stop service?" (stops, disables, removes the
init script), then delete the payload directory via the portal or:
rm -rf /root/payloads/user/remote_access/pager-webui. No stock files are modified.
After a firmware upgrade (which wipes the overlay), reinstall and run the
payload to re-enable it—the same caveat as Nautilus.
Local dev loop
.\scripts\deploy.ps1 -SshKey "$HOME\.ssh\pager_key" # deploy backend once
.\scripts\dev.ps1 -Tunnel # local SPA + API proxy
# open http://127.0.0.1:8000
dev.ps1 serves www/ locally, proxies /api/* to the Pager, and points the
terminal at the Pager's daemon WS (-Tunnel opens the :1471 SSH tunnel).
The live WebSocket falls back to 5s polling through the dev proxy.
API tests
Python unit tests (stdlib unittest, runnable on Windows with mocks). Run each
module in its own process—the tests monkeypatch module-level helpers and do not
restore them, so a single discover process leaks state between files:
$py = "$env:LOCALAPPDATA\Programs\Python\Python311\python.exe"
Get-ChildItem tests\test_*.py | ForEach-Object {
$mod = "tests." + [IO.Path]::GetFileNameWithoutExtension($_.Name)
& $py -m unittest $mod -v
}
On-device smoke tests cover every page, background vs foreground, terminal I/O, and reboot persistence.
Architecture
server.py— Mark VIII's pure-socket HTTP + JSON API + minimal RFC6455 WS on0.0.0.0:8080, written to run on the device'spython3-light(nourllib/http.server/sqlite3stdlib modules there); talks to the Hak5 daemon (127.0.0.1:1471) over a raw-socket HTTP client,hak5cmd,uci,iwinfo, andrecon.dbread-only (via thesqlite3CLI).www/— vanilla JS SPA (no build step) + bundled xterm.js.payload.sh+pagerwebui.init— Nautilus-style installer / procd service.
Stability notes (Pager 24.10.1)
Reliability Core (v1.4.0)
The factory /etc/config/pineapd ships every crash source below enabled, so
guards that only live inside Mark VIII revert on every reset/upgrade. v1.4.0
makes the fixes structural (payload-only — no firmware changes):
- Boot guard (
mk8-guard, START=49): enforces the known-good UCI set before the S50 pineapple stack starts; idempotent, diff-only commits, logged to/tmp/mk8-guard.logand the event journal. - Profiles + rollback watchdogs: every risky operation (AP deploy,
client-mode change, profile restore) first snapshots UCI under
/mmc/mk8/profiles/, then spawns a detached watchdog probing local liveness (127.0.0.1:8080+ monitor presence). Sustained failure → automatic snapshot restore +wifi reload; recovery → promoteslastknown-good. Watchdogs self-exit after 120 quiet ticks. - RF plan: phy0 is always 2.4GHz ops; phy1 role-switches
uplink/attack/idle (
POST /api/rfplan/role). The uplink STA lives on radio1, so client-mode no longer blinds 2.4GHz recon. Hop governance belongs to the role manager, not the boot guard. - Supervisor: passive sampler (pidof/iw//proc only — never pineapd's
socket), bounded JSONL journal at
/mmc/mk8/events.log, boot-marker unexpected-reboot detection, memory watermark alerts. Dashboard shows events feed + reliability counters + guard sync chip. - Atomic deploys:
scripts/deploy.shstampsVERSIONinto build copies only, sha256-verifies the upload, swaps/mmc/mk8/releases/<ts>with acurrentsymlink, polls local health, and auto-rolls back to the previous release on failure. - Smoke suite:
scripts/smoke.shon-device (read-only checks always;--writeadds reconcile/watchdog drills;SMOKE_UPLINK_SSID=...enables the RF-role drill). All checks verified against live hardware including reboot persistence.
Persistent state lives in /mmc/mk8/ and survives reboots and firmware
upgrades (overlay wipes). A pre-reliability config backup is captured at
first deploy.
pineapd crash sources found and fixed on this firmware
pineapd crash sources found and fixed on this firmware (verified on-device, zero crashes over sustained watches):
- SSID-pool broadcast — segfaults pineapd (~15s cadence). Kept disabled.
- wlan2mon — a 6GHz monitor this hardware never creates; hopping the missing iface segfaults pineapd. Disabled.
- Large refilled pool — the pool list itself crashes pineapd even with broadcast disabled. The health monitor clears it (collect refills).
- wlan1mon fast-hopping 6GHz — stalls pineapd's command socket; the stock daemon's watchdog then SIGTERMs pineapd every ~30s. Bands pinned to 5GHz (2.4GHz only on wlan0mon).
- Socket collisions — actively pinging pineapd from a health monitor
collides with the stock daemon's own socket writes. The monitor now
checks
pidofonly.
GET /api/health reports pineapd/monitor state; the top bar shows a
PINEAP OK / POOL OFF / PINEAPD DOWN chip.
Security notes
- Auth via device password validated against the daemon; HttpOnly session
cookie
AUTH_<serverid>; all state-changing endpoints gated. - Commands run with argument lists (no shell interpolation).
- Binds
0.0.0.0:8080— same exposure class as the stock:1471/:7681. - Same-origin validation protects browser writes and WebSocket upgrades; the daemon token is stored in a root-only temporary session file.
Out of scope (v1)
:1471 takeover, Mark VII-only features (Campaigns/Modules/Cloud C2/EAP),
physical-display mirroring, and a PR to hak5/wifipineapplepager-payloads
(packaging is drop-in ready for that PR).
License
Mark VIII source code is available under the MIT License. See LICENSE and
THIRD_PARTY_NOTICES.md for bundled-component and trademark notices.