Wi-Fi: laptop yes, phone no
-
@stephenw10 said in Wi-Fi: laptop yes, phone no:
Because it's configured for WPA Ent I imagine.
If Ent means "Enterprise" then its not - its WPA2 with Pre-shared Key and AES
-
Huh, interesting. Checking....
-
@fireodo said in Wi-Fi: laptop yes, phone no:
@mrkaban said in Wi-Fi: laptop yes, phone no:
There is nothing in the firewall log from the WLAN interface (wireless network).
When my Android Smartphone connects I see this in wireless log:
Apr 2 15:24:00 hostapd 35016 ath0_wlan0: STA 00:27:15:3d:db:a7 IEEE 802.1X: unauthorizing port Apr 2 15:24:00 hostapd 35016 ath0_wlan0: STA 00:27:15:3d:db:a7 WPA: event 2 notification Apr 2 15:24:00 hostapd 35016 ath0_wlan0: STA 00:27:15:3d:db:a7 IEEE 802.11: disassociated Apr 2 15:23:46 hostapd 35016 ath0_wlan0: STA 00:27:15:3d:db:a7 WPA: pairwise key handshake completed (RSN) Apr 2 15:23:46 hostapd 35016 ath0_wlan0: STA 00:27:15:3d:db:a7 RADIUS: starting accounting session 665BCC0E11586A5E Apr 2 15:23:46 hostapd 35016 ath0_wlan0: STA 00:27:15:3d:db:a7 IEEE 802.1X: authorizing port Apr 2 15:23:46 hostapd 35016 ath0_wlan0: STA 00:27:15:3d:db:a7 WPA: received EAPOL-Key frame (4/4 Pairwise) Apr 2 15:23:46 hostapd 35016 ath0_wlan0: STA 00:27:15:3d:db:a7 WPA: sending 3/4 msg of 4-Way Handshake Apr 2 15:23:46 hostapd 35016 ath0_wlan0: STA 00:27:15:3d:db:a7 WPA: received EAPOL-Key frame (2/4 Pairwise) Apr 2 15:23:46 hostapd 35016 ath0_wlan0: STA 00:27:15:3d:db:a7 WPA: sending 1/4 msg of 4-Way Handshake Apr 2 15:23:46 hostapd 35016 ath0_wlan0: STA 00:27:15:3d:db:a7 IEEE 802.1X: unauthorizing port Apr 2 15:23:46 hostapd 35016 ath0_wlan0: STA 00:27:15:3d:db:a7 WPA: start authentication Apr 2 15:23:46 hostapd 35016 ath0_wlan0: STA 00:27:15:3d:db:a7 WPA: event 1 notification Apr 2 15:23:46 hostapd 35016 ath0_wlan0: STA 00:27:15:3d:db:a7 IEEE 802.11: associated(MAC Adress is edited)
and where exactly do you see these statistics? Status \ System Logs \ System \ Wireless connection
-
@mrkaban said in Wi-Fi: laptop yes, phone no:
and where exactly do you see these statistics? Status \ System Logs \ System \ Wireless connection
Exact there! (Highlighted)
-
Yes I see the same.
You should also see it in Status > Wireless -
@stephenw10 said in Wi-Fi: laptop yes, phone no:
Yes I see the same.
You should also see it in Status > WirelessIt took me a moment to realize that the most recent ones were from below. Here's what appears after trying to connect from your phone:
not in the form of a picture, antispam does not allow you to write
-
@mrkaban said in Wi-Fi: laptop yes, phone no:
Here's what appears after trying to connect from your phone:
I see there:
EAPOL-Key timeoutand I interprete that like the Authentication is not coming from your device - is that smartphone logging in correctly in a other access point?
-
Also I assume if you login from the laptop the logs look the same as we see?
-
@stephenw10 said in Wi-Fi: laptop yes, phone no:
Also I assume if you login from the laptop the logs look the same as we see?
It connects to all other Wi-fi points from the phone without problems.
This is what I see when I connect from my laptop:
-
Possible the phone is restricted to WPA3 only? Other APs you tested against are WPA2?
-
@stephenw10 said in Wi-Fi: laptop yes, phone no:
Possible the phone is restricted to WPA3 only? Other APs you tested against are WPA2?
Currently connected to a wireless network with WPA2-PSK
-
@fireodo said in Wi-Fi: laptop yes, phone no:
rtl8192ce
What driver is that using? rtwn(4)? Is that USB or PCI connected?
What does
sysctl dev.rtwn.0.hwcryptoshow? -
@stephenw10 said in Wi-Fi: laptop yes, phone no:
sysctl dev.rtwn.0.hwcrypto
If you run "Diagnostics \ Command Prompt" here, then the output:
dev.rtwn.0.hwcrypto: 1
-
Hmm, well I don't think that hardware crypto applies to WPA2 but try disabling that with:
sysctl dev.rtwn.0.hwcrypto=0Unclear if that applies immediately.
-
@stephenw10 said in Wi-Fi: laptop yes, phone no:
Hmm, well I don't think that hardware crypto applies to WPA2 but try disabling that with:
sysctl dev.rtwn.0.hwcrypto=0Unclear if that applies immediately.
Completed, the output was:
sysctl: oid 'dev.rtwn.0.hwcrypto' is a read only tunable
sysctl: Tunable values are set in /boot/loader.confOf course I rebooted and tried. And only after the failure did I read what exactly he was writing.
-
Yup run:
echo dev.rtwn.0.hwcrypto=0 >> /boot/loader.conf.localThen reboot.
-
@stephenw10 said in Wi-Fi: laptop yes, phone no:
Yup run:
echo dev.rtwn.0.hwcrypto=0 >> /boot/loader.conf.localThen reboot.
As before, it does not pass authentication. He says that the password is incorrect, but it is definitely correct.
-
Running
sysctl dev.rtwn.0.hwcryptoshows it's correctly disabled?Hmm, I didn't really expect that make any difference in WPA2 unless it had a broken AES/TKIP implementation perhaps.
Do you have an older Android you could test with? I'm not aware of any particular issue with Android 14 but I don't have a device to test with right now.
-
@stephenw10 said in Wi-Fi: laptop yes, phone no:
Running
sysctl dev.rtwn.0.hwcryptoshows it's correctly disabled?Hmm, I didn't really expect that make any difference in WPA2 unless it had a broken AES/TKIP implementation perhaps.
Do you have an older Android you could test with? I'm not aware of any particular issue with Android 14 but I don't have a device to test with right now.
I don't have it on my hands, but I'll try to find it and check it out.
-
@stephenw10 said in Wi-Fi: laptop yes, phone no:
Running
sysctl dev.rtwn.0.hwcryptoshows it's correctly disabled?Hmm, I didn't really expect that make any difference in WPA2 unless it had a broken AES/TKIP implementation perhaps.
Do you have an older Android you could test with? I'm not aware of any particular issue with Android 14 but I don't have a device to test with right now.
You're right, it connects to android 4 phones without any problems. There are problems with Android 13 and 14 from different manufacturers. What can I try to do?
