-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add MQTT publish #20
Comments
It should be possible, in the event of an attack being detected to step out of the main loop, connect to wifi network, then mqtt server and post a record. |
Hi @vongyver , i'm currently trying to implement the deauth detector into my home assistant + node-red build as sensor, so i can properly alert via App, Telegram, Lights, etc. |
Sadly, I deleted the code for this. If I recall I just was counting the
triggers and alerting when it increased within Node-Red.
Best of luck with the project! Thank you for the work.
…On Mon, Jul 3, 2023 at 7:11 AM chris-nite ***@***.***> wrote:
It should be possible, in the event of an attack being detected to step
out of the main loop, connect to wifi network, then mqtt server and post a
record. Alternatively, if you have a running Node-red instance with a
serial interface, you could read from the serial port and post to MQTT
within Node-red, which is what I am currently doing. I skipped the
timestamp from the esp32 because modding time is a pain. if (packet_rate>0)
{ Serial.print("{Channel:"); Serial.print(channels[ch_index]);
Serial.print(",Packets:"); Serial.print(packet_rate); Serial.println("}"); }
Hi @vongyver <https://github.com/vongyver> , i'm currently trying to
implement the deauth detector into my home assistant + node-red build as
sensor, so i can properly alert via App, Telegram, Lights, etc.
Would you be kind enough to share your Node-Red-Template for properly
splitting up the serial input into a MQTT-Topic?
Thanks in advance and best regards.
—
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AASTLSWASEJDZU4MRGUURJLXOLAHLANCNFSM5TSTIJNA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Wouldn't it be a nice improvement to add a function that publishes the channel number where an deauth attack has been identified (LED on) to a pre-configured MQTT broker?
The broker would implicitly record the UTC for the event for later deep analysis.
More ideas on this proposed enhancement welcome...
The text was updated successfully, but these errors were encountered: