Based on the ESP32-C5-DevKitC-1 v1.2, the ESP32 Dual Band Wardriver offers wardriving capabilities for 2.4GHz and 5GHz WiFi as well as BLE. Logs are formatted for Wigle and saved to SD card.
Join #wardriving on Wigle and KokosStripClub (invite code: _mN01r0TAS8q) on WDGWars to have a little competitive fun with the art of wardriving.
IMPORTANT: If you are using the ESP32-C5-DevKitC-1 with the JCMK C5 Wardriver host board or you are powering your DevKit via the 3V3 pin, you much remove the 3V3 jumper from the DevKit or your device will not power properly
| ESP32-C5 | Display |
|---|---|
3V3 |
VCC |
GND |
GND |
GPIO6 |
SCK |
GPIO7 |
MOSI |
GPIO23 |
CS |
GPIO24 |
DC |
GPIO27 |
BL |
RST |
RST |
| ESP32-C5 | GPS |
|---|---|
3V3 |
VCC |
GND |
GND |
GPIO13 |
RX |
GPIO14 |
TX |
| ESP32-C5 | SD |
|---|---|
3V3 |
VCC |
GND |
GND |
GPIO6 |
SCK |
GPIO2 |
MISO |
GPIO7 |
MOSI |
GPIO10 |
CS |
| Board | ESP32-C5 | Button |
|---|---|---|
GPIO4 |
SCL |
|
GPIO5 |
SDA |
|
3V3 |
VCC |
|
GND |
GND |
|
Battery + |
BAT |
| ESP32-C5 | LED |
|---|---|
GPIO28 |
+ |
GND |
- |
The User Buttons require pull-down resistors
| ESP32-C5 | Button |
|---|---|
GPIO8 |
DOWN |
GPIO9 |
UP |
GPIO15 |
SELECT |
- Clone this repo
- In your workstation CLI, navigate to the
C5_Py_Flasherdirectory - With your ESP32-C5 device unplugged, execute
python c5_flasher.pyand allow any missing python packages to install - Once you see
Waiting for ESP32-C5 device to be connected..., connect your ESP32-C5 device to your PC via USB-C cable - Once you see
Ready to flash these files to ESP32-C5? (y/N):, enteryand allow the firmware to flash - When the
Hardware resetmessage appears on the screen, you may disconnect your ESP32-C5 device
The firmware update process is very simple once the initial install process is completed. The firmware is designed to check the attached SD card at every boot for a new bin file. If a new bin file is found, it uses it to automcatically execute an update. If an old bin file is found or no bin file is found, it resumes normal operation.
- Download latest firmware from releases
- Place the .bin file on the root of your SD card
- Install your SD card into the C5 wardriver
- Boot the C5 wardriver and allow the automatic update process to execute
When the C5 Wardriver is powered on, it will attempt to connect to WiFi using the user-provided WiFi credentials. If there were not credentials provided or the provided WLAN is not available, the C5 Wardriver will then start its own access point with the name c5wardriver and the password c5wardriver. The access point will remain active for 60 seconds if no client connections are made. The access point will otherwise remain active until a client disconnected. If the C5 Wardriver is able to connect to WiFi, it will remain connected until 60 seconds of inactivity on it's web server has passed. Once the web server or access point inactivity threshold has been reached, the C5 Wardriver will start normal wardriving operation. You can skip the admin phase of the boot process and go straight to wardriving if you hold the SELECT button as soon as the JCMK logo appears on the display.
The first time you boot the C5 Wardriver, it will start its own access point named c5wardriver. You can connect to this access point using password c5wardriver. The access point will remain active for 60 seconds or until all connected clients disconnect. Once connected, you can navigate to http://192.168.4.1 on your connected device where you will be presented with a web page. Here you can enter WiFi credentials which the C5 Wardriver will use to connect to a WLAN at every boot as well as your Wigle API credentials. You can also find the full contents of your SD card root available for download, including your wardriving logs. Once WiFi credentials are saved, the access point and webserver shutdown and normal wardriving operation starts.
At every boot, if the C5 Wardriver is able to connect to a WLAN using the user-provided WiFi credentials from the initial boot, it will present a webpage. The local IP of the C5 Wardriver will be displayed on the screen. The IP address may then be used by a device connected to the same WLAN to access the admin page of the C5 Wardriver. Here you will find the same web page as what you would see during the initial setup, the WLAN and Wigle credential fields, and SD card root contents. Here you can reconfigure your WLAN settings, download the contents of your SD card, and upload your wardriving logs directly to Wigle. Like the initial setup phase, there is a 60 second inactivity timeout. This means if you do not perform any actions on the web page for 60 seconds, the webserver will shutdown and normal wardriving operation will start. If the WLAN connection fails, the C5 Wardriver will start its own access point as described in Initial Setup.
During normal wardriving operation, the UP and DOWN buttons may be used to switch between display modes for different presentation of the wardriving status and statistic information.
The initial WiFi admin sequence at boot can be skipped by holding the SELECT button as soon as the boot logo appears.
The C5 Wardriver is capable of using multiple ESP32 modules as separate collection nodes with a single "Core" ESP32 to consolidate the collection data and save it to an SD card. The following section describes the process for selecting specific modes as well as the purpose for each mode. For Nodes and Cores to communicate, they do not require a physical connection to each other as their communication is conduction over-the-air. They are required to be within typical WiFi range of each other. When configuring the device mode from the Admin web interface, the device will boot into that mode from that point on. If selecting the mode from the menu directly on the device, the mode is temporary and will reset upon next boot.
Modes may be selected from the Admin web interface from Initial Setup or from the main menu if using a full display and button hardware setup.
Solo mode allows the C5 Wardriver to function as a standalone device which will collect and store data on its own. To function in solo mode, the device needs connection to an SD card and a GPS module and needs to have a GPS fix. While in Solo mode, users can upload logs directly to Wigle.
Node mode allows a device to collect wardriving data but instead of storing the data, it is given to a Core which is responsible for pairing the collection sata with location data and consolidating it into a wardriving log file. Nodes do not require SD card or GPS in order to function properly.
Core mode allows a device to receive wardriving data from Nodes. This data is paired with location data and saved to a wardriving log file. Cores require an SD card and GPS module in order to function properly. Cores themselves do not collect wardriving data and because of this, do not require any specific antenna configurations. Cores can upload directly to Wigle, same as Solo mode.
Communications between the Nodes and the Core can be encrypted. Encryption can be enabled using the Admin web interface from Initial Setup however there is an important caveat. If encryption is enabled, the number of nodes you may use at once is limited to six due to memory constraints. If encryption is disabled, the number of nodes you may use at once is theoretically unlimited.