Flipper Zero/Rogue AP Detector - Revision history

Admin: /* Implementation */

2026-06-20T04:44:51Z

Implementation

← Older revision		Revision as of 04:44, 20 June 2026
Line 98:		Line 98:
	* Extract: SSID, BSSID, RSSI, encryption type, channel		* Extract: SSID, BSSID, RSSI, encryption type, channel
	* Return structured AP data array		* Return structured AP data array

	~~[[Flipper Zero/Rogue AP Detector/scanner.c]]~~

	==Step 2 - Baseline Manager (baseline.c)==		==Step 2 - Baseline Manager (baseline.c)==
Line 107:		Line 105:
	* Data aging (remove old entries, update signal ranges)		* Data aging (remove old entries, update signal ranges)
	* Handle storage limitations on Flipper Zero		* Handle storage limitations on Flipper Zero

	~~[[Flipper Zero/Rogue AP Detector/baseline.c]]~~

	==Step 3 - Analysis Engine (analyzer.c)==		==Step 3 - Analysis Engine (analyzer.c)==
Line 119:		Line 115:
	* Analyze signal strength patterns		* Analyze signal strength patterns
	* Generate suspicion scores (0-100)		* Generate suspicion scores (0-100)

	~~[[Flipper Zero/Rogue AP Detector/analyzer.c]]~~

	==Step 4 - Detection Logic (detector.c)==		==Step 4 - Detection Logic (detector.c)==
Line 128:		Line 122:
	* Classify threat types: typosquatting, signal anomaly, unknown device		* Classify threat types: typosquatting, signal anomaly, unknown device
	* Maintain detection history to reduce false positives		* Maintain detection history to reduce false positives

	~~[[Flipper Zero/Rogue AP Detector/detector.c]]~~

	==Step 5 - User Interface (ui.c)==		==Step 5 - User Interface (ui.c)==
Line 137:		Line 129:
	* Alert interface for rogue APs		* Alert interface for rogue APs
	* Settings menu for thresholds		* Settings menu for thresholds

	~~[[Flipper Zero/Rogue AP Detector/ui.c]]~~

Unknown user at 17:23, 26 August 2025

2025-08-26T17:23:12Z

← Older revision		Revision as of 17:23, 26 August 2025
Line 1:		Line 1:
	{{Main\|Flipper Zero}}		{{Main\|Flipper Zero}}

			This page covers a project that implements a rogue AP detector using a Flipper Zero, ESP32 board, and a C program running on the Flipper Zero. The C program collects background observations about wifi networks to create a baseline, then performs analysis scans to compare to the baseline and identify possible Rogue APs.

	__TOC__		__TOC__

Unknown user at 17:14, 26 August 2025

2025-08-26T17:14:09Z

← Older revision		Revision as of 17:14, 26 August 2025
Line 1:		Line 1:
			{{Main\|Flipper Zero}}

	__TOC__		__TOC__

Unknown user: /* Step 5 - User Interface (ui.c) */

2025-08-26T12:23:41Z

Step 5 - User Interface (ui.c)

← Older revision		Revision as of 12:23, 26 August 2025
Line 133:		Line 133:
	* Alert interface for rogue APs		* Alert interface for rogue APs
	* Settings menu for thresholds		* Settings menu for thresholds

			[[Flipper Zero/Rogue AP Detector/ui.c]]

Unknown user: /* Step 4 - Detection Logic (detector.c) */

2025-08-26T12:23:28Z

Step 4 - Detection Logic (detector.c)

← Older revision		Revision as of 12:23, 26 August 2025
Line 124:		Line 124:
	* Classify threat types: typosquatting, signal anomaly, unknown device		* Classify threat types: typosquatting, signal anomaly, unknown device
	* Maintain detection history to reduce false positives		* Maintain detection history to reduce false positives

			[[Flipper Zero/Rogue AP Detector/detector.c]]

	==Step 5 - User Interface (ui.c)==		==Step 5 - User Interface (ui.c)==

Unknown user: /* Step 3 - Analysis Engine (analyzer.c) */

2025-08-26T11:57:28Z

Step 3 - Analysis Engine (analyzer.c)

← Older revision		Revision as of 11:57, 26 August 2025
Line 115:		Line 115:
	* Analyze signal strength patterns		* Analyze signal strength patterns
	* Generate suspicion scores (0-100)		* Generate suspicion scores (0-100)

			[[Flipper Zero/Rogue AP Detector/analyzer.c]]

	==Step 4 - Detection Logic (detector.c)==		==Step 4 - Detection Logic (detector.c)==

Unknown user: /* Step 3 - Analysis Engine (analyzer.c) */

2025-08-26T11:57:11Z

Step 3 - Analysis Engine (analyzer.c)

← Older revision		Revision as of 11:57, 26 August 2025
Line 107:		Line 107:

	==Step 3 - Analysis Engine (analyzer.c)==		==Step 3 - Analysis Engine (analyzer.c)==

			(This is arguably the module that is at the heart of the project - how you detect rogue APs)

	* Compare current scan vs baseline		* Compare current scan vs baseline

Unknown user: /* Step 2 - Baseline Manager (baseline.c) */

2025-08-26T11:28:42Z

Step 2 - Baseline Manager (baseline.c)

← Older revision		Revision as of 11:28, 26 August 2025
Line 103:		Line 103:
	* Data aging (remove old entries, update signal ranges)		* Data aging (remove old entries, update signal ranges)
	* Handle storage limitations on Flipper Zero		* Handle storage limitations on Flipper Zero

			[[Flipper Zero/Rogue AP Detector/baseline.c]]

	==Step 3 - Analysis Engine (analyzer.c)==		==Step 3 - Analysis Engine (analyzer.c)==

Unknown user: /* Step 1 - Wifi Scanner Module scanner.c */

2025-08-25T23:17:49Z

Step 1 - Wifi Scanner Module scanner.c

← Older revision		Revision as of 23:17, 25 August 2025
Line 94:		Line 94:
	* Extract: SSID, BSSID, RSSI, encryption type, channel		* Extract: SSID, BSSID, RSSI, encryption type, channel
	* Return structured AP data array		* Return structured AP data array

			[[Flipper Zero/Rogue AP Detector/scanner.c]]

	==Step 2 - Baseline Manager (baseline.c)==		==Step 2 - Baseline Manager (baseline.c)==

Unknown user at 23:01, 25 August 2025

2025-08-25T23:01:24Z

@@ Line 1: / Line 1: @@
 =Plan=
@@ Line 80: / Line 83: @@
 * Implement circular buffer for recent scan results
 * Limit active monitoring to ~50 APs simultaneously