I am finding the same - although I have tried flashing with NodeMCU flasher (works, no display activated in bin file) vs using Arduino IDE (doesn't work, display activated). It is showing packets being sent however. If I comment out the display, it works, however I also noticed that after the attack starts via the Arduino upload, connectivity to the device AP seems to drop on my phone - I don't recall a previous version doing this. (EDIT - #215 refers)
I have added additional menu point to send beacon attack, which works with oled display enabled no issues. Added a menu option to turn off display, because i thought that the display requires to much energy, even with turned off display the deauth attack is not working, though the serial monitor shows that the deauth attack packets are sent.
The code to turn display off is:
display.end();
display.displayOff();
pinMode(D1, OUTPUT);
pinMode(D2, OUTPUT);
digitalWrite(D1, LOW);
digitalWrite(D2, LOW);
which didn't help.
Thought might be the chip is unstable with display turned on, added a 1000uf capacitor between vcc and gnd pins, but this didn't help too.
First i thought that my code modification has caused the problem, but later i tried the default code from this repo which didn't work for me too.
Only when i comment the #define USE_DISPLAY line, the deauth attack works.
Tried 3 different esp8266 development boards, even without the display connected, all of them show the same behavior.
I also tried with the oled display, and to me it doesn't work the deauth attack.
I have the same problem, when I comment the line #define USE_DISPLAY works perfectly, I will try with a greater power source.
Found the bug!
Will be fixed in the next update.
Great work, thank you for your excellent project.
Most helpful comment
I have added additional menu point to send beacon attack, which works with oled display enabled no issues. Added a menu option to turn off display, because i thought that the display requires to much energy, even with turned off display the deauth attack is not working, though the serial monitor shows that the deauth attack packets are sent.
The code to turn display off is:
display.end(); display.displayOff(); pinMode(D1, OUTPUT); pinMode(D2, OUTPUT); digitalWrite(D1, LOW); digitalWrite(D2, LOW);which didn't help.
Thought might be the chip is unstable with display turned on, added a 1000uf capacitor between vcc and gnd pins, but this didn't help too.
First i thought that my code modification has caused the problem, but later i tried the default code from this repo which didn't work for me too.
Only when i comment the #define USE_DISPLAY line, the deauth attack works.
Tried 3 different esp8266 development boards, even without the display connected, all of them show the same behavior.