mirror of
https://github.com/SpacehuhnTech/esp8266_deauther.git
synced 2026-04-26 16:25:54 +03:00
[GH-ISSUE #133] Disconnects upon deauth #94
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#94
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 @Clon3d on GitHub (Mar 19, 2017).
Original GitHub issue: https://github.com/SpacehuhnTech/esp8266_deauther/issues/133
Please read issues.md
and the readme
before posting a new issue. Thanks!
Hello, using version 1.1 bin. whenever I try to death it says starting then loses all connection causing me to have to do a full reboot and does not work against the wifi networks. I tried version 2.0 but will not compile correctly following your exact instructions. please reply or PM me for details. thanks
@Niklaus1911 commented on GitHub (Mar 21, 2017):
i have the same issue...
@spacehuhn commented on GitHub (Mar 22, 2017):
What does it say in the serial monitor?
You need the SDK version 2.0.0. If you get an error than that's an other issue.
@RMOA789 commented on GitHub (Mar 23, 2017):
Same issue. For some APs it's working well without disconnecting, but for other APs, I get an unavailable webpage. Already tried with different smartphones.
Flashing with the bin file from the git.
@elliot12 commented on GitHub (Mar 31, 2017):
Also the same issue. I can deauth an entire network but when scanning for devices on the network to deauth individually the esp8266 restarts. Other than that though, its working 100%. Thanks for the great work @spacehuhn 👍
@jLynx commented on GitHub (Mar 31, 2017):
I also have this issue
Running Android 7.1.1
@jLynx commented on GitHub (Mar 31, 2017):
I have noticed, if im connected to the deauther on my computer it works fine, but if I try it on my phone it does exactly what the problem describes. But im not sure, it could just be a coincidence
@spacehuhn commented on GitHub (Mar 31, 2017):
Your problem is that it's getting disconnected when scanning for clients?
@elliot12 commented on GitHub (Mar 31, 2017):
Correct. It won't let me see individual devices on a given AP. It just
disconnects and comes on again about 10-15 seconds after but still doesn't
show me the clients. I used the bin file btw.
On 31 Mar 2017 10:22, "Stefan Kremser" notifications@github.com wrote:
@spacehuhn commented on GitHub (Mar 31, 2017):
It's normal that it disconnects, it has to do that in order to scan for devices.
To find devices they have to send packets while you are scanning, so make sure you generate some traffic in this network (by loading a site for example).
Also note that if your network has 2.4 and 5Ghz it will only find the devices which are using the 2.4Ghz connection.
@Fireflaker commented on GitHub (Mar 31, 2017):
Would it be possible to develop it based on ESP32? It is just as cheap and
has 2x 160MHz cores with both bluetooth and wifi. The dual core should make
coding a lot easier.
Stefan Kremser notifications@github.com于2017年3月31日 周五上午11:04写道：
@spacehuhn commented on GitHub (Mar 31, 2017):
The ESP32 isn't able to inject packets, so no :(
@jLynx commented on GitHub (Apr 2, 2017):
This is the problem I am having https://imgur.com/iSISaNa
It gets to starting then times out the page when it try to reload. But it does stay connected to the device, as per the WiFi icon in the notification bar. But I cannot access any page from it now until I reset the power
@spacehuhn commented on GitHub (Apr 2, 2017):
Yeah... I still need the serial log from you guys.
@jLynx commented on GitHub (Apr 2, 2017):
@spacehuhn Oops sorry didn't see that message
Ok..typical... it works this time. Anyway here is my log https://pastebin.com/qWd5MFZw
On line 85 it finally shows the page again with 8pkts where normally it wouldn't get that far and timeout like I explained earlier
@spacehuhn commented on GitHub (Apr 2, 2017):
thank you. The device isn't crashing and doesn't throw any other error.
@jLynx commented on GitHub (Apr 2, 2017):
I have tested it 2 other times since that post and both have timed out, no error messages or anything out of the ordinary.
@spacehuhn commented on GitHub (Apr 2, 2017):
Sorry I didn't want to close it! (stupid phones..)
Anyway...
can you access the website with another device?
@jLynx commented on GitHub (Apr 2, 2017):
Yes on my desktop I have no problems (So same test, phone cant connect once deauthing but desktop can). Just tried again and and it worked perfectly like it should and instantly started deauthing, where before in that log I sent it took at least 30 seconds or more before it started working (Website showing up anyway).
Its as if some thread is blocking the web server from working or something like that
@spacehuhn commented on GitHub (Apr 2, 2017):
OK yes that's really weird. It's not like that the ESP8266 doesn't send the website or something, because then it also wouldn't work with your PC.
@jLynx commented on GitHub (Apr 2, 2017):
Could it be a way Android's Chrome handles the requests or something?
@jLynx commented on GitHub (Apr 2, 2017):
Ok it just happened again while logging, and there is no crashes just the constant running deauth attack message. no matter what I did on my phone I could not access it. I tried disconnecting and reconnecting and that didn't work, but on my desktop I connected to the point and I can see the attack still running and then stop it with no problems.
Now i'm getting timeout (took too long to respond) with a 504 error on my phone trying to load the site, but no errors in the logs in console
@spacehuhn commented on GitHub (Apr 8, 2017):
I maybe found a solution.
Scan for the network you want to deauth. Look what channel it uses and then go to settings and set the channel to the same value.
Then restart your ESP8266 and try to deauth that network.
I shouldn't loose the connection then.
@jLynx commented on GitHub (Apr 10, 2017):
That seems to fix the problem! Thanks @spacehuhn
Now do you think it's possible to fix this in software or is it just a problem we will have to live with?
@jLynx commented on GitHub (Apr 17, 2017):
@spacehuhn can this issue be closed now?