wpa_supplicant not detecting loss of an association with AP

Reinholds@comcast.net reinholds at comcast.net
Fri May 27 20:35:52 PDT 2016


Hi,
I am attempting to address a problem in which the wpa_supplicant does not
appear to detect the loss of association with an access point. The problem
is intermittent and does not happen consistently. However, when it does
happen the system on which wpa_supplicant is running does not recover and
manual intervention is necessary. Manual intervention involves disconnecting
wpa_supplicant from the AP, and then reconnecting to the AP.
In debugging the problem we looked at the state of the wifi connection by
using iwconfig which indicates that the wlan0 interface is not-associated.
This is consistent with the output from the ip link command which also
indicates that the wlan0 is "DOWN".
However, if we use D-feet to examine the properties of
fi.w1.wpa_supplicant1.Interface we find that it believes that it is
associated with the wifi AP. Further, there are no indications in the
journalctl log file suggest that wpa_supplicant is seeing the disconnection
and trying to reestablish it.

I am looking for suggestions as to how to further identify what is causing
the problem, and suggestions for work arounds that will allow the Raspberry
PI-3 to remain online.

The testing is being done using wpasupplicant 2.3, on a Raspberry PI-3
running Raspian version 8 (Jessie) and Linux kernel 4.4.10-v7+

A segment of the journalctl output, starting at the detection of the lost
carrier is below:

May 27 10:05:58 raspberrypi systemd-networkd[1032]: wlan0           : lost
carrier
May 27 10:05:58 raspberrypi systemd-networkd[1032]: wlan0           : DHCP
lease lost
May 27 10:05:58 raspberrypi avahi-daemon[402]: Withdrawing address record
for 192.168.0.106 on wlan0.
May 27 10:05:58 raspberrypi avahi-daemon[402]: Leaving mDNS multicast group
on interface wlan0.IPv4 with address 192.168.0.106.
May 27 10:05:58 raspberrypi avahi-daemon[402]: Interface wlan0.IPv4 no
longer relevant for mDNS.
May 27 10:05:58 raspberrypi wpa_supplicant[807]: wlan0:
CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May 27 10:05:58 raspberrypi kernel: brcmfmac: brcmf_cfg80211_reg_notifier:
not a ISO3166 code
May 27 10:05:58 raspberrypi kernel: cfg80211: World regulatory domain
updated:
May 27 10:05:58 raspberrypi kernel: cfg80211:  DFS Master region: unset
May 27 10:05:58 raspberrypi kernel: cfg80211:   (start_freq - end_freq @
bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
May 27 10:05:58 raspberrypi kernel: cfg80211:   (2402000 KHz - 2472000 KHz @
40000 KHz), (N/A, 2000 mBm), (N/A)
May 27 10:05:58 raspberrypi kernel: cfg80211:   (2457000 KHz - 2482000 KHz @
40000 KHz), (N/A, 2000 mBm), (N/A)
May 27 10:05:58 raspberrypi kernel: cfg80211:   (2474000 KHz - 2494000 KHz @
20000 KHz), (N/A, 2000 mBm), (N/A)
May 27 10:05:58 raspberrypi kernel: cfg80211:   (5170000 KHz - 5250000 KHz @
80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
May 27 10:05:58 raspberrypi kernel: cfg80211:   (5250000 KHz - 5330000 KHz @
80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
May 27 10:05:58 raspberrypi kernel: cfg80211:   (5490000 KHz - 5730000 KHz @
160000 KHz), (N/A, 2000 mBm), (0 s)
May 27 10:05:58 raspberrypi kernel: cfg80211:   (5735000 KHz - 5835000 KHz @
80000 KHz), (N/A, 2000 mBm), (N/A)
May 27 10:05:58 raspberrypi kernel: cfg80211:   (57240000 KHz - 63720000 KHz
@ 2160000 KHz), (N/A, 0 mBm), (N/A)
May 27 10:07:06 raspberrypi start.sh[1098]: 10:07:06.883 [    MQTT Ping:
@7309] ERROR o.e.p.c.m.i.ClientState - @7309: Timed out as no activity,
keepAlive=60,000 lastOutboundActivity=1,464,357,966,877
lastInboundActivity=1,464,357,907,045 time=1,464,358,026,876
lastPing=1,464,357,966,877
May 27 10:07:06 raspberrypi start.sh[1098]: 10:07:06.943 [    MQTT Ping:
@7309]  INFO c.l.h.s.h.a.ApsService - APS connection lost
May 27 10:07:06 raspberrypi start.sh[1098]: 10:07:06.944 [
aps-reconnect]  INFO c.l.h.s.h.a.ApsService - Attempting to reconnect APS
May 27 10:07:07 raspberrypi start.sh[1098]: 10:07:07.082 [
aps-reconnect]  INFO c.l.h.s.h.a.ApsService - Failed to reconnect APS;
retrying in 10000 ms
May 27 10:07:07 raspberrypi start.sh[1098]: com.lni.aps.ApsException: Error
connecting to MQTT broker
May 27 10:07:07 raspberrypi start.sh[1098]: at
com.lni.aps.ahd.AhdMqttClient.connect(AhdMqttClient.java:152)
~[aps-1.0.6.jar!/:na]
May 27 10:07:07 raspberrypi start.sh[1098]: at
com.lni.hhh.service.hdata.aps.ApsService$ReconnectThread.run(ApsService.java
:287) ~[h3l-2.1.0-beta9.jar!/:na]
May 27 10:07:07 raspberrypi start.sh[1098]: Caused by:
org.eclipse.paho.client.mqttv3.MqttException: MqttException

The command line used to start wpa_supplicant is: /sbin/wpa_supplicant -u -s
-O /run/wpa_supplicant

wpa_supplicant config file:
country=GB
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

Barry Reinhold (mailto:reinholds at comcast.net)





More information about the Hostap mailing list