mirror of
https://github.com/SpacehuhnTech/esp8266_deauther.git
synced 2026-04-26 00:05:55 +03:00
[GH-ISSUE #904] ESP can't detect stations properly #389
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#389
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 @ExploiTR on GitHub (Jun 26, 2018).
Original GitHub issue: https://github.com/SpacehuhnTech/esp8266_deauther/issues/904
I've 4 devices connected to victim AP. When I perform scan through serial (I've tried all possible commands)
it gives :
Can't understand where's the problem. AP is detected as normal.
@tobozo commented on GitHub (Jun 26, 2018):
make sure victim AP uses 2.4GHz band
@ExploiTR commented on GitHub (Jun 26, 2018):
@tobozo Hmm. I've said the AP is detected normally
I'm compiling from the 2.0.5 releases zip, without changing a single character of the code.
Tried
reset_sketchand flashed the compiled binary and got the same result.@tobozo commented on GitHub (Jun 26, 2018):
Please try to understand what dual band is, review the settings on your AP, then read the wiki and you'll see why the deauther can only see devices using the 2.4GHz band.
@ExploiTR commented on GitHub (Jun 26, 2018):
😭 😭 😭 😭 I do understand. @tobozo
Look, the AP is a Linksys E1200 N300 Router which only supports that 2.4 GHz band & channels 1-13.
And the stations are, desktop, one laptop and 2 phones which only support that 2.4GHz.
It worked last night. But, not working now 😭
@ExploiTR commented on GitHub (Jun 26, 2018):
The problem is persisting on the ESP side.
stopAP: 0 result null XstartAP: 1 device detected (3 connected)a really unusual problem, I just got the all 3 of them. but, not always 😭 😕
@ExploiTR commented on GitHub (Jun 26, 2018):
Look, it detects one now then none.. 😭 Looks like spacehunn will tag WTF again. :trollface:
@tobozo commented on GitHub (Jun 26, 2018):
don't worry I can do this for @spacehuhn
what kind of activity do you generate on the given devices in order to actually have packets to sniff ?
@ExploiTR commented on GitHub (Jun 26, 2018):
Can't understand
I tried
scan -a -t 30000|scan -st -t 30000and, tried connect-disconnect on stations while scan is running.. no result. It shows there is 0 pckts@spacehuhn commented on GitHub (Jun 26, 2018):
In other words, are there any packets it could be sniffing? Because maybe there is actually 0 packets per second on the channel the ESP is sniffing on.
EDIT:
maybe also post the whole serial output, could be helpful if something is wrong there
@ExploiTR commented on GitHub (Jun 26, 2018):
Doesn't it iterate through the channels by default? 😨 @spacehuhn
@ExploiTR commented on GitHub (Jun 26, 2018):
However, my AP is on channel 6, and the stations too..
I tried the command
scan -st -c 10But, after 30 scans, only one device is getting detected - from the first to the last.
@ExploiTR commented on GitHub (Jun 26, 2018):
@spacehuhn | I've turned off settings echo
set serialEcho false@spacehuhn commented on GitHub (Jun 26, 2018):
@ExploiTR but why?! Now we can't see what command you typed, which is kinda important for debugging you know... 😉
@ExploiTR commented on GitHub (Jun 26, 2018):
@spacehuhn , I've updated logcat
@spacehuhn commented on GitHub (Jun 26, 2018):
Thanks. Have you tried running the scanner somewhere else where there are more networks? Have you tried sniffing with other devices to make sure there are packet's beeing sent?
@ExploiTR commented on GitHub (Jun 26, 2018):
Well, opened virtual interfaces on my WRT. @tobozo
@spacehuhn
Command :
scan -aAnd the result is quite normal for the other 2 open networks
The 3rd device connected to my main network which is encrypted by WPA doesn't seem to be detected 😨
But, I'm quite sure that it's software isn't configured to use encrypted frames as, it worked last night 😕 🤔
@spacehuhn commented on GitHub (Jun 26, 2018):
Looks like it's working
@ExploiTR commented on GitHub (Jun 26, 2018):
?? How @spacehuhn ? I'm continuously trying it for hours. But, it doesn't even sometimes the other two on an open network isn't showing.
I've already ordered the NodeMCU V3 to test if the problem is persisting only in this V2 one. \O/
One thing also to notice, rebooting that shows perfect result (90% cases).
@killergeek commented on GitHub (Jun 26, 2018):
@ExploiTR yea i see the problem. its between the chair and the computer.
and something something RTFM.
@jLynx commented on GitHub (Jun 26, 2018):
Closed issue due to the issue being with the user, not the actual software. Sadly we don't provide help for this specific "clearly beta" version of user
@ExploiTR commented on GitHub (Jun 27, 2018):
@killergeek Welcome mate. Looks like went a long way through for the first comment. And, Secondly, being stubborn wouldn't help one - well? And, @killergeek first write a working project instead of forking before commenting
And, @jLynx @spacehuhn the issue is with the software. The way it detects stations isn't efficient. I know why this happened, and it's actually a bug. The devices aren't releasing any packet to save power somehow. So, as an open-source and without-warranty project, deauther wouldn't be detecting 100% of the devices using wifi tech and even not of them which don't use frame-encryption.
@jLynx commented on GitHub (Jun 27, 2018):
I dont see why you reacted to your own comment...
@jLynx commented on GitHub (Jun 27, 2018):
also @killergeek you just got TOLD, sit the f**k down kid! make a project before commenting 😂
@spacehuhn commented on GitHub (Jun 27, 2018):
This might look rude but let me document my reactions reading this word salat
oookaayy....
rly?!
Well now I'm hyped, tell me what you found young padawan!
🤦♂️ 🤦♀️ how is that a bug with the software then?! We already told you that you can only detect devices that send packets while your sniffing for those packets. It's common sense. You can't hear someone that isn't saying anything.
Oh jeez...
open-source and without-warranty projecthas nothing to do with the rest of your comment, so what's your point here?deauther wouldn't be detecting 100% of the devices using wifi techyes it can only detect active devices that use Wi-Fi. (kinda self explanatory, isn't it?)even not of them which don't use frame-encryption.Sniffing and detecting devices is absolutly unrelated to the Wi-Fi network encryption beeing used. There is a thing called MAC header in every 802.11 frame.Some extra notes:
@tobozo commented on GitHub (Jun 27, 2018):
Actually this thread is the aftermath of doing exactly that
Unless stated in the Code of conduct, using emojis instead of a GPG public key to sign messages does not invalidate the opening of an issue, I'd be more blaming github for that, why did they allow self-emojis in the first place ?
Anyway, most symptoms described here are from a different environment from the usual standard we hear about in this issue tracker.
The build @ExploiTR is trying to achieve is a Java client running on an Android and using the serial to talk to the deauther.
As a result there are mixed problems and mixed symptoms, hence the WTF smell and the fun reactions.
@ExploiTR commented on GitHub (Jun 27, 2018):
@spacehuhn No man, I'm not telling it in that way, I want to say that it wouldn't work when the devices are connected but not sending packets. Actually, I commented too fast being angry with killergeeks's comment. I'm sorry, it's my mistake to talk to a computer science student @spacehuhn
I just wanted to tell that @jLynx
No, it's global and wontfix. Again, sorry all for my languages pushed by killergeek
@spacehuhn commented on GitHub (Jun 27, 2018):
To sum this whole thing up:
I can't see anything wrong with the serial output you provided. You need devices that send packets and are connected to an AP that is in the list of the ESP8266. The more active the devices are, the higher the chance the ESP will find them.
If it is a software bug, tell us how to fix it.
@ExploiTR commented on GitHub (Jun 27, 2018):
By saying
not efficientI wanted actually to mean it's not official and wouldn't always be successful to detect all the devices.I don't know C/C++. And, I'm not an expert software engineer! But, one thing I can suggest. That is,
airodump-ng, I mean the wholeaircrack-ngpackage is written in C. And, I didn't see it failing to detect any stations being active or not. Will this help you?@spacehuhn commented on GitHub (Jun 27, 2018):
Aircrack suit has the same "problems". It can only see active devices. Only advantage is that it lists unconnected devices. But that wouldn't make sense here, since you can only attack connected devices.
Aircrack might give you more reliable results because it's running on dedicated hardware with much much more horsepower than this $2 chip and a real OS to schedule tasks and processes.
@ExploiTR commented on GitHub (Jun 27, 2018):
Okay. Thanks