Community
cancel
Showing results for 
Search instead for 
Did you mean: 
OLOYN
Novice
3,506 Views

Reconnect Wifi after a network interruption on Edison

Hi,

The Intel Edison don't reconnect after a network interruption (like my Wifi box shutdown)

Edison is installed with the last software

I have the problem with or without connman installed.

Is it normal ? Or I missing something ?

 

I have to reconnect with wpa_cli like this

 

wpa_cli reconfigure

wpa_cli select_network wlan0

udhcpc -i wlan0

Or if connman is installed, I reconnect with

connmanctl scan wifi

Olivier

9 Replies
Matthias_H_Intel
Employee
159 Views

on connman it might take a while until it's reconnected. However, if you set connect to auto for that WiFi service it should reconnect after a while

OLOYN
Novice
159 Views

Yes AutoConnect=true in settings file

Sometimes it takes long time, but most of time it does not reconnect.

Matthias_H_Intel
Employee
159 Views

"I have the problem with or without connman installed."

That would possibly indicate a wifi driver issue meaning that kernel wifi driver does not notice that AP was shutdown etc.

ConnMan only listens various kernel messages about the network link and then acts accordingly. If these message are missing or lost, then there is not much ConnMan can do. Of course there might be other culprit but without debug logs from ConnMan and wpa_supplicant it is difficult to say.

btw: which Edison image are you using?

YHOJO1
New Contributor I
159 Views

Hi oloynet,

I'm not sure my case is same with yours, but it looks similar. I have been experiencing Wifi disconnection almost everyday after I flashed my Edison with ww05-15. Though I may be doing something wrong in my script that uploads status report to share drive periodically, I have never seen this kind of Wifi disconnection when with the previous image (ww42-14). I'm not sure it recovers by itself every time because Wifi disconnection continues hours and I cannot wait.

I removed p2p service from wpa_supplicant.service, but the behavior did not change.

Below is part of the journalctl output when Wifi disconnection happened.

I will try Wifi reconnect that you mentioned, in my script.

Thank you,

vjou

... (For first disconnection in this log, I rebooted Edison about 3 hours later after Wifi disconnection.)

Mar 17 15:30:48 Edison systemd-timesyncd[157]: interval/delta/delay/jitter/drift 2048s/+0.010s/0.024s/0.039s/+9ppm (ignored)

Mar 17 16:04:56 Edison systemd-timesyncd[157]: interval/delta/delay/jitter/drift 2048s/-0.001s/0.019s/0.034s/+9ppm

Mar 17 16:32:39 Edison kernel: CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_DEAUTH_IND

Mar 17 16:32:39 Edison kernel: link down if wlan0 may call cfg80211_disconnected. event : 6, reason=23 from 20:37:06:ab:6e:1f

Mar 17 16:32:39 Edison kernel: CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_LINK

Mar 17 16:32:39 Edison kernel: cfg80211: Calling CRDA to update world regulatory domain

Mar 17 16:32:39 Edison kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Mar 17 16:32:39 Edison wpa_cli[250]: event DISCONNECTED received from wpa_supplicant

Mar 17 16:32:39 Edison wpa_cli[250]: 28446 root 2404 S udhcpc -i wlan0 -p /var/run/udhcpc-wlan0.pid -S

Mar 17 16:32:39 Edison udhcpc[28446]: Received SIGTERM

Mar 17 16:32:39 Edison wpa_cli[250]: rm: can't remove '/var/run/udhcpc-wlan0.pid': No such file or directory

Mar 17 16:32:40 Edison mDNSResponder[244]: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to FF02:0000:0000:0000:0000:0000:0000:00FB on interface FE80:0000:0000:0000:FEC2:DEFF:FE31:6B48/wlan0/3

Mar 17 16:32:40 Edison mDNSResponder[244]: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to FF02:0000:0000:0000:0000:0000:0000:00FB on interface FE80:0000:0000:0000:FEC2:DEFF:FE31:6B48/wlan0/3

Mar 17 16:32:40 Edison mDNSResponder[244]: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to FF02:0000:0000:0000:0000:0000:0000:00FB on interface FE80:0000:0000:0000:FEC2:DEFF:FE31:6B48/wlan0/3

Mar 17 16:32:48 Edison kernel: CFG80211-ERROR) wl_notify_pfn_status : >>> PNO Event

-- Reboot --

... (After reboot, Wifi had been working until 0:30 am, then disconnected. It came back 4:05 am by itself.)

Mar 17 23:28:13 Edison systemd-timesyncd[157]: interval/delta/delay/jitter/drift 2048s/-0.013s/0.026s/0.022s/+10ppm (ignored)

Mar 18 00:02:21 Edison systemd-timesyncd[157]: interval/delta/delay/jitter/drift 2048s/-0.027s/0.026s/0.021s/+3ppm

Mar 18 00:29:12 Edison udhcpc[16409]: Sending renew...

Mar 18 00:29:12 Edison udhcpc[16409]: Lease of XXX.XXX.XXX.XXX obtained, lease time 14400

Mar 18 00:30:04 Edison kernel: CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_DEAUTH_IND

Mar 18 00:30:04 Edison kernel: link down if wlan0 may call cfg80211_disconnected. event : 6, reason=23 from 20:37:06:ab:6e:1f

Mar 18 00:30:04 Edison kernel: CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_LINK

Mar 18 00:30:04 Edison kernel: cfg80211: Calling CRDA to update world regulatory domain

Mar 18 00:30:04 Edison wpa_cli[251]: event DISCONNECTED received from wpa_supplicant

