Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 4 subscribers
  • Views 1671 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

new Dyson fan & Samsung Galaxy won't connect to Wifi

SalishSwede

I have a fairly fancy fan that monitors all sorts of air quality metrics.
The thing operates best through the wifi app.

I had it running for months just fine then dissociated it from the Sophos UTM-Access Point and now it won't connect.

The logs show the following:

2023:01:31-18:07:48 P110012KQP8G77A hostapd: ath100: STA 50:14:79:8a:ba:60 IEEE 802.11: associated
2023:01:31-18:07:48 P110012KQP8G77A hostapd: ath100: STA 50:14:79:8a:ba:60 WPA: AP-STA-POSSIBLE-PSK-MISMATCH
2023:01:31-18:07:48 P110012KQP8G77A kernel: [6105847.055098] [wifi1] FWLOG: [4557769] RATE: ChainMask 1, peer_mac ba:60, phymode 6, ni_flags 0x00203006, vht_mcs_set 0x0000, ht_mcs_set 0x00ff, legacy_rate_set 0x0ff0
2023:01:31-18:07:48 P110012KQP8G77A kernel: [6105847.055120] [wifi1] FWLOG: [4557769] RTT_REPORT ( 0x2804, 0x3, 0x479, 0x0, 0x9 )
2023:01:31-18:07:49 P110012KQP8G77A hostapd: ath100: STA 50:14:79:8a:ba:60 WPA: AP-STA-POSSIBLE-PSK-MISMATCH
2023:01:31-18:07:50 P110012KQP8G77A hostapd: ath100: STA 50:14:79:8a:ba:60 WPA: AP-STA-POSSIBLE-PSK-MISMATCH
2023:01:31-18:07:51 P110012KQP8G77A hostapd: ath100: STA 50:14:79:8a:ba:60 WPA: AP-STA-POSSIBLE-PSK-MISMATCH
2023:01:31-18:07:52 P110012KQP8G77A hostapd: ath100: STA 50:14:79:8a:ba:60 IEEE 802.11: disassociated
2023:01:31-18:07:52 P110012KQP8G77A hostapd: ath100: STA 50:14:79:8a:ba:60 IEEE 802.11: Disassoc - Previous auth not valid (code:2)
2023:01:31-18:07:52 P110012KQP8G77A kernel: [6105850.305544]
2023:01:31-18:07:52 P110012KQP8G77A kernel: [6105850.305544] wlan_mlme_disassoc_request_with_callback 482 50:14:79:8a:ba:60 reason 2
2023:01:31-18:08:21 P110012KQP8G77A kernel: [6105879.463104]
2023:01:31-18:08:21 P110012KQP8G77A kernel: [6105879.463104] ieee80211_mlme_recv_disassoc 1633 c8:ff:77:51:55:17 reason 8
2023:01:31-18:08:21 P110012KQP8G77A hostapd: ath100: STA c8:ff:77:51:55:17 IEEE 802.11: disassociated
2023:01:31-18:08:21 P110012KQP8G77A hostapd: ath100: STA c8:ff:77:51:55:17 IEEE 802.11: Disassoc - client has left (code:8)

I'm using a password manager for setting the password on the UTM.  This syncs via cloud with my phone so there should be no  typos/incorrect passwords.  To check, I 'forgot' my wifi password on my cell phone and attempted to reconnect using the validated password on my password manager.  My cell phone won't connect.

The logs from the cell phone fail are...

2023:01:31-18:15:31 P110012KQP8G77A hostapd: ath100: STA c8:ff:77:51:55:17 IEEE 802.11: associated
2023:01:31-18:15:31 P110012KQP8G77A hostapd: ath100: STA c8:ff:77:51:55:17 WPA: AP-STA-POSSIBLE-PSK-MISMATCH
2023:01:31-18:15:31 P110012KQP8G77A kernel: [6106310.357806] [wifi1] FWLOG: [147905] RATE: ChainMask 1, peer_mac 55:17, phymode 4, ni_flags 0x00041006, vht_mcs_set 0x0000, ht_mcs_set 0x00ff, legacy_rate_set 0x0ff0
2023:01:31-18:15:31 P110012KQP8G77A kernel: [6106310.357827] [wifi1] FWLOG: [147905] RTT_REPORT ( 0x2804, 0x3, 0x479, 0x0, 0x9 )
2023:01:31-18:15:32 P110012KQP8G77A hostapd: ath100: STA c8:ff:77:51:55:17 WPA: AP-STA-POSSIBLE-PSK-MISMATCH
2023:01:31-18:15:33 P110012KQP8G77A hostapd: ath100: STA c8:ff:77:51:55:17 WPA: AP-STA-POSSIBLE-PSK-MISMATCH
2023:01:31-18:15:34 P110012KQP8G77A hostapd: ath100: STA c8:ff:77:51:55:17 WPA: AP-STA-POSSIBLE-PSK-MISMATCH
2023:01:31-18:15:35 P110012KQP8G77A hostapd: ath100: STA c8:ff:77:51:55:17 IEEE 802.11: disassociated
2023:01:31-18:15:35 P110012KQP8G77A hostapd: ath100: STA c8:ff:77:51:55:17 IEEE 802.11: Disassoc - Previous auth not valid (code:2)
2023:01:31-18:15:35 P110012KQP8G77A kernel: [6106314.280751]
2023:01:31-18:15:35 P110012KQP8G77A kernel: [6106314.280751] wlan_mlme_disassoc_request_with_callback 482 c8:ff:77:51:55:17 reason 2

