The WLAN Pros Toolbox, served by your own WLAN Pi, reading your own radios.
Beta. This edition is finished and installable, and it has not yet been through a round of outside testing. This page is unlisted while that happens. If you are reading it, you were sent it on purpose, and the thing we want back from you is what broke.
Every other edition of the Toolbox runs on a device that holds the operating system at arm’s length. A phone will not decode a DHCP packet for you. A sandboxed Mac will not either. The WLAN Pi is Linux, it is yours, and it says yes.
So this is the edition with no wired ceiling. It reads the full DHCP option list rather than the handful of fields a phone will surrender, and it is the only place a real DORA exchange belongs. It scans with the Pi’s own radios instead of asking the operating system what it feels like sharing, and on a multi-radio Pi it lets you pick which one.
That makes it the reference platform rather than the afterthought. When an edition on another platform cannot answer a question, this is the build that shows you what the honest answer would have been.
Tested on both shipping models, the WLAN Pi R4 and the M4+, on WLAN Pi OS 3.4.4. The R4 with two Panda 6E adapters, the M4+ with a Panda plus an Intel BE200. There is no third current model.
The Pi serves the Toolbox over HTTP on port 8080 and answers 27 endpoints behind it. You reach it from any browser on the same network. Nothing is installed on the machine you browse from.
Read this before you put one on a network you do not own.
A normal install ships plain HTTP with authentication off. That is the right default for a bench tool on your own bench, and the wrong one anywhere else: anyone who can reach the Pi can reach everything it exposes, including tools that send arbitrary packets and wake machines on the LAN.
There is a hardened image-build mode that turns on TLS and HTTP authentication, forces key-only SSH, and regenerates secrets on first boot. If the Pi is going anywhere near a client site, use that one.
On the Pi itself, over SSH, one command:
curl -fsSL https://raw.githubusercontent.com/keithrparsons/wlan-pros-toolbox-pi/main/pi-install.sh | sudo bash
It checks it is really on a WLAN Pi and refuses loudly if it is not. It ends by printing INSTALL_OK.
If you do not see INSTALL_OK, it did not finish, whatever else scrolled past.
Then open http://<pi-ip>:8080/ from any browser on the same network.
The full runbook has the verification steps, the multi-radio notes, and what to do when it does not come up.
Not a bug list in the abstract. Three things: whether the one command above finished on your hardware, what the scan looked like against a network you already know well, and anything the Pi edition claims that you can prove wrong. The last one is the most valuable and the least fun to receive, so please send it anyway.