Deauth in Logs / 4-way-handshake log entries

I replied to a previous comment with a long reply from GLt-iNet app o discover that I reached my reply limits from the app and that comment simply vanished in no where!

Yes, you are right, and my previous comment I spoke about more professional specific tools and software to achieve better results. I myself use a Kali Linux with a modified Realteek WLAN adapter that comes with a driver that permits packet injection and promiscuous mode with no further modifications even on Windows! It isn't Alpha though, and costs about 160 USD with detachable antennas.

I agree with you that flipper is a toy, but that is a heck of a all-in-one toy. With the Dev Marauder ESP32, spamming the AP with the same name, crating an Evil Portal, Rick Roll attacks is really really easy even for non experts

I used it to clone swimming pool NFC cards which my kid keeps losing, analyze my garage frequency and clone the RF signal, and gave a nice grin with Tesla charging door!

Yep. I currently use an Alfa adaptor with a Raspberry running Kali.

1 Like

I am using WPA3 and have a password 25 of letters numbers and symbols from a password generator, but are you saying these are deauths coming from somewhere because these are the only thing my router is logging.

Do you use WPA3 only?

No I have one 2.4 as WPA2 but I dont want to use it, I am 5 guest and 5 main on.

I am getting this every 45 seconds, fishy?

11:13:49 2024 kern.notice kernel: [194337.231991] 7986@C15L3,MlmeDeAuthAction() 1404: Send DEAUTH frame with ReasonCode(2)

So disable WPA2 completely and check the logs again.

OK, Im reading up on snort and going to dedicate some time to it.

My neighbor is always bragging about how he can break into networks, this is why I am doing this.

Snort is in the routers repo, know any good tutorials on it?

According Cisco:

Deauth reason 2 means that the previous authentication is no longer valid.

Meaning that you likely had changed between wpa2 and wpa3 this means the device hangs on a encryption key which no longer is recognized.

^ of course it is possible to sent a deauth with any code, but i see this as a very low chance, i see this always happen on my network after a upgrade some devices just work very broken in these scenarios even when i restart them, so its worth to identify them.

See it like ssl certificates for a bit as example, when this has been changed the certificate fail, likely due to the change, the router sents a different wpa2 key than before even though password remains unchanged, so it is advised to forget wifi and re-associate keys.

As for snort...

snort is very resource intensive you need atleast 4gb ram, while the flint 2 uses 7-8gb ram, it also shares it as storage, and a minimum requirement of a dual core, flint 2 uses quad so you are fine... but snort takes a while to correctly configure + i don't believe this version comes with ui.

^ then snort also constantly reads and writes, this is not so recommended on flash memory.

My advise if you really like a IDS system to have it appart from your router :slight_smile:

on the other hand you can also look into something lighter like banip, this is less evasive but blocks malicious ip.

This is happening every minute or so, is that normal?

Mon Nov 4 05:07:42 2024 kern.notice kernel: [172369.645918] 7986@C01L3,wifi_sys_conn_act() 1115: wdev idx = 1
Mon Nov 4 05:07:42 2024 kern.notice kernel: [172369.652010] 7986@C08L3,hw_ctrl_flow_v2_connt_act() 215: wdev_idx=1
Mon Nov 4 05:07:42 2024 kern.notice kernel: [172369.779986] 7986@C15L3,WPABuildPairMsg1() 5310: <=== send Msg1 of 4-way
Mon Nov 4 05:07:42 2024 kern.notice kernel: [172369.786730] 7986@C15L3,PeerPairMsg2Action() 6303: ===>Receive msg 2
Mon Nov 4 05:07:43 2024 kern.notice kernel: [172370.787965] 7986@C15L3,WPABuildPairMsg1() 5310: <=== send Msg1 of 4-way
Mon Nov 4 05:07:43 2024 kern.notice kernel: [172370.794702] 7986@C15L3,PeerPairMsg2Action() 6303: ===>Receive msg 2
Mon Nov 4 05:07:44 2024 kern.notice kernel: [172371.811987] 7986@C15L3,WPABuildPairMsg1() 5310: <=== send Msg1 of 4-way
Mon Nov 4 05:07:44 2024 kern.notice kernel: [172371.818735] 7986@C15L3,PeerPairMsg2Action() 6303: ===>Receive msg 2
Mon Nov 4 05:07:45 2024 kern.err kernel: [172372.835536] 7986@C15L1,WpaEAPOLRetryAction() 7790: 4Way-MSG1 timeout with 90:31:4b:1e:16:f7
Mon Nov 4 05:07:45 2024 kern.notice kernel: [172372.844051] 7986@C15L3,MlmeDeAuthAction() 1404: Send DEAUTH frame with ReasonCode(2) to 90:31:4b:1e:16:f7
Mon Nov 4 05:07:45 2024 kern.warn kernel: [172372.853871] 7986@C01L2,wifi_sys_disconn_act() 1002: wdev_idx=1
Mon Nov 4 05:07:45 2024 kern.notice kernel: [172372.860125] 7986@C08L3,hw_ctrl_flow_v2_disconnt_act() 172: wdev_idx=1
Mon Nov 4 05:07:45 2024 kern.warn kernel: [172372.867349] 7986@C13L2,MacTableDeleteEntry() 1938: Del Sta:90:31:4b:1e:16:f7
Mon Nov 4 05:07:48 2024 kern.debug kernel: [172375.647539] entrytb_aid_aquire(): found non-occupied aid:6, allocated from:4
Mon Nov 4 05:07:48 2024 kern.warn kernel: [172375.654689] 7986@C13L2,MacTableInsertEntry() 1577: New Sta:90:31:4b:1e:16:f7
Mon Nov 4 05:07:48 2024 kern.notice kernel: [172375.667332] 7986@C08L3,ap_cmm_peer_assoc_req_action() 1714: Recv Assoc from STA - 90:31:4b:1e:16:f7
Mon Nov 4 05:07:48 2024 kern.notice kernel: [172375.676760] 7986@C08L3,ap_cmm_peer_assoc_req_action() 2241: ASSOC Send ASSOC response (Status=0)...