What seems to be the problem. 

I'm not seeing it.
AP-STA-POSSIBLE-PSK-MISMATCH doesn't clear it up for me.
I see another thread by me with the same issue 4 months ago.
Alas I don't recall what the fix was.  I'm locked out of the Wifi Network.

Update: My desktop connects just fine...

2023:01:31-18:41:13 P110012KQP8G77A hostapd: ath100: STA a8:64:f1:ec:e9:38 IEEE 802.11: associated
2023:01:31-18:41:13 P110012KQP8G77A hostapd: ath100: STA a8:64:f1:ec:e9:38 RADIUS: starting accounting session 3DCC4970-0000003A
2023:01:31-18:41:13 P110012KQP8G77A hostapd: ath100: STA a8:64:f1:ec:e9:38 WPA: pairwise key handshake completed (RSN)
2023:01:31-18:41:13 P110012KQP8G77A kernel: [6107851.762766] [wifi1] FWLOG: [1725930] RATE: ChainMask 3, peer_mac e9:38, phymode 9, ni_flags 0x0203b006, vht_mcs_set 0xfffa, ht_mcs_set 0xffff, legacy_rate_set 0x0ff0
2023:01:31-18:41:13 P110012KQP8G77A kernel: [6107851.762788] [wifi1] FWLOG: [1725931] RTT_REPORT ( 0x2804, 0x3, 0x479, 0x0, 0x9 )
2023:01:31-18:41:13 P110012KQP8G77A kernel: [6107851.762820] [wifi1] FWLOG: [1726006] RATE: ChainMask 3, peer_mac e9:38, phymode 10, ni_flags 0x0203b006, vht_mcs_set 0xfffa, ht_mcs_set 0xffff, legacy_rate_set 0x0ff0
2023:01:31-18:42:27 wahine awed[5229]: [MASTER] start processing configuration change
2023:01:31-18:42:27 wahine awed[5229]: [MASTER] end processing configuration change


This thread was automatically locked due to age.
Parents
  • 0

    One thing I could think of is that maybe the fan is set to use a different encryption standard than the sophos wireless protection is set for..

    Ex. the fan uses TPK/WEP and the access point is set for WPA2/AES.

    Or the password is wrong like Amodin says.

    You did make the same post 4 months ago and seem to be having a lot of issues with your Vivint network in general after your neighbor, the retired database engineer, placed a nefarious device on you front lawn. 

    So basically check the following things:

    Make sure the fan is set to use the same encryption standard as the access point. 

    Check the password. If this fan worked fine a few months ago, then go to Management and see if you made any changes.

    To recreate your logs, I typed the password incorrectly on my own device and the logs simply don't match those of an incorrect password. If it were a matter of simply entering the wrong password, the logs would say:

    "name="STA WPA failure"

    and then...

    "IEEE 802.11: deauthenticated due to local deauth request"

    EDIT: I see your post history and it seems a few times you created a post asking for help, people reply with questions, and you don't reply back.

Reply
  • 0

    One thing I could think of is that maybe the fan is set to use a different encryption standard than the sophos wireless protection is set for..

    Ex. the fan uses TPK/WEP and the access point is set for WPA2/AES.

    Or the password is wrong like Amodin says.

    You did make the same post 4 months ago and seem to be having a lot of issues with your Vivint network in general after your neighbor, the retired database engineer, placed a nefarious device on you front lawn. 

    So basically check the following things:

    Make sure the fan is set to use the same encryption standard as the access point. 

    Check the password. If this fan worked fine a few months ago, then go to Management and see if you made any changes.

    To recreate your logs, I typed the password incorrectly on my own device and the logs simply don't match those of an incorrect password. If it were a matter of simply entering the wrong password, the logs would say:

    "name="STA WPA failure"

    and then...

    "IEEE 802.11: deauthenticated due to local deauth request"

    EDIT: I see your post history and it seems a few times you created a post asking for help, people reply with questions, and you don't reply back.

Children
No Data
Unfiltered HTML