[Solved] WiFi Windows clients can't connect

Started by DrWily, September 24, 2019, 10:29:31 PM

Previous topic - Next topic
September 24, 2019, 10:29:31 PM Last Edit: September 25, 2019, 09:39:51 PM by DrWily
Hello!

Tried searching but found nothing similar.

I have a very strange problem, when I try to connect windows computers to the Ubiquiti AP connected to the APU2 OPNSense router, they can't connect. They can see the AP and try to connect but they just hang.

Ipad, Androids and Linux laptops are working, even one of the windows laptops can connect to the wifi when booting Linux on it.

I'cant seem to find any information in the OPNSense logs and I'm not a windows user so I had a hard time finding data in the Windows logs.
Has anyone else encountered anything similar?? I would greatly appreciate some hints, thinking about installing pfSense and trying if it works but would rather use OPNSense. (Everything worked fine when using the Ubiquiti AP connected to an ASUS Router)

I had a DHCP problem a few weeks ago that sounds a bit like what you're describing.  I use opnsense's DHCP service exclusively.  As lame as this sounds, I think that rebooting multiple times is what cleared it up. 

If you're allowing Ubiquity to serve the DHCP, I don't know how to diagnose.  If you're using opnsense DHCP:  In the Windows machines networking config, make sure that they're receiving an ip from the DHCP.  If they're not, either a rule (or lack of) is preventing DHCP access, or the DHCP service is acting up.  If there's anything else possible, that's beyond my feeble efforts.

Best wishes!  Let us know how it goes.

Thanks for the quick reply!

I managed to find the problem but it took a while.

WPA2 passwords can only use 7bit ASCII letters, since I used a swedish åäö character everything failed (When using windows). The question is why Linux and IOS worked... Perhaps the hashing algorithm is different or something..

Well the answer to my problem is there in case someone else stumbles upon the same error.

As far as I know Linux based systems are using a different default encoding in some cases which very likely fits the character encoding in use.

Good to know, thanks for posting the solution!
Twitter: banym
Mastodon: banym@bsd.network
Blog: https://www.banym.de