Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for passive scanning #1

Open
DatanoiseTV opened this issue Mar 26, 2018 · 12 comments
Open

Add support for passive scanning #1

DatanoiseTV opened this issue Mar 26, 2018 · 12 comments

Comments

@DatanoiseTV
Copy link
Owner

This is WiP. Partial passive scanning is done, but not committed here yet.

@maddog986
Copy link

I would love to see passive scanning added.

@david81
Copy link

david81 commented Nov 1, 2018

Agreed. I'd be happy to help with the effort if you're willing to share the WIP.

@imtoori
Copy link

imtoori commented Nov 11, 2018

Available for help if needed. This is a really useful feature for me

@IoTThinks
Copy link

IoTThinks commented Nov 14, 2018

Yeap. I really love to have this passive scanning feature, too.
Pi is quite heavy stack to be deploy in bigger scale like shopping malls...

If needed, I can join the testing or fixing force :D

@ItsEcholot
Copy link

Any update on this? What needs to be done to implement this?

@jekkos
Copy link

jekkos commented Nov 26, 2018

Jut a matter of getting a hold of any probe requests, their mac address and rssi signal strength mean over a time interval. Then this result should be posted to the find server over http. I had some basic example done some time ago for this

@ItsEcholot
Copy link

ItsEcholot commented Nov 27, 2018

@jekkos

Jut a matter of getting a hold of any probe requests, their mac address and rssi signal strength mean over a time interval. Then this result should be posted to the find server over http. I had some basic example done some time ago for this

Could you send me your example or post it somewhere? It doesn't seem overly complicated but I sure would like to see your implementation. Reading through the esp-find3-client code it seems like there is an issue implementing both a wlan connetion and scanning for BLE devices because of partition space?

@jacobalberty
Copy link

jacobalberty commented Jan 21, 2019

@ItsEcholot this looks like what he's talking about. The only thing is It's only going to get things actively scanning. The http post would also need to be modified for find3 and it will only get things actively scanning, clients already associated are going to be sending out fewer probe requests so it'll be less accurate and it will only be scanning one channel

@jacobalberty
Copy link

I'm working on something based on https://github.com/rw950431/ESP8266mini-sniff , the problem is it won't allow you to sniff while connected as a station. I'm thinking set a configurable interval and run for a few seconds and submit what it sees.

@IoTThinks
Copy link

I'm working on something based on https://github.com/rw950431/ESP8266mini-sniff , the problem is it won't allow you to sniff while connected as a station. I'm thinking set a configurable interval and run for a few seconds and submit what it sees.

Of course, you need to change wifi mode.
I'm also trying do one for ESP32.

@jacobalberty
Copy link

@IoTThinks if you want to see what I have going on heres my repo https://github.com/jacobalberty/esp8266-find-passive

I'm just sniffing for 10 seconds (and changing cycling through the channels every 1/14th of that) then connecting to wifi. I need to add the code to change it to json and posting the data. I may also switch to using WifiManager for new setups to handle configuration. but so far the sniff and switch to wifi seems fairly stable. It's mostly esp8266mini-sniff i just trimmed down the unneeded stuff from functions.h and instead of sniffing each channel till nothing new I do it on a set timer.

@gomme600
Copy link

Was this ever implemented ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants