Title: GhostLink
Description: GhostLink connects two ESP32 devices for remote control while maintaining continuous AP hosting.
URL: /v2.1/getting-started/dual-communication/
Version: v2.1
Section: Getting Started
Search index: /search-index.json

# GhostLink

> GhostLink connects two ESP32 devices for remote control while maintaining continuous AP hosting.

## On this page

- [Prerequisites](#prerequisites)
- [How it works](#how-it-works)
- [Wiring](#wiring)
- [Basic usage](#basic-usage)
- [Examples](#examples)
- [Changing pins](#changing-pins)
- [Manual connection](#manual-connection)
- [On-screen UI](#on-screen-ui)
- [Troubleshooting](#troubleshooting)
- [Use cases](#use-cases)
- [Notes](#notes)
- [See also](#see-also)

---

GhostLink connects two ESP32 devices so one can host the AP while the other runs attacks.
## Prerequisites
- Two compatible ESP32 boards.
- Three wires (TX, RX, GND) to connect them.
- Both devices flashed with GhostESP firmware.
## How it works
- Wire two ESP32s together via UART.
- They auto-discover and connect on boot.
- Send any GhostESP command from one device to the other.
- No manual connection commands needed in most cases.
## Wiring
Connect the devices with 3 wires:
- TX of Device A → RX of Device B (GPIO 6 → GPIO 7 by default, 17 → 16 on base ESP32 models)
- RX of Device A → TX of Device B (GPIO 7 → GPIO 6 by default, 16 → 17 on base ESP32 models)
- GND → GND
Both devices need power.
## Basic usage
Once wired and powered on, devices automatically find each other:
- commstatus - Check if connected
- commsend <command> - Send any command to the other device
- commdisconnect - Disconnect if needed
### Examples
- commstatus - Check connection
- commsend scanap - Send command to other device
- commsend attack -d - Start attack on other device
- commsend beaconspam -r - Start beacon spam on other device
- commsend capture -probe - Start probe capture on other device
## Changing pins
Default pins are TX: GPIO 6, RX: GPIO 7 (or 17 and 16 on base ESP32 models). To change them:
Run commsetpins <TX_PIN> <RX_PIN> (for example, commsetpins 4 5).
Pin changes are saved and persist across reboots. You cannot change pins while connected.
## Manual connection
If auto-connection fails, you can manually connect:
- commdiscovery - Check discovery status
- commconnect ESP_A1B2C3 - Connect to specific device
Device names are auto-generated based on MAC address (format: ESP_XXXXXX).
## On-screen UI
When connected, the GhostLink menu appears. It uses a split-view terminal: local logs on the left, remote responses on the right.
Commands sent via the menu automatically open this view.
## Troubleshooting
- Not connecting: Check wiring (TX→RX, RX→TX, GND connected). Make sure both devices are powered. Reboot them simultaneously and wait 30 seconds for discovery. Run commstatus to check.
- Commands not working: Verify connection with commstatus. Use exact GhostESP command syntax.
## Use cases
- Hidden device control: Hide one ESP32 and control it remotely with full functionality through the web interface.
- Coordinated attacks: Both devices attack different targets simultaneously.
- Continuous AP hosting: One device maintains the access point while the other performs intensive operations.
## Notes
- Auto-discovery happens every 3 seconds.
- Connection uses UART at 115,200 baud.
- The device with the “larger” name becomes master, but commands can be sent from both directions.
- Auto-reconnect is enabled; the connection will automatically restore if interrupted.
- Physical wired connection is required.
## See also
- [BLE Bridge](/v2.1/getting-started/ble-bridge/) — use one of these wired boards as a Bluetooth proxy to the Android companion app.