Mar 18 00:30:04 Edison kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Mar 18 00:30:04 Edison wpa_cli[251]: 16409 root 2404 S udhcpc -i wlan0 -p /var/run/udhcpc-wlan0.pid -S

Mar 18 00:30:04 Edison udhcpc[16409]: Received SIGTERM

Mar 18 00:30:04 Edison wpa_cli[251]: rm: can't remove '/var/run/udhcpc-wlan0.pid': No such file or directory

Mar 18 00:30:05 Edison mDNSResponder[247]: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to FF02:0000:0000:0000:0000:0000:0000:00FB on interface FE80:0000:0000:0000:FEC2:DEFF:FE31:6B48/wlan0/3

Mar 18 00:30:05 Edison mDNSResponder[247]: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to FF02:0000:0000:0000:0000:0000:0000:00FB on interface FE80:0000:0000:0000:FEC2:DEFF:FE31:6B48/wlan0/3

Mar 18 00:30:05 Edison mDNSResponder[247]: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to FF02:0000:0000:0000:0000:0000:0000:00FB on interface FE80:0000:0000:0000:FEC2:DEFF:FE31:6B48/wlan0/3

Mar 18 00:30:12 Edison kernel: CFG80211-ERROR) wl_notify_pfn_status : >>> PNO Event

Mar 18 04:05:14 Edison wpa_supplicant[213]: Successfully initialized wpa_supplicant

Mar 18 04:05:14 Edison wpa_supplicant[213]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (org.freedesktop.DBus.Error.Failed) failed to parse WPA IE

Mar 18 04:05:14 Edison wpa_supplicant[213]: dbus: Failed to construct signal

Mar 18 04:05:14 Edison wpa_supplicant[213]: wlan0: Trying to associate with 20:37:06:ab:6e:1f (SSID='xxxxxxxxxx' freq=5200 MHz)

Mar 18 04:05:14 Edison wpa_supplicant[213]: wlan0: Associated with 20:37:06:ab:6e:1f

Mar 18 04:05:14 Edison wpa_supplicant[213]: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started

Mar 18 04:05:14 Edison wpa_supplicant[213]: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=17 -> NAK

Mar 18 04:05:14 Edison wpa_supplicant[213]: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13

Mar 18 04:05:14 Edison wpa_supplicant[213]: EAP-TLS: Private key not configured

Mar 18 04:05:14 Edison wpa_supplicant[213]: wlan0: EAP: Failed to initialize EAP method: vendor 0 method 13 (TLS)

Mar 18 04:05:14 Edison wpa_supplicant[213]: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25

Mar 18 04:05:14 Edison wpa_supplicant[213]: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected

Mar 18 04:05:14 Edison wpa_supplicant[213]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=3 subject='/C=US/O=VeriSign, Inc./OU=Class 3 Public Primary Certification Authority'

Mar 18 04:05:14 Edison wpa_supplicant[213]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=3 subject='/C=US/O=VeriSign, Inc./OU=Class 3 Public Primary Certification Authority'

Mar 18 04:05:14 Edison wpa_supplicant[213]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=(c) 2006 VeriSign, Inc. - For authorized use only/CN=VeriSign Class 3 Public Primary Certification Authority - G5'

Mar 18 04:05:14 Edison wpa_supplicant[213]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='/C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=Terms of use at https://www.verisign.com/rpa https://www.verisign.com/rpa (c)10/CN=VeriSign Class 3 International Server CA - G3'

Mar 18 04:05:14 Edison wpa_supplicant[213]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/C=US/ST=XXXXXXXX/L=XXXXXXXX/O=XXXXXXX/CN=ddpwlrad'

Mar 18 04:05:14 Edison wpa_supplicant[213]: wlan0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully

Mar 18 04:05:14 Edison wpa_s...

Pedro_M_Intel
Employee
159 Views

Hello oloynet,

Could you provide a little more information about your environment, which image are you using? How is your board getting its IP, Static IP? DHCP? Is your network secured? Please post any other detail about your network configuration.

Peter.

wpete1
Novice
159 Views

Hi Peter,

My Edison also lost wifi connection if it is connected over hours and it won't reconnect. If I turn-off interface wlan0 and turn-on again, it can connect to wifi normally.

Can you advise a method to auto-reconnect?

Thanks!

JDodg1
Novice
159 Views

I'm having the same issue. I have two Intel Edisons running at two locations. If their network drops temporarily they seem to permanently lose their connection until reset.

Is there a setting or something I have to configure beyond the default Edison configuration to get them reconnecting reliably?

I'm on the latest Edison image.

They are both getting IP with DHCP.

Networks are secure.

If I run "wpa_cli status" I get "wpa_state=INTERFACE_DISABLED"

DMaye2
Novice
159 Views

Here we go - had the same issue, just figured how to get around it ;

idata
Community Manager
159 Views

@Dave_CT: Good idea to set scan_ssid to 0! I hadn't tried that one yet.

Depending on what is actually happening internal to your board... it may be the issue that myself and another user are experiencing in this thread:

/message/376144# 376144 https://communities.intel.com/message/376144# 376144

The above issue is that the WiFi has been disconnecting & re-connecting and not coming back up with an IP. Not sure if there's a complete solution yet... but I've gone down the path of troubleshooting the OS services responsible for the above mentioned issue.

I was able to find out a way of getting the services to restart & recover from a state of fast disconnect & reconnect cycles.

It doesn't look like yours is doing it too rapidly, but the same restart process should also work.

Reply