LM006 Wi-Fi Connection Instability

Technical Support
, , , ,
1

Hi,

I have connected LM006 USB Wi-Fi to Colibri VF61 and Viola Plus carrier board. Board is running on V2.6.b1.
I have followed steps given in this link (link text). Now my issue is After some time board get disconnected from network. When I saw journelctl log, I found that It takes ip address as 169.254.x.x. Because of that board will unable reconnect to my network. I found out that reason behind 169.254.x.x is dhcp request failure. But I couldn’t figure out the reason why it failing to get proper ip from router(192.168.x.x). At the same time, my laptop and smartphone are stay connected to router. So Can anyone tell me the reason/solution for this issue.

Thanks in advance.

snippet of log

Aug 14 19:46:05 colibri-vf avahi-daemon[342]: Registering new address record for fe80::5ef3:70ff:fe24:9471 on wlan0.*.
Aug 14 19:46:05 colibri-vf avahi-daemon[342]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.105.
Aug 14 19:46:05 colibri-vf avahi-daemon[342]: New relevant interface wlan0.IPv4 for mDNS.
Aug 14 19:46:05 colibri-vf avahi-daemon[342]: Registering new address record for 192.168.0.105 on wlan0.IPv4.
Aug 14 19:46:05 colibri-vf connmand[360]: wlan0 {add} address 192.168.0.105/24 label wlan0 family 2
Aug 14 19:46:05 colibri-vf connmand[360]: wlan0 {add} route 192.168.0.0 gw 0.0.0.0 scope 253 
Aug 14 19:46:05 colibri-vf connmand[360]: wlan0 {add} route 192.168.0.1 gw 0.0.0.0 scope 253 
Aug 14 19:46:05 colibri-vf connmand[360]: wlan0 {add} route 0.0.0.0 gw 192.168.0.1 scope 0 
Aug 14 19:46:06 colibri-vf connmand[360]: wlan0 {add} route 82.165.8.211 gw 192.168.0.1 scope 0 
Aug 14 19:46:06 colibri-vf connmand[360]: wlan0 {del} route 82.165.8.211 gw 192.168.0.1 scope 0 
Aug 14 19:46:10 colibri-vf app_start.sh[351]: [2017-08-14 19:46:10] [connect] Successful connection
Aug 14 19:46:10 colibri-vf app_start.sh[351]: [2017-08-14 19:46:10] [connect] WebSocket Connection 52.10.155.7:80 v-2 "WebSocket++/0.5.1" /socket.io/?EIO=4&transport=websocket&t=1502720170 101
Aug 14 19:49:06 colibri-vf avahi-daemon[342]: Withdrawing address record for 192.168.0.105 on wlan0.
Aug 14 19:49:06 colibri-vf avahi-daemon[342]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.105.
Aug 14 19:49:06 colibri-vf avahi-daemon[342]: Interface wlan0.IPv4 no longer relevant for mDNS.
Aug 14 19:49:06 colibri-vf connmand[360]: wlan0 {del} address 192.168.0.105/24 label wlan0
Aug 14 19:49:06 colibri-vf connmand[360]: wlan0 {del} route 192.168.0.0 gw 0.0.0.0 scope 253 
Aug 14 19:49:46 colibri-vf avahi-daemon[342]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.126.225.
Aug 14 19:49:46 colibri-vf avahi-daemon[342]: New relevant interface wlan0.IPv4 for mDNS.
Aug 14 19:49:46 colibri-vf avahi-daemon[342]: Registering new address record for 169.254.126.225 on wlan0.IPv4.
Aug 14 19:49:46 colibri-vf connmand[360]: wlan0 {add} address 169.254.126.225/16 label wlan0 family 2
Aug 14 19:49:46 colibri-vf connmand[360]: wlan0 {add} route 169.254.0.0 gw 0.0.0.0 scope 253 
Aug 14 19:49:46 colibri-vf connmand[360]: wlan0 {add} route 0.0.0.0 gw 0.0.0.0 scope 253
2

I believe we already answered your question by email. However if you refuse to upgrade to a later BSP version we are sorry that we are not able to help you.

3

I have observed same issue on latest BSP(v2.7b3) and specified in mail.

4

Update

Issue has been with wifi-driver. It is working well with backported driver. So After Dominik’s commit on git repo, I have build new image for latest bsp version.

Thanks

5

Thanks for the update, glad it works with the backports!

6

Hi mbajaria, what backported driver are you talking?

Thanks for your help,
Stefano.

7

Starting with our BSP 2.7b4 we include Bluetooth and Wi-Fi drivers from backports.