What's new

Failed wifi connections still logged as successful?

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

rotareneg

Occasional Visitor
Is it normal for failed wifi connection attempts using the wrong key to be logged as successful anyway, just with a "station is leaving" deauth afterwards? This is on an RT-AC66U B1 running 3.0.0.4.386_51668.

Failed connection with incorrect wifi key:
Code:
Jan 19 12:07:56 syslog: wlceventd_proc_event(530): eth2: Auth xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:0
Jan 19 12:07:56 syslog: wlceventd_proc_event(559): eth2: Assoc xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:0
Jan 19 12:08:04 syslog: wlceventd_proc_event(494): eth2: Deauth_ind xx:xx:xx:xx:xx:xx, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-76

Successful connection with correct wifi key:
Code:
Jan 19 12:55:15 syslog: wlceventd_proc_event(530): eth2: Auth xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:0
Jan 19 12:55:15 syslog: wlceventd_proc_event(559): eth2: Assoc xx:xx:xx:xx:xx:xx, status: Successful (0), rssi:0
 
Ah, looks like WPA2 associates first and then does its handshakes, ect. afterwards, so that's probably normal. Still a little odd it doesn't say anything about the connection failing though.
 
follow this thread - you maybe facing the same problem.

 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top