Testing DeAuther

[Splodgie]

Removed.

[spacehuhn]

To get you right, the deauth attack won't work with any of your devices? Also you have some troubles using different browsers -> https://github.com/spacehuhn/esp8266_deauther/issues/5 (just updated minutes ago, please check out).

[spacehuhn]

Ok. Have you read this(?):

Deauth attack won't work
If you see 0 pkts/s on the website you have made a mistake. Check if you have followed the the installation steps correctly and that the right SDK installed, it must be version 2.0.0! If it can send packets but your target don't loose its connection then the WiFi router uses 802.11w and it's protected against such attacks or they communicate via 5 GHz WiFi, which the ESP8266 doesn't support.

[D3VL-Jack]

To also add to this, I have NOT been very successful on deauthing and it's not 100% effective.

[D3VL-Jack]

Mainly FireFox, Although i have tried Chrome Mobile still to no avail. There may be a problem in the code as it was working on an earlier release. If i get some spare time later i'll fork it and have a play around, if i manage to fix it ill stick a pull request in and we can get it fixed in the main repo :)

That is unless @spacehuhn manages to patch it before.

[spacehuhn]

Would be great if you find the problem! I have no issues at all and I have tested it with a lot of different ESP8266 boards, networks and devices.

What you could try is using linux tools to make a deauth attack manually - if this works but the ESP8266s attack doesn't you could use wireshark to analyse if there is something wrong with the packets.

[D3VL-Jack]

You have pretty much read my mind!! I will setup a wireless network later and pipe it thru wire shark and attack it from my ESP first and then Kali as i know that works on my network.

Out of interest however, what wireless protocol are you testing yours on?

[D3VL-Jack]

@Splodgie In attack.h go to line 64 https://github.com/spacehuhn/esp8266_deauther/blob/master/esp8266_deauther/Attack.h#L64 and change the value from 0x01 to 0x05 and see if that unveils anything, i have successfully got it going on my network now, just waiting on #29 to be implemented now 😄

[spacehuhn]

Good to hear. If the reason-code is the problem then we can fix this pretty easy. I'm started to rewrite the attack class and enable multiple APs and advanced beacon flooding.

[D3VL-Jack]

Great! Looking forward to it, maybe an option could be to select a reason from a dropdown menu? A great list i found here http://www.aboutcher.co.uk/2012/07/linux-wifi-deauthenticated-reason-codes/

-Jack

[spacehuhn]

The tx power should be irrelevant. Either the client gets the deauth packet (then it should disconnect) or it doesn't recieve it. Like I said you can test this with wireshark and other linux tools.

[chinahk]

splogie, me folow how you say to install and it work ok or no instal me use chrome and it work fire fox as well no mor browser work but program not jam not stop workin phone i reed what you say for test an test you say do me test same as yoiu say and work all time jam must be mor power signal esp not router jam al time wot you test is true me find me find same or not work 55+ mor esp ok less not work thak for all people help chi.

[FirstPure]

Hi looking for help with this and found the information in this closed section. could not get this to work after installing went ok after some reading just would not boot any phone off. read the information that you found and tested it the much same way but cannot tell how to see the signal. but its like you say, jammer has to be very close to the phone your attacking for it to work 3/4 or more from the AP then it works just. how you going to find that out when you cannot see the phone your attacking or the AP its using its good if you want to jam your self 'He He'.

[spacehuhn]

Maybe the devices reconnect faster (within 1sec) than they get the next deauth packet. But even then because of the constant reconnecting, the network speed must be super slow.