E400 problem with Raspberry Pi client

cad · August 23, 2017, 9:12pm

Hello together,

since a few days I try to connect a Raspberry Pi with an RTL 8191SU chipset WLAN-Adapter to my WLAN with E400 accesspoints. The Pi runs a Linux system "Raspbian Jessie".

It seems to connect but then gets immediately disconncted.

A connection to a Zyxel Accesspoint with the same configuration works without problems. I upgraded the E400 to firmware version 3.4.3-r9, but the problem still remains. I've changed the channel width to 20 MHz and Multicast Data rate to "Highest supported", but no success.

Here is what I find in the log:

Aug 23 21:13:30: wifid : Client[00-87-24-93-FA-74] on ssid Abbey internal cache based vlan is 0 (apd.c:82)
Aug 23 21:13:30: wifid : client [00-87-24-93-FA-74] on ssid Abbey vlan 1 state sync (type:1) sent, len[128] (cache.c:1253)
Aug 23 21:13:30: scmd : Dropping message to autopilot master, registration not completed (connect.c:604)
Aug 23 21:13:30: scmd : Event write failed (pid:494). error 2:No such file or directory (main.c:1070)
Aug 23 21:13:30: scmd : Aug 23 21:13:30 WIFI-6-CLIENT-CONNECTED Client [00-87-24-93-FA-74] connected to wireless lan [Abbey] (main.c:1
Aug 23 21:13:30: wifid : client[00-87-24-93-FA-74] on vap_id[0] wlan_id[0] created in coplane (stats.c:217)
Aug 23 21:13:30: wifid : client[00-87-24-93-FA-74] current ssid[0][Abbey] and it's cache ssid[Abbey] (cache.c:1838)
Aug 23 21:13:30: wifid : client[00-87-24-93-FA-74] no hotspot session found (hotspot.c:821)
Aug 23 21:13:30: wifid : Client[00-87-24-93-FA-74] on ssid Abbey internal cache based vlan is 0 (apd.c:82)
Aug 23 21:13:30: wifid : Failed to get stats for client[00-87-24-93-FA-74] on wlan 1 (wifi_stats.c:36)
Aug 23 21:13:30: wifid : IEEE80211_IOCTL_STA_STATS failed (stats.c:265)
Aug 23 21:13:30: wifid : client [00-87-24-93-FA-74] on ssid Abbey vlan 1 state sync (type:1) sent, len[128] (cache.c:1253)
Aug 23 21:13:30: wifid : client[00-87-24-93-FA-74] on vap_id[0] wlan_id[0] created in coplane (stats.c:217)
Aug 23 21:13:30: wifid : client[00-87-24-93-FA-74] current ssid[0][Abbey] and it's cache ssid[Abbey] (cache.c:1838)
Aug 23 21:13:30: wifid : client[00-87-24-93-FA-74] no hotspot session found (hotspot.c:821)
Aug 23 21:13:30: scmd : Dropping message to autopilot master, registration not completed (connect.c:604)
Aug 23 21:13:30: scmd : Event write failed (pid:494). error 2:No such file or directory (main.c:1070)
Aug 23 21:13:30: scmd : Aug 23 21:13:30 WIFI-6-CLIENT-DISCONNECTED Client [00-87-24-93-FA-74] disconnected from WLAN [Abbey], after [0
Aug 23 21:13:30: wifid : client[00-87-24-93-FA-74] on vap_id[0] wlan_id[0] deleted in coplane (stats.c:217)
Aug 23 21:13:36: scmd : State timer callback. autopilot state = 0 (connect.c:659)

So I'd like to ask for help here...

Thanks and regards

Conny

firefly · August 23, 2017, 9:16pm

Is this an open SSID or with security enabled?

does 'show events' in the CLI (or the correponding page on the GUI for events) show a reason for the client disconnection?

cad · August 23, 2017, 11:51pm

Thanks for the reply! There is no reason for the disconnect shown in the GUI-page. It simply says "Client [00-87-24-93-FA-74] disconnected from WLAN [Abbey], after [0] secs and used txbytes [0] rxbytes [0]".

This is a wpa2-psk secured WLAN with SSID "Abbey".

Regards Conny

ireddy · August 24, 2017, 5:19am

hi please share ap techdump to channareddy.ireddy@cambiumnetworks.com. we will look into this one. in the mean time can we downgrade ap to 3.3-r16 and check the connetivity status.

ireddy · August 24, 2017, 5:28am

before downgrading to 3.3-r16 image, can we configure ssid with open autehntication and check client is abel to associate and able do data transfer with ap.

cad · August 24, 2017, 10:10am

Hi, thanks for your replies. I initially had firmware 3.1-r20 installed when I encountered this problem.

Then I upgraded to 3.4.3-r9, but the problem still remained. Does ist make sense to downgrade to 3.1-r16?

I made a test now with open authentication and everything worked fine. Switching back to WPA2-PSK the problem reappeared.

How can I create a techdump? (I found this option in the "Autopilot"-menues but I do not have the autopilot activated.) Can I create that dump with the classic GUI? Or with the CLI?

Anything else I could do?

Regards Conny

CAM_TSK · August 24, 2017, 10:33am

Procedure to download tech-support:

Login to device GUI
Navigate to Operations
Click on "Download Tech-support"

Once downloaded, please email tech-support and client MAC at shashank.tadakamadla@cambiumnetworks.com

Thank You.

cad · August 24, 2017, 3:28pm

Thanks - I've mailed it to that address!

Best regards, Conny

newkirk · August 24, 2017, 6:11pm

@cad wrote:
Hello together,

since a few days I try to connect a Raspberry Pi with an RTL 8191SU chipset WLAN-Adapter to my WLAN with E400 accesspoints. The Pi runs a Linux system "Raspbian Jessie".

It seems to connect but then gets immediately disconncted.

A connection to a Zyxel Accesspoint with the same configuration works without problems. I upgraded the E400 to firmware version 3.4.3-r9, but the problem still remains. I've changed the channel width to 20 MHz and Multicast Data rate to "Highest supported", but no success.

...

Thanks and regards

Conny

What about the log on the Pi itself? try "grep wpa_supplicant /var/log/syslog" and see what it tells you.

I'm assuming this is a USB wifi adapter? (RasPis with onboard WiFi are Broadcom chips) How was the wifi set up - using the GUI or via console editing /etc/wpa_supplicant/wpa_supplicant.conf and /etc/network/interfaces?

I have several Pis with RTL8189 chipset (plus a couple with BCM onboard wifi), the following wpa_supplicant.conf works for them to connect to my E400 APs:

network={
ssid="newkirk"
psk="super-secret passphrase"
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
auth_alg=OPEN
}

The wpa_supplicant.conf file should have something similar whether configured manually or via GUI.

j

cad · August 25, 2017, 6:17pm

Hi and thanks for the reply. Yes - this is an USB Wifi Asapter.

My wpla_supplicant.conf is:

country=DE
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
network={
        ssid="Abbey"
        scan_ssid=1
        proto=RSN
        key_mgmt=WPA-PSK
        pairwise=CCMP
        group=CCMP
        psk=encryptedPSK
}

I tried an adaptation of your wpa_supplicant.conf but it didn't work, too.

I do not know if the raspi has a problem with the CCMP cipher, but the logfile in the E400 doesn't show something like that.

Here are my results of the syslog:

Aug 25 16:39:45 raspberrypi wpa_supplicant[378]: Successfully initialized wpa_supplicant
Aug 25 16:39:45 raspberrypi wpa_supplicant[378]: nl80211: Driver does not support authentication/association or connect commands
Aug 25 16:39:55 raspberrypi wpa_supplicant[402]: wlan0: Trying to associate with 00:04:56:ab:9c:xx (SSID='Abbey' freq=2432 MHz)
Aug 25 16:39:55 raspberrypi wpa_supplicant[402]: wlan0: Association request to the driver failed
Aug 25 16:40:00 raspberrypi wpa_supplicant[402]: wlan0: Authentication with 00:04:56:ab:9c:xx timed out.
Aug 25 16:40:00 raspberrypi wpa_supplicant[402]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:04:56:ab:9c:xx reason=3 locally_generated=1
#then it tries to connect to a second E400 nearby:
Aug 25 16:40:10 raspberrypi wpa_supplicant[402]: wlan0: Trying to associate with 00:04:56:ab:80:yy (SSID=‘Abbey’ freq=2437 MHz)

Aug 25 16:40:10 raspberrypi wpa_supplicant[402]: wlan0: Association request to the driver failed

Aug 25 16:40:15 raspberrypi wpa_supplicant[402]: wlan0: Authentication with 00:04:56:ab:80:yy timed out.
#…and so on…

To compare - the following is a successful connect to a Zyxel accesspoint (using TKIP):

Aug 25 14:21:29 raspberrypi wpa_supplicant[379]: Successfully initialized wpa_supplicant

Aug 25 14:21:30 raspberrypi wpa_supplicant[379]: nl80211: Driver does not support authentication/association or connect commands

Aug 25 14:21:40 raspberrypi wpa_supplicant[446]: wlan0: Trying to associate with 60:31:97:84:c7:zz (SSID=‘GuestHouse’ freq=2412 MHz)

Aug 25 14:21:40 raspberrypi wpa_supplicant[446]: wlan0: Association request to the driver failed

Aug 25 14:21:42 raspberrypi wpa_supplicant[446]: wlan0: Associated with 60:31:97:84:c7:zz

Aug 25 14:21:42 raspberrypi wpa_supplicant[446]: wlan0: WPA: Key negotiation completed with 60:31:97:84:c7:zz [PTK=TKIP GTK=TKIP]

Aug 25 14:21:42 raspberrypi wpa_supplicant[446]: wlan0: CTRL-EVENT-CONNECTED - Connection to 60:31:97:84:c7:zz completed [id=0 id_str=]

Aug 25 16:30:03 raspberrypi wpa_supplicant[446]: wlan0: WPA: Group rekeying completed with 60:31:97:84:c7:zz [GTK=TKIP]

I use a lite version of Jessie without GUI

Thanks for helping and regards

Conny

CAM_TSK · August 26, 2017, 4:02am

Based on logs with other AP

wlan0: WPA: Key negotiation completed with 60:31:97:84:c7:zz [PTK=TKIP GTK=TKIP]"

it seems TKIP is negotiated.

Could you please try the following configuration in wpa_supplicant:

network={
ssid="<SSID-NAME>"

scan_ssid = 1

    proto=RSN
    key_mgmt=WPA-PSK
    pairwise=CCMP TKIP
    group=CCMP TKIP
    psk="<passowrd>"
}

cad · August 26, 2017, 8:55am

Thanks for the reply. I tested it, but no change. I had tested several configurations before and nothing worked. The problem here is that TKIP is not propagated by the E400, see the AP scan:

          Cell 05 - Address: 00:04:56:AB:9C:xx
                    ESSID:"Abbey"
                    Protocol:IEEE 802.11bgn
                    Mode:Master
                    Frequency:2.432 GHz (Channel 5)
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 12 Mb/s
                              18 Mb/s; 24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Extra:rsn_ie=xxxxxxxx [edited]
                    IE: IEEE 802.11i/WPA2 Version 1
                    Group Cipher : CCMP
                    Pairwise Ciphers (1) : CCMP
                    Authentication Suites (2) : PSK unknown (4)
                    Signal level=100/100

It seems that the E400 simply stops answering during authentication.

I can rembember that sometimes ago I had a mobile phone which also could not connect to the E400. Maybe it was the same problem.

Regards Conny

CAM_TSK · August 27, 2017, 10:54am

Please enable TKIP from Command Line Interface [CLI] of device:

E400-AP(config)# wireless wlan <ID>
E400-AP(config-wlan-<ID>)# allow-tkip
E400-AP(config-wlan-<ID>)# save

Thank You.

cad · September 2, 2017, 7:00pm

Thanks for the reply. I was a few days away from my desk - so sorry for not answering so long.

I activated TKIP but that didn't help. I tried several configurations.

The E400 simply stops answering during authentication.

So this problem seems not to be TKIP-related.

@CAM_TSK - were you able to take a look at the techdump?

Thanks and regards

Conny

cad · September 3, 2017, 1:12pm

I played a little bit around with this and I think the problem lies anywhere around the "no hotspot session found" entry:

Sep 03 14:40:29: scmd : Sep 3 14:40:29 WIFI-6-CLIENT-CONNECTED Client [00-87-24-93-FA-xx] connected to wireless lan [Abbey-Tec] (main
Sep 03 14:40:29: wifid : Client[00-87-24-93-FA-xx] on ssid Abbey-Tec internal cache based vlan is 0 (apd.c:82)
Sep 03 14:40:29: wifid : Failed to get stats for client[00-87-24-93-FA-xx] on wlan 2 (wifi_stats.c:36)
Sep 03 14:40:29: wifid : IEEE80211_IOCTL_STA_STATS failed (stats.c:265)
Sep 03 14:40:29: wifid : client [00-87-24-93-FA-xx] on ssid Abbey-Tec vlan 1 state sync (type:1) sent, len[128] (cache.c:1253)
Sep 03 14:40:29: wifid : client[00-87-24-93-FA-xx] on vap_id[1] wlan_id[1] created in coplane (stats.c:217)
Sep 03 14:40:29: wifid : client[00-87-24-93-FA-xx] current ssid[1][Abbey-Tec] and it's cache ssid[Abbey-Tec] (cache.c:1838)
Sep 03 14:40:29: wifid : client[00-87-24-93-FA-xx] no hotspot session found (hotspot.c:821)
Sep 03 14:40:29: wifid : client[00-87-24-93-FA-xx] on vap_id[1] wlan_id[1] deleted in coplane (stats.c:217)
Sep 03 14:40:44: wifid : Client[00-87-24-93-FA-xx] on ssid Abbey-Tec internal cache based vlan is 0 (apd.c:82)
Sep 03 14:40:44: wifid : client [00-87-24-93-FA-xx] on ssid Abbey-Tec vlan 1 state sync (type:1) sent, len[128] (cache.c:1253)

Maybe this helps anyway?

Regards, Conny