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=0

Unclear 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.conf

Of course I rebooted and tried. And only after the failure did I read what exactly he was writing.

stephenw10

Yup run: echo dev.rtwn.0.hwcrypto=0 >> /boot/loader.conf.local

Then reboot.

mrkaban

@stephenw10 said in Wi-Fi: laptop yes, phone no:

Yup run: echo dev.rtwn.0.hwcrypto=0 >> /boot/loader.conf.local

Then reboot.

As before, it does not pass authentication. He says that the password is incorrect, but it is definitely correct.

stephenw10

Running sysctl dev.rtwn.0.hwcrypto shows 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.

mrkaban

@stephenw10 said in Wi-Fi: laptop yes, phone no:

Running sysctl dev.rtwn.0.hwcrypto shows 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.

mrkaban

@stephenw10 said in Wi-Fi: laptop yes, phone no:

Running sysctl dev.rtwn.0.hwcrypto shows 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?

stephenw10

Hmm, well that seem like a clue. Perhaps some deprecated cypher is preventing it? I'm not sure how you might change that though. Can you test with anything else? An iOS device perhaps?

mrkaban

@stephenw10 said in Wi-Fi: laptop yes, phone no:

Hmm, well that seem like a clue. Perhaps some deprecated cypher is preventing it? I'm not sure how you might change that though. Can you test with anything else? An iOS device perhaps?

To be honest, it was difficult to get a phone with android 4. I can check on another laptop. iOS probably won't be available.

stephenw10

Did you try setting 'WPA Pairwise' to TKIP or both instead of AES?

mrkaban

@stephenw10 said in Wi-Fi: laptop yes, phone no:

Did you try setting 'WPA Pairwise' to TKIP or both instead of AES?

Yes... It didn't help...

mrkaban

Thanks friends for trying to help! As a result, I spat and installed another distribution that is not a fork of pfSense and wi-fi works perfectly on all devices. This means that the problem was not with the device, but with pfSense or freebsd itself. It is a pity that it was not possible to make friends with pfsense wi-fi.

stephenw10

The confirms it's a not a hardware issue at least. Which makes sense since the WPA auth should all be in software.