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

ESP8266mini-sniff connected to local Wifi #1

Open
hofi-jus opened this issue Aug 24, 2017 · 7 comments
Open

ESP8266mini-sniff connected to local Wifi #1

hofi-jus opened this issue Aug 24, 2017 · 7 comments

Comments

@hofi-jus
Copy link

Hello,
is it possible to connect the mini sniffer to a local wifi?
As you can read here schollz/find-lf#17

It would be perfect to find my phone in house,
if i can place some mini sniffer nodes in my house and these node would connect to
my wifi. So i can look up where it is or was at least.

@rw950431
Copy link
Owner

I think the critical point from https://github.com/schollz/find-lf is

each Raspberry pi has a USB Wifi adapter that supports "monitor mode", like the TL-WN722N, and it additionally has a second internet connection via ethernet or another adapter

I am fairly certain that its not possible to connect to a wifi access point while in monitor mode. I do have some code that periodically drops out of monitor mode, connects to an access point and reports its data but I haven't published it yet due to it some other problems I'm having with it. The other option might be to use 2 ESP8266 modules wired together via the serial ports so that one is the monitor and the other transmits back to base- 2 cheap ESP8266 modules might still be cheaper than a Raspberry Pi

@hofi-jus
Copy link
Author

Hi,
thanks for fast replay.
How fast can switching be done?
Only for finding my phone 5s are ok but for movement tracking its to slow ^^
A second one was also my thought, but when its not needed.
I also try to use esp with ethernet shild so it would also be possible to transmit packages.

@rw950431
Copy link
Owner

rw950431 commented Aug 26, 2017

My code was taking about 7 seconds to connect & transmit on my home router. It went down to around 4 seconds if I used a static IP address rather than waiting for DHCP.

I'm finding that many devices don't transmit regularly unless they are being actively used so making it harder to keep track of them. (Probably done to maximize battery life).

@hofi-jus
Copy link
Author

Oh ok,
Only for finding my business phone where I can not install apps it would be great ^^

@hofi-jus
Copy link
Author

Hi,
just tried to get your project to work with my node mcu v3.
Can you tell me wich folder and data should be where?
Downloading the zip and extracting it to sketch folder does not work :(
Kind regards

@rw950431
Copy link
Owner

rw950431 commented Oct 4, 2017

Maybe you can try combining both the ino files into one big one and see if that helps? It seems that multiple-file projects are still a bit fragile under arduino IDE (I compiled mine using Visual Studio Code and it worked OK although I had to specify which was the main sketch file)

@Hummer75
Copy link

Hummer75 commented Oct 4, 2017

Perhaps this will sort my problem to...? If I combine them?

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

3 participants