Are you using an external USB Wi-Fi card manufactured by Altobeam?

why is my flint 2 doing a 4way hand shake every 4-5 seconds? It is attempting to do one if thats the correct terminology?

How did you determine that its happening every 4-5 seconds??

1 Like

Also you made similar posts about this, but not answered anything what steps you already perform to fix it.

On your post about de-authing here i already gave you a awnser.

So what did you do with it?, my suggestion was to reset devices wifi, did you?, did it still happen?

A de-auth can also be just a legitimate kick by the router, the de-auth reason code gives insight what it is, i noticed 2 which ment that the device mismatch with the matched key chain probably due a new initialization of a different wpa2 seed, and the client doesn't know how to handle a new request for the new crypto key, so you have to do that manual by forgetting the network and re-connecting to it.

But a de-auth packet can also be spoofed with a reason code in a attack, though i don't think this is happening, the truth is this type error is very common on older 2.4ghz devices especially when you upgrade the router, or changed seed these devices have no way to refresh it and stay on a broken handshake in where the router responds with reason 2.

1 Like

My router keeps doing this every 5 seconds. Chat GPT explains each line very well but I dont understand the hand shaking every 5 seconds....seems odd?

Sun Nov 10 00:08:31 2024 kern.notice kernel: [297781.489238] 7986@C15L3,MlmeDeAuthAction() 1404: Send DEAUTH frame with ReasonCode(2) to 90:31:4b:
Sun Nov 10 00:08:31 2024 kern.warn kernel: [297781.498918] 7986@C01L2,wifi_sys_disconn_act() 1002: wdev_idx=1
Sun Nov 10 00:08:31 2024 kern.notice kernel: [297781.505150] 7986@C08L3,hw_ctrl_flow_v2_disconnt_act() 172: wdev_idx=1
Sun Nov 10 00:08:31 2024 kern.warn kernel: [297781.512227] 7986@C13L2,MacTableDeleteEntry() 1938: Del Sta:90:31:4b:
Sun Nov 10 00:08:34 2024 kern.debug kernel: [297784.265660] entrytb_aid_aquire(): found non-occupied aid:5, allocated from:4
Sun Nov 10 00:08:34 2024 kern.warn kernel: [297784.272805] 7986@C13L2,MacTableInsertEntry() 1577: New Sta: MACADD
Sun Nov 10 00:08:34 2024 kern.notice kernel: [297784.284750] 7986@C08L3,ap_cmm_peer_assoc_req_action() 1714: Recv Assoc from STA - 90:31:4b:1e:16:f7
Sun Nov 10 00:08:34 2024 kern.notice kernel: [297784.294136] 7986@C08L3,ap_cmm_peer_assoc_req_action() 2241: ASSOC Send ASSOC response (Status=0)...
Sun Nov 10 00:08:34 2024 kern.notice kernel: [297784.303295] 7986@C01L3,wifi_sys_conn_act() 1115: wdev idx = 1
Sun Nov 10 00:08:34 2024 kern.notice kernel: [297784.309389] 7986@C08L3,hw_ctrl_flow_v2_connt_act() 215: wdev_idx=1
Sun Nov 10 00:08:34 2024 kern.notice kernel: [297784.437220] 7986@C15L3,WPABuildPairMsg1() 5310: <=== send Msg1 of 4-way
Sun Nov 10 00:08:34 2024 kern.notice kernel: [297784.447826] 7986@C15L3,PeerPairMsg2Action() 6303: ===>Receive msg 2
Sun Nov 10 00:08:35 2024 kern.notice kernel: [297785.449229] 7986@C15L3,WPABuildPairMsg1() 5310: <=== send Msg1 of 4-way
Sun Nov 10 00:08:35 2024 kern.notice kernel: [297785.455952] 7986@C15L3,PeerPairMsg2Action() 6303: ===>Receive msg 2
Sun Nov 10 00:08:36 2024 kern.notice kernel: [297786.473218] 7986@C15L3,WPABuildPairMsg1() 5310: <=== send Msg1 of 4-way
Sun Nov 10 00:08:36 2024 kern.notice kernel: [297786.484950] 7986@C15L3,PeerPairMsg2Action() 6303: ===>Receive msg 2

Posting the same question over and over again in new threads won't help you.

These messages are debug messages and you could simply ignore them. I guess you are running a beta firmware?

2 Likes

great ty, I had thought that dual posts may not take. ty