mirror of
https://github.com/SpacehuhnTech/esp8266_deauther.git
synced 2026-04-26 00:05:55 +03:00
[GH-ISSUE #141] General Client Scan Issue #102
Labels
No labels
best of
bug
development
discussion
documentation
duplicate
feature request
help wanted
help wanted
improvement
pinned
pull-request
question
stale
translation
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/esp8266_deauther#102
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @BusesCanFly on GitHub (Mar 25, 2017).
Original GitHub issue: https://github.com/SpacehuhnTech/esp8266_deauther/issues/141
First off, phenomenal work! I'm blown away by this!
Everything seems to work flawlessly, except with the client scan. It seems that the scan is a race against how fast your browser decides to error out of the page because you have no internet connection (As the esp has only one antenna). The maximum scan length I can do before chrome decides to error out the page because of no internet is 5 seconds, which does not detect a large amount of clients. Am I making a noob mistake, or is this just something that'll have to be like this?
@epiller commented on GitHub (Mar 25, 2017):
The ESP8266 AP is turned off while scanning for clients - which means that your phone/computer will disconnect from it in about 5 seconds. All you need to do is connect to the ESP8266 AP again and refresh the clients page.
@BusesCanFly commented on GitHub (Mar 25, 2017):
Thank you for the response!
Right, this is the client v monitor mode idea, with only on interface. However, after the automatic reconnect, I do not have any clients picked up, even when connected to 15+ AP's. However, in the 5 second window, I can pick up one client sometimes. I doubt its the effect of the browser directly, as its all on the ESP, but maybe the connection registering is resetting the client scan?
@epiller commented on GitHub (Mar 25, 2017):
Well, this concludes that I'm not the only one having that issue. I just posted it a few minutes ago here.