ESP32 Bit Pirate

ESP32-S3 Wi-Fi debugging

Scan Wi-Fi networks and host a Web CLI with ESP32

ESP32 Bit Pirate turns a compatible ESP32-S3 board into a Wi-Fi scanning and network debugging workbench. Use it to scan networks, find local devices, run authorized passive 2.4 GHz sniffing, host the Web CLI and test permitted network services.

Explore the ESP32 Bit Pirate site index Open the GitHub project
Wi-Fi debugging visual with ESP32 board, wireless signal and local network devices

Quick Wi-Fi workflow

Start by understanding the radio and network context. Once the board is connected or in AP mode, move to the recipe that matches the network task.

  1. 01

    Start Wi-Fi mode from the serial CLI.

  2. 02

    Scan nearby networks or start a controlled access point for a lab session.

  3. 03

    Connect only to authorized networks and confirm IP status.

  4. 04

    Run discovery for local devices, then check HTTP endpoints or test known service ports.

  5. 05

    Use passive sniffing only for authorized lab observation of nearby 2.4 GHz activity.

mode wifi
scan
connect
status
discovery
sniff

Example CLI flow. See the Wi-Fi wiki for exact syntax, saved credential behavior and firmware-specific options.

Wi-Fi workflows covered by ESP32 Bit Pirate

Use this overview to choose the right Wi-Fi or network workflow before opening a detailed recipe.

Scan

ESP32 Wi-Fi scanner

List nearby networks, inspect SSIDs and confirm whether the expected lab network is visible from the bench.

Discover

Local device discovery

After connecting to your own network, use discovery to identify local devices and document IP or MAC address details.

Sniff

Passive Wi-Fi sniffer

Cycle 2.4 GHz channels and observe nearby packet activity from the serial CLI for authorized lab awareness.

Hotspot

Web CLI over Wi-Fi

Start an access point or hotspot workflow when there is no existing router or when a quick browser CLI is useful.

HTTP

HTTP endpoint checks

Use Wi-Fi mode to test known local IoT endpoints or run URL analysis workflows after the network path is confirmed.

TCP

Authorized service checks

Use nmap, nc, telnet or Modbus TCP recipes to confirm whether a known host and service respond from the ESP32 network segment.

When an ESP32-S3 Wi-Fi workbench helps

Wi-Fi debugging often sits between firmware, radio range and local network behavior. A small external tool can prove whether the network path works before changing target code.

Bring-up

Before blaming firmware

Scan networks, connect, check IP status and confirm that another device can see the same local services.

Lab access

Before relying on infrastructure

Use AP or hotspot mode to open the Web CLI from a phone or laptop when the normal Wi-Fi network is unavailable.

Network service

Before debugging protocols

Check ports and raw TCP reachability before moving into HTTP, Modbus or application-specific workflows.

Wi-Fi hardware and safety reminders

These notes are intentionally short. The detailed command references live in the project documentation and firmware repository.

2.4 GHz

ESP32-S3 Wi-Fi workflows are centered on 2.4 GHz behavior. Use the right companion hardware for other radio bands.

Authorization

Run scans, sniffing and service checks only on networks and targets you own or are explicitly allowed to test.

Signal quality

RSSI, antenna placement, USB power and board orientation can change scan results and connection stability.

Network segment

Port checks and local discovery only see what the current Wi-Fi network, firewall and routing rules allow.

Common Wi-Fi problems

Most Wi-Fi failures are signal, credentials, routing, firewall or mode-selection problems. Check these before changing application code.

No network found

Check 2.4 GHz availability, signal strength, hidden SSIDs and whether the board is placed near enough to the access point.

Connect fails

Check credentials, security mode, DHCP behavior and whether the target network allows ESP32 clients.

No local devices

Confirm the ESP32 is on the same subnet, client isolation is disabled and the scan target is powered and reachable.

HTTP fails

Check DNS, IP address, port, path, firewall and whether the endpoint binds to the interface visible from Wi-Fi.

Sniffer looks quiet

Cycle channels, move closer, confirm the target traffic is 2.4 GHz and remember passive sniffing does not decrypt application data.

Detailed Wi-Fi recipes

These pages are the task-level Wi-Fi and network workflows. This overview keeps the protocol-level guidance here, while each recipe covers commands and troubleshooting in detail.

Useful Wi-Fi references

This page is a protocol overview. Use the site index for the full web experience, or GitHub for source code, firmware documentation and the Wi-Fi command reference.

Flash ESP32 Bit Pirate

Flash a supported ESP32-S3 board before testing Wi-Fi mode from the browser.

Open Web Flasher

ESP32 Bit Pirate GitHub

Check firmware source, issues and releases that affect Wi-Fi support.

Open GitHub repository

Wi-Fi debugging FAQ

Short answers for common questions before moving into a detailed workflow.

Can ESP32 Bit Pirate scan Wi-Fi networks and local devices?

Yes. ESP32 Bit Pirate can scan nearby Wi-Fi networks, connect to an authorized network and help discover local devices with the firmware discovery command.

Can ESP32 Bit Pirate run a passive Wi-Fi sniffer session?

Yes. ESP32 Bit Pirate can use Wi-Fi sniff mode to cycle channels and display nearby 2.4 GHz packet activity from the serial CLI.

Can ESP32 Bit Pirate host a Web CLI over Wi-Fi?

Yes. ESP32 Bit Pirate can start a Wi-Fi access point or hotspot workflow so a nearby client can open the Web CLI without an existing router.