0

I made a configuration with this config : 2 WLAN, 2 SSID, Dongle + integrated wifi on Raspberry PI 3B+

Everything is working except, not everybody cannot connect to the wifi. Samsung Smartphone cannot connect to this and some Windows 10 too. What can be the problem. Any idea? This is my WPA_SUPPLICANT CONFIG: network={ mode=2 ssid="Work" psk="Password01" frequency=2412 proto=RSN key_mgmt=WPA-PSK pairwise=CCMP group=CCMP auth_alg=OPEN }.

The SSID work and it is visible. Nothing appear, is like a loop, the user click on the SSID WORK and the device said, connecting... after a while the connection process stop and again connecting. For Windows 10. It says, Unable to connect to this network.

Ingo
  • 42,961
  • 20
  • 87
  • 207
Pi3.14
  • 47
  • 6

2 Answers2

1

I use this /etc/wpa_supplicant/wpa_supplicant.conf:

country=DE
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
    ssid="RPiNet"
    mode=2
    key_mgmt=WPA-PSK
    psk="verySecretPassword"
    frequency=2412   # channel 1
}

and my Samsung smartphone connects to the RasPi without any problems. You have to configure the Samsung WiFi using the "verySecretPassword" and to use DHCP. Do you configure it? I have also seen that sometimes a 4 character password was to short. You should use at least 8 character.

You can try to delete the line key_mgmt=WPA-PSK in the hope that wpa_supplicant will then use the right encryption. By default WPA2 (resp. RSN) is used instead of older WPA. With a line proto=RSN WPA you can define that WPA should be used if RSN isn't accepted.

Ingo
  • 42,961
  • 20
  • 87
  • 207
0

This could be a false positive, but the symptoms (unspecific as they are) match up with the answer I provided here.

In short, it seems some clients fail to connect unless you disable WPA2 with proto=wpa, or wpa_supplicant is replaced with something that provides an WPA2 Authenticator like hostapd.

Heath Raftery
  • 275
  • 1
  • 9