[9.260][SOLVED] Wireless problem

Hi,

I have a Ap50 on my HomeUTM, it runs a 2,4GHz only net, because I have some SqueezeBox Boom media players attached.

After the Beta upgrade, none of them can connect, only iPhone and laptops can.

I see this in the logs:

2014:10:03-10:05:45 192.168.110.73 awelogger[1412]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="OUR-WIFI" ssid_id="WLAN2.0" bssid="00:1a:8c:0b:86[:D]0" sta="00:04:20:1f:16:34" status_code="0"
2014:10:03-10:05:45 192.168.110.73 awelogger[1412]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="OUR-WIFI" ssid_id="WLAN2.0" bssid="00:1a:8c:0b:86[:D]0" sta="00:04:20:1f:16:34" status_code="0"
2014:10:03-10:05:47 192.168.110.73 awelogger[1412]: id="4105" severity="info" sys="System" sub="WiFi" name="STA WPA failure" ssid="OUR-WIFI" ssid_id="WLAN2.0" bssid="00:1a:8c:0b:86[:D]0" sta="00:04:20:1e:8f:31" reason_code="2"
2014:10:03-10:05:47 192.168.110.73 awelogger[1412]: id="4105" severity="info" sys="System" sub="WiFi" name="STA WPA failure" ssid="OUR-WIFI" ssid_id="WLAN2.0" bssid="00:1a:8c:0b:86[:D]0" sta="00:04:20:1e[:D]9:9c" reason_code="2"
2014:10:03-10:05:49 192.168.110.73 awelogger[1412]: id="4105" severity="info" sys="System" sub="WiFi" name="STA WPA failure" ssid="OUR-WIFI" ssid_id="WLAN2.0" bssid="00:1a:8c:0b:86[:D]0" sta="00:04:20:1f:16:34" reason_code="2"
2014:10:03-10:05:52 192.168.110.73 hostapd: wlan0: STA 00:04:20:1e:8f:31 IEEE 802.11: deauthenticated due to local deauth request
2014:10:03-10:05:52 192.168.110.73 hostapd: wlan0: STA 00:04:20:1e[:D]9:9c IEEE 802.11: deauthenticated due to local deauth request
2014:10:03-10:05:53 192.168.110.73 hostapd: wlan0: STA 00:04:20:1f:16:34 IEEE 802.11: deauthenticated due to local deauth request
2014:10:03-10:05:54 192.168.110.73 hostapd: wlan0: STA 00:04:20:1e:8f:31 IEEE 802.11: authenticated
2014:10:03-10:05:54 192.168.110.73 awelogger[1412]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="OUR-WIFI" ssid_id="WLAN2.0" bssid="00:1a:8c:0b:86[:D]0" sta="00:04:20:1e:8f:31" status_code="0"
2014:10:03-10:05:54 192.168.110.73 hostapd: wlan0: STA 00:04:20:1e:8f:31 IEEE 802.11: associated (aid 1)
2014:10:03-10:05:54 192.168.110.73 hostapd: wlan0: STA 00:04:20:1e[:D]9:9c IEEE 802.11: authenticated
2014:10:03-10:05:54 192.168.110.73 awelogger[1412]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="OUR-WIFI" ssid_id="WLAN2.0" bssid="00:1a:8c:0b:86[:D]0" sta="00:04:20:1e:8f:31" status_code="0"
2014:10:03-10:05:54 192.168.110.73 awelogger[1412]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="OUR-WIFI" ssid_id="WLAN2.0" bssid="00:1a:8c:0b:86[:D]0" sta="00:04:20:1e[:D]9:9c" status_code="0"
2014:10:03-10:05:54 192.168.110.73 hostapd: wlan0: STA 00:04:20:1e[:D]9:9c IEEE 802.11: associated (aid 2)
2014:10:03-10:05:54 192.168.110.73 awelogger[1412]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="OUR-WIFI" ssid_id="WLAN2.0" bssid="00:1a:8c:0b:86[:D]0" sta="00:04:20:1e[:D]9:9c" status_code="0"
2014:10:03-10:05:55 192.168.110.73 hostapd: wlan0: STA 00:04:20:1f:16:34 IEEE 802.11: authenticated
2014:10:03-10:05:56 192.168.110.73 awelogger[1412]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="OUR-WIFI" ssid_id="WLAN2.0" bssid="00:1a:8c:0b:86[:D]0" sta="00:04:20:1f:16:34" status_code="0"
2014:10:03-10:05:56 192.168.110.73 hostapd: wlan0: STA 00:04:20:1f:16:34 IEEE 802.11: associated (aid 3)
2014:10:03-10:05:56 192.168.110.73 awelogger[1412]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="OUR-WIFI" ssid_id="WLAN2.0" bssid="00:1a:8c:0b:86[:D]0" sta="00:04:20:1f:16:34" status_code="0"
2014:10:03-10:05:57 192.168.110.73 awelogger[1412]: id="4105" severity="info" sys="System" sub="WiFi" name="STA WPA failure" ssid="OUR-WIFI" ssid_id="WLAN2.0" bssid="00:1a:8c:0b:86[:D]0" sta="00:04:20:1e:8f:31" reason_code="2"
2014:10:03-10:05:57 192.168.110.73 awelogger[1412]: id="4105" severity="info" sys="System" sub="WiFi" name="STA WPA failure" ssid="OUR-WIFI" ssid_id="WLAN2.0" bssid="00:1a:8c:0b:86[:D]0" sta="00:04:20:1e[:D]9:9c" reason_code="2"
2014:10:03-10:05:59 192.168.110.73 awelogger[1412]: id="4105" severity="info" sys="System" sub="WiFi" name="STA WPA failure" ssid="OUR-WIFI" ssid_id="WLAN2.0" bssid="00:1a:8c:0b:86[:D]0" sta="00:04:20:1f:16:34" reason_code="2"
2014:10:03-10:06:02 192.168.110.73 hostapd: wlan0: STA 00:04:20:1e:8f:31 IEEE 802.11: deauthenticated due to local deauth request
2014:10:03-10:06:02 192.168.110.73 hostapd: wlan0: STA 00:04:20:1e[:D]9:9c IEEE 802.11: deauthenticated due to local deauth request
2014:10:03-10:06:04 192.168.110.73 hostapd: wlan0: STA 00:04:20:1f:16:34 IEEE 802.11: deauthenticated due to local deauth request
2014:10:03-10:06:04 192.168.110.73 hostapd: wlan0: STA 00:04:20:1e:8f:31 IEEE 802.11: authenticated
2014:10:03-10:06:04 192.168.110.73 hostapd: wlan0: STA 00:04:20:1e:8f:31 IEEE 802.11: associated (aid 1)

I used a WLAn scanner, and the 5Ghz is not being broadcasted, so thats okay.

Authentication is still the same.

Other than the ACS, what is else changed??

0 twister5800 over 10 years ago

UPDATE:

Tried to create a new WLAN (SSID), still same problem.

I have now changed the encryption from WPA2-PSK (AES) to WPA-PSK (AES), and that seems to work.

I have used WPA2-PSK (AES) several years with theese devices, have you changed something in the handshake?

If I revert to 9.207-18, everything works again [:S]

-----

Best regards
Martin

Sophos XGS 2100 @ Home | Sophos v19 Architect
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 twister5800 over 10 years ago

New issue:

This is also different, I also have a Chromecast, it works, but the signal strength for this device only, is diplayed at 0%.

This is also new...

-----

Best regards
Martin

Sophos XGS 2100 @ Home | Sophos v19 Architect
- Udklip.JPG
- View
- Hide
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 twister5800 over 10 years ago

Another update:

Got a D-LINK DCS-932L webcam, it also has the problem with not connection, when WPA2-PSK is used, changing to WPA-PSK makes it work again.

-----

Best regards
Martin

Sophos XGS 2100 @ Home | Sophos v19 Architect
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 RFCat_vk_01 over 10 years ago in reply to twister5800

HI,
I have found that devices with existing connections can connect, but new devices cannot connect. Password is wrong. Even though the security type is mixed.

Devices that had existing connections and can connect are
mac book pro
mac mini
android tablet
Sony android phone.

Ian
(using up2date upgrade)
I would provide logs if I could get into the logs.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 twister5800 over 10 years ago in reply to RFCat_vk_01

HI,
I have found that devices with existing connections can connect, but new devices cannot connect. Password is wrong. Even though the security type is mixed.

In my setup can phones and laptops connect, but media players (Logitech) ,and webcams (D-link) cannot.

Changing to mixed mode helps nothing, but setting the problematic devices with WPA-PSK instead of WPA2-PSK, makes them work again.

I have switched back to 9.207-18 in the weekend, and all devies reconnected successfully again and I avoided a divorce [[:D]]

(Still testing 9.3 today [[:D]] )

-----

Best regards
Martin

Sophos XGS 2100 @ Home | Sophos v19 Architect
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 reinerh over 10 years ago

After trying a workaround with Twister5800, we found out that disabling IEEE 802.11r solved his connection problems.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 twister5800 over 10 years ago in reply to reinerh

After trying a workaround with Twister5800, we found out that disabling IEEE 802.11r solved his connection problems.

Reinerh: Do you plan to make it an on/off switch in the next release?

-----

Best regards
Martin

Sophos XGS 2100 @ Home | Sophos v19 Architect
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 reinerh over 10 years ago in reply to twister5800

Reinerh: Do you plan to make it and on/off switch in the next release?

Yes, we do. [:)]
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 twister5800 over 10 years ago in reply to reinerh

Yes, we do. [:)]

GREAT, thanks! [:D]

-----

Best regards
Martin

Sophos XGS 2100 @ Home | Sophos v19 Architect
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Sascha Paris over 10 years ago in reply to twister5800

I had after 9.260 update similar issue with only one laptop with old AGN5100 WIFI Chipset. Had to revert SSID from WPA2 to WPA2/WPA to get it back to work. All other device had no issues to connect to WPA2 only.

Before 9.3 beta all devices worked with WPA2.

As the AGN5100 latest driver is rom 2011, I assume it to be a driver issue handling the new 802.11r feature in UTM Wifi.

Fascinating...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel