mirror of
https://github.com/SpacehuhnTech/esp8266_deauther.git
synced 2026-04-26 08:15:51 +03:00
[GH-ISSUE #106] [Version Request] ESP32 implementation #74
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#74
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 @tobozo on GitHub (Mar 10, 2017).
Original GitHub issue: https://github.com/SpacehuhnTech/esp8266_deauther/issues/106
Seems like ESP8266 running complex apps over networking are in danger of transient global heap underrun (sounds scary and I have no idea what this means).
In the comments, they say the ESP32 has enough memory to escape this problem. What is the problem with the ESP32 SDK (apart from the cryptic post saying only ARP can be fiddled with)?
Is there a workaround like there is with SKD 2.0.0 / ESP8266?
@spacehuhn commented on GitHub (Mar 10, 2017):
that's the problem. Have you read the forum post I attached to the links in the readme?
http://esp32.com/viewtopic.php?f=13&t=586&p=2648&hilit=wifi_send_pkt_freedom#p2648
They completely removed the
wifi_send_pkt_freedomfunction from the esp32 SDK and without that you can't inject packets. And the newesp_wifi_internalfunction can't be used for that.I couldn't find other functions for packet injection.
@spacehuhn commented on GitHub (Mar 10, 2017):
Also very informative: https://esp32.com/viewtopic.php?p=3053#p3053
@tobozo commented on GitHub (Mar 10, 2017):
Ok I guess we can't just recycle the code from the ESP8266, but does it mean ESP32 cannot do packet injection (hardware wise), or does it just mean Espressif won't provide any code that would allow it?
Also I don't understand the posture, denying free packets but allowing ARP spoofing sounds a bit schizophrenic. If this is a lost cause I'll just close the issue and yell at my ESP32's.
@spacehuhn commented on GitHub (Mar 10, 2017):
yes exectly! You'd have to rewrite their code which is not open source :(
I thought that too, but as it turns out it's not easy. The
esp_wifi_internalfunction is really internal only and get's super buggy when using it, but in theory it could send (for example) ARP packets.I do that too from time to time... 😄
@dwillmore commented on GitHub (Aug 16, 2018):
Does this change the ability of the ESP32 to support deauther?
@spacehuhn commented on GitHub (Dec 12, 2021):
Hi! There are many issues on this repo about ESP32 support, so I published a blog post to bring some clarity to this topic: https://blog.spacehuhn.com/esp32-deauther/
TL;DR: It's made for the ESP8266, and I have no plans to port this application to the ESP32. But it's open-source, so you're free to do it yourself if you want. I appreciate your understanding.