Mirror/flock-you
1
0
Fork 0
mirror of https://github.com/colonelpanichacks/flock-you.git synced 2026-07-24 15:38:10 -07:00
Code Issues Packages Projects Releases Wiki Activity

Add credit for nsm_barii's original observations.

Browse Source
This commit is contained in:
DeFlock Joplin
2026-06-20 19:03:20 -05:00
parent 69696497d6
commit 2e694abf7f
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1 -1
View File
@@ -40,7 +40,7 @@ In the past, Flock cameras were detectable by the AP they were broadcasting for
These observations are not meant to cast doubt on anyone else's. These cameras are not managed well and are updated OTA.
Observations:
Flock cameras transmit wildcard probe requests on wi-fi channels in ascending order. These probes are emitted at around .125 second intervals. These probes are essentially a WiFi client asking any AP to respond with the SSID of the AP. Hidden SSIDs generally require you send the exact SSID in the probe to generate a response. See [here](https://goodwi.fi/posts/2023/12/hunt-for-hidden-probe/). Flock cameras are also known to use cellular LTE modems to upload to the Flock cloud.
Flock cameras transmit wildcard probe requests on wi-fi channels in ascending order. These probes are emitted at around .125 second intervals (credit to nsm_barii for orginal observations of both of these). These probes are essentially a WiFi client asking any AP to respond with the SSID of the AP. Hidden SSIDs generally require you send the exact SSID in the probe to generate a response. See [here](https://goodwi.fi/posts/2023/12/hunt-for-hidden-probe/). Flock cameras are also known to use cellular LTE modems to upload to the Flock cloud.
Given this, I have disabled all other detection methods in this branch. While they are associated with Flock cameras, they are essentially all echoes of the camera itself, which is only gated by OUI match. The other methods can fire when any OUI matched device is sending wildcard probes because nearby APs can respond and generate a false positive match on addr1 or addr3 methods.
main.cpp
+2 -2
View File
@@ -40,9 +40,9 @@
#define CHANNEL_MODE_SINGLE 2
#define CHANNEL_MODE CHANNEL_MODE_CUSTOM
#define CHANNEL_DWELL_MS 250
#define CHANNEL_DWELL_MS 250 // Changed to 2 x 125ms to aid in faster detection. 125ms is the observed hop time of the cameras (credit to nsm_barri for the observation).
#define SINGLE_CHANNEL 1
// Channel order reversed to aid in faster detection. Credit to nsm_barri for the observation on the ascending hop order of the cameras.
static const uint8_t customChannels[] = {11, 6, 1};
static const size_t customChannelCount = sizeof(customChannels) / sizeof(customChannels[0]);