WiFi doesn't start

Reach Module / M+ / M2 Getting started
1

Hello

I work with “Reach RTK GNSS Module”. And I faced with problem of WiFi working.

  1. I done all steps from instructions. I connected to reach:xx:xx WiFi, opened Web Interface, and setup settings of my WiFi net. After that Reach reconnected to my local WiFi network, and I changed WiFi to my local network. All good, I found IP of the Reach and opened Web Interface in my local WiFi network

  2. After that I reboot the Rach. And trying to find IP address in my local WiFi network - but nothing, And the Reach doesn’t run wifi hotspot. I can’t open web interface!

  3. I connected USB and open SSH by IP 192.168.2.15 (by RNDIS). And done the command ifconfig.
    That is result:

    root@reach_rover[~]# ifconfig
    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:570 errors:0 dropped:0 overruns:0 frame:0
    TX packets:570 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:34519 (33.7 KiB) TX bytes:34519 (33.7 KiB)

usb0 Link encap:Ethernet HWaddr 02:00:86:96:9b:23
inet addr:192.168.2.15 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::86ff:fe96:9b23/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:706 errors:0 dropped:4 overruns:0 frame:0
TX packets:307 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:119005 (116.2 KiB) TX bytes:47766 (46.6 KiB)

WiFi doesn’t start! What am I doing wrong?

Thanks a lot!

4

Do you have any other device with IP address on your network with only one digit at the end? e.g 192.168.1.x

5

I used nmap to check:
nmap -sn 192.168.1.0/24
in my network, and there isn’t any result.

6

Sorry, I should have written 192.168.2.x

7

If I connect micro-USB cable, nmap shows 2 device.
1st: 192.168.2.2 - ip address of the RNDIS at my PC (I myself have set such an IP according to the instructions)
2nd: 162.168.2.15 - ip address of Reach. I can connect to this IP by SSH.

If I disconnect micro-USB,then there aren’t devices with IP like 192.168.2.x

But how does this relate to the fact, that ifconfig shows that the WiFi (wlan0) is not running?

8

Reach may be connected but not reachable, due to this Can not connect to the reach RS - #6 by igor.vereninov and therefore not creating hotspot either.

9

Ok.
If I understand correct, I must exclude the possibility of issuing IP like 192.168.2.x from DHCP?

My local WiFi network has IP address only like 192.168.15.x. And before wlan0 stopped running I worked with device at IP 192.168.15.52. Then I was reboot device and Reach weren’t connect to my local WiFi and weren’t start hotspot.

10

Yes

11

Ok.

As I wrote, in my local WiFi network has IP only like 192.168.15.x. DHCP can’t set IP to the device 192.168.2.x

In addition, if the device was connected to wifi with ip 192.168.2.x, I must look this connection wlan0 in result ifconfig command. But wlan0 does not work at all!

What can I try to do?

12

Could you try share a new wifi AP network on your phone or another router/AP for reach to connect to? you need to turn of existing wifi or log in to reach hotspot and delete it before connecting to new network. This is to rule out any issue with current wifi.

13

Hello!

Did you manage to go through the update process?

This behavior reminds me of an issue we had some time ago, but fixed in one of the updates. Could you please post the output of command rfkill list?

If it shows wlan as disabled do the following over a USB connection:

  • rfkill unblock wlan
  • ifconfig wlan0 up
  • systemctl stop hostapd && systemctl restart wpa_supplicant

This will help you to establish the Wi-Fi connection again. If you haven’t actually updated, this should not be a problem in the last released version. If you did in fact update, then we would ask to help us debug this issue. To do this, please send me the output of the following commands:

  • journalctl -u reach_setup --no-pager
  • journalctl -u wpa_supplicant --no-pager
14

When I turned on reach first time update process finished successfully. Now version 2.9.0

rfkill list returns:

0: phy0: wlan
    Soft blocked: no
    Hard blocked: no
1: brcmfmac-wifi: wlan
    Soft blocked: no
    Hard blocked: no
2: bcm43xx Bluetooth: bluetooth
    Soft blocked: yes
    Hard blocked: no

I executed the following commands:

rfkill unblock wlan
ifconfig wlan0 up
systemctl stop hostapd && systemctl restart wpa_supplicant

What was going to happen after that? ifconfig shows next:

root@emlid_base[~]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:9079 errors:0 dropped:0 overruns:0 frame:0
TX packets:9079 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:621462 (606.8 KiB) TX bytes:621462 (606.8 KiB)

usb0 Link encap:Ethernet HWaddr 02:00:86:65:84:51
inet addr:192.168.2.15 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::86ff:fe65:8451/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:342 errors:0 dropped:9 overruns:0 frame:0
TX packets:256 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:41015 (40.0 KiB) TX bytes:58971 (57.5 KiB)

wlan0 Link encap:Ethernet HWaddr 90:b6:86:0e:3d:61
inet6 addr: fe80::92b6:86ff:fe0e:3d61/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1660 (1.6 KiB)

root@emlid_base[~]# journalctl -u reach_setup --no-pager
– Logs begin at Fri 2017-10-06 13:33:13 UTC, end at Fri 2017-10-06 13:34:15 UTC. –
Oct 06 13:33:18 emlid_base systemd[1]: Starting Emlid Reach setup…
Oct 06 13:33:18 emlid_base systemd[1]: Started Emlid Reach setup.
Oct 06 13:33:24 emlid_base reach_setup[246]: Traceback (most recent call last):
Oct 06 13:33:24 emlid_base reach_setup[246]: File “/usr/bin/init_network”, line 45, in
Oct 06 13:33:24 emlid_base reach_setup[246]: initialize()
Oct 06 13:33:24 emlid_base reach_setup[246]: File “/usr/bin/init_network”, line 31, in initialize
Oct 06 13:33:24 emlid_base reach_setup[246]: wifi_controller.turn_on_wifi()
Oct 06 13:33:24 emlid_base reach_setup[246]: File “/usr/lib/python2.7/site-packages/wificontrol/wificontrol.py”, line 60, in turn_on_wifi
Oct 06 13:33:24 emlid_base reach_setup[246]: self.wpasupplicant.start()
Oct 06 13:33:24 emlid_base reach_setup[246]: File “/usr/lib/python2.7/site-packages/wificontrol/wpasupplicant.py”, line 73, in start
Oct 06 13:33:24 emlid_base reach_setup[246]: self.execute_command(self.wpas_control(“start”))
Oct 06 13:33:24 emlid_base reach_setup[246]: File “/usr/lib/python2.7/site-packages/wificontrol/wificommon.py”, line 87, in execute_command
Oct 06 13:33:24 emlid_base reach_setup[246]: raise WiFiControlError(error_message)
Oct 06 13:33:24 emlid_base reach_setup[246]: wificontrol.wificommon.WiFiControlError: WiFiControl: subprocess call error
Oct 06 13:33:24 emlid_base reach_setup[246]: Return code: 1
Oct 06 13:33:24 emlid_base reach_setup[246]: Command: systemctl start wpa_supplicant.service && sleep 2
Oct 06 13:33:24 emlid_base reach_setup[246]: Exception in thread Thread-1:
Oct 06 13:33:24 emlid_base reach_setup[246]: Traceback (most recent call last):
Oct 06 13:33:24 emlid_base reach_setup[246]: File “/usr/lib/python2.7/threading.py”, line 551, in __bootstrap_inner
Oct 06 13:33:24 emlid_base reach_setup[246]: self.run()
Oct 06 13:33:24 emlid_base reach_setup[246]: File “/usr/lib/python2.7/threading.py”, line 504, in run
Oct 06 13:33:24 emlid_base reach_setup[246]: self.__target(*self.__args, **self.__kwargs)
Oct 06 13:33:24 emlid_base reach_setup[246]: File “/usr/lib/python2.7/site-packages/dev_utils/setup/reach_setup.py”, line 135, in _network_scan
Oct 06 13:33:24 emlid_base reach_setup[246]: Variables.network_status = subprocess.check_output(“init_network”)
Oct 06 13:33:24 emlid_base reach_setup[246]: File “/usr/lib/python2.7/subprocess.py”, line 544, in check_output
Oct 06 13:33:24 emlid_base reach_setup[246]: raise CalledProcessError(retcode, cmd, output=output)
Oct 06 13:33:24 emlid_base reach_setup[246]: CalledProcessError: Command ‘init_network’ returned non-zero exit status 1
Oct 06 13:33:26 emlid_base reach_setup[246]: u-blox:true,mpu:true,ltc:true,stc:true,lora:true
Oct 06 13:33:26 emlid_base reach_setup[246]: ReachRS
Oct 06 13:33:27 emlid_base reach_setup[246]: None
Oct 06 13:33:27 emlid_base reach_setup[246]: Error for wireless request “Set Power Management” (8B2C) :
Oct 06 13:33:27 emlid_base reach_setup[246]: SET failed on device wlan0 ; Input/output error.
Oct 06 13:33:34 emlid_base reach_setup[246]: (343) wsgi starting up on http://0.0.0.0:5000
Oct 06 13:33:40 emlid_base reach_setup[246]: ----> Initializing main blueprint…
Oct 06 13:33:40 emlid_base reach_setup[246]: Done
Oct 06 13:33:40 emlid_base reach_setup[246]: ----> Initializing rtk_broadcasts blueprint…
Oct 06 13:33:40 emlid_base reach_setup[246]: Done
Oct 06 13:33:40 emlid_base reach_setup[246]: ----> Initializing bluetooth blueprint…
Oct 06 13:33:40 emlid_base reach_setup[246]: Done
Oct 06 13:33:40 emlid_base reach_setup[246]: ----> Initializing logging blueprint…
Oct 06 13:33:40 emlid_base reach_setup[246]: Done
Oct 06 13:33:40 emlid_base reach_setup[246]: ----> Initializing wireless blueprint…
Oct 06 13:33:40 emlid_base reach_setup[246]: Done
Oct 06 13:33:40 emlid_base reach_setup[246]: ----> Initializing gnss_updater blueprint…
Oct 06 13:33:40 emlid_base reach_setup[246]: Done
Oct 06 13:33:40 emlid_base reach_setup[246]: ----> Initializing surveying blueprint…
Oct 06 13:33:40 emlid_base reach_setup[246]: Done
Oct 06 13:33:40 emlid_base reach_setup[246]: ----> Initializing configuration blueprint…
Oct 06 13:33:40 emlid_base reach_setup[246]: Received a new configuration to apply:
Oct 06 13:33:40 emlid_base reach_setup[246]: {‘base mode’: {‘base coordinates’: {‘accumulation’: u’2’,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘antenna offset’: {‘east’: u’0’,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘north’: u’0’,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘up’: u’0’},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘coordinates’: [u’55.7744304543’, Oct 06 13:33:40 emlid_base reach_setup[246]: u’37.6292671483’,
Oct 06 13:33:40 emlid_base reach_setup[246]: u’185.464’],
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘format’: u’llh’,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘mode’: u’single-and-hold’},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘output’: {‘enabled’: True,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘format’: u’rtcm3’,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘path’: u’ntrips://:user@mycaster.com:8080/MOUNTPOINT#rtcm3’,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘type’: u’ntrips’},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘rtcm3 messages’: {‘1002’: {‘enabled’: True,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘frequency’: u’5’},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘1006’: {‘enabled’: True,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘frequency’: u’0.1’},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘1008’: {‘enabled’: False,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘frequency’: u’1’},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘1010’: {‘enabled’: True,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘frequency’: u’5’},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘1019’: {‘enabled’: True,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘frequency’: u’1’},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘1020’: {‘enabled’: True,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘frequency’: u’1’},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘1097’: {‘enabled’: False,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘frequency’: u’1’},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘1107’: {‘enabled’: False,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘frequency’: u’1’},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘1117’: {‘enabled’: False,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘frequency’: u’1’},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘1127’: {‘enabled’: False,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘frequency’: u’1’}}},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘bluetooth’: {‘discoverable’: False, ‘enabled’: False, ‘pin’: 123456},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘correction input’: {‘input2’: {‘enabled’: False,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘format’: u’rtcm3’,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘path’: u’test:user@mycaster.com:8080/MOUNTPOINT’,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘send position to base’: u’off’,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘type’: u’ntripcli’},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘input3’: {‘enabled’: False,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘format’: u’rtcm3’,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘path’: u’:9028’,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘type’: u’tcpsvr’}},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘logging’: {‘base’: {‘format’: u’RTCM3’, ‘started’: True, ‘version’: None},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘correction’: {‘format’: u’RTCM3’,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘started’: True,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘version’: None},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘interval’: 24,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘overwrite’: True,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘raw’: {‘format’: u’UBX’, ‘started’: True, ‘version’: None},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘solution’: {‘format’: u’LLH’, ‘started’: True, ‘version’: None}},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘lora’: {‘air rate’: 2.6000000000000001,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘frequency’: 868000,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘output power’: 20},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘position output’: {‘output1’: {‘enabled’: False,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘format’: u’nmea’,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘path’: u’bluetooth’,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘type’: u’bluetooth’},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘output2’: {‘enabled’: True,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘format’: u’llh’,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘path’: u’:2013’,
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘type’: u’tcpsvr’}},
Oct 06 13:33:40 emlid_base reach_setup[246]: ‘rtk settings’: {‘elevation mask angle’: u’20’,
Oct 06 13:33:42 emlid_base reach_setup[246]: ‘glonass ar mode’: u’oService bt_daemon.service is not running.
Oct 06 13:33:46 emlid_base reach_setup[246]: (354) wsgi starting up on http://0.0.0.0:80

root@emlid_base[~]# journalctl -u wpa_supplicant --no-pager
– Logs begin at Fri 2017-10-06 13:33:13 UTC, end at Fri 2017-10-06 13:34:15 UTC. –
Oct 06 13:33:23 emlid_base systemd[1]: Starting WPA supplicant service…
Oct 06 13:33:23 emlid_base wpa_supplicant[316]: Successfully initialized wpa_supplicant
Oct 06 13:33:23 emlid_base wpa_supplicant[316]: Line 22: failed to parse phase1 ‘peaplable=0’.
Oct 06 13:33:23 emlid_base wpa_supplicant[316]: Line 22: failed to parse phase1 ‘peaplable=0’.
Oct 06 13:33:23 emlid_base wpa_supplicant[316]: Line 30: failed to parse network block.
Oct 06 13:33:23 emlid_base wpa_supplicant[316]: Failed to read or parse configuration ‘/etc/wpa_supplicant/wpa_supplicant.conf’.
Oct 06 13:33:23 emlid_base systemd[1]: wpa_supplicant.service: main process exited, code=exited, status=255/n/a
Oct 06 13:33:24 emlid_base systemd[1]: Failed to start WPA supplicant service.
Oct 06 13:33:24 emlid_base systemd[1]: Unit wpa_supplicant.service entered failed state.
Oct 06 13:34:14 emlid_base systemd[1]: Starting WPA supplicant service…
Oct 06 13:34:14 emlid_base systemd[1]: Started WPA supplicant service.
Oct 06 13:34:14 emlid_base wpa_supplicant[461]: Successfully initialized wpa_supplicant
Oct 06 13:34:14 emlid_base wpa_supplicant[461]: Line 22: failed to parse phase1 ‘peaplable=0’.
Oct 06 13:34:14 emlid_base wpa_supplicant[461]: Line 22: failed to parse phase1 ‘peaplable=0’.
Oct 06 13:34:14 emlid_base wpa_supplicant[461]: Line 30: failed to parse network block.
Oct 06 13:34:14 emlid_base wpa_supplicant[461]: Failed to read or parse configuration ‘/etc/wpa_supplicant/wpa_supplicant.conf’.
Oct 06 13:34:14 emlid_base systemd[1]: wpa_supplicant.service: main process exited, code=exited, status=255/n/a
Oct 06 13:34:15 emlid_base systemd[1]: Unit wpa_supplicant.service entered failed state.

15

Thanks for the detailed report.

The log shows something is wrong with the wpa_supplicant configuration file, /etc/wpa_supplicant/wpa_supplicant.conf. Is there a chance you have edited it manually?

I am not entirely sure what happened, but its contents could help.
You can print the file with cat /etc/wpa_supplicant/wpa_supplicant.conf.

This is how the file is supposed to be in case of a WPA 2 personal encryption. You may copy this text inside the problematic file, changing the network and psk.

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
config_methods=virtual_push_button virtual_display push_button keypad
update_config=1
fast_reauth=1
device_name=Edison
manufacturer=Intel
model_name=Edison

network={
        psk="YOUR_PSK"
        group=CCMP TKIP
        ssid="YOUR_NETWORK"
        proto=RSN
        pairwise=CCMP TKIP
        eap=TTLS PEAP TLS
        key_mgmt=WPA-PSK
}
16

That helped!

When I opened /etc/wpa_supplicant/wpa_supplicant.conf, I saw 2 netowrk: WPA-PSK and WPA-EAP (I have 2 local WiFi networks). Next I was manually edit /etc/wpa_supplicant/wpa_supplicant.conf - I was delete one of these and reboot device, and all is OK!

So, if I have 2 networks, and I specify two WiFi networks in the device settings, then the wifi will not start.
I also tried leave only network with WPA_EAP, and wifi were not run. It is problem with my network, or settings in Reach wifi?

Thanks a lot!!!

17

Thank you for your patience and cooperation :slight_smile:

So, you had two networks, one of them WPA-EAP? I will look into this, as it seems to be a Reach software problem.

18

Yeap.

Firstly I entered settings of my the first WiFi network WPA_PSK, and connected to it - all is OK. Then I entered settings of my the second WiFi network WPA_EAP, connected to it - all is OK. After that I reboot device and WiFi won’t start at the device.

Thanks for the quick help!

19

I will try to reproduce and fix the problem.

20

Any news of a fix.
Having same/similar problem as Sergei_Kravchenko.
My file /etc/wpa_supplicant/wpa_supplicant.conf looks ok in my case.
Running ReachView 2.9.0

Thanks

21

Please provide more information about the issue that you are experiencing.

22

PROBLEM : Reach not able to connect to WiFi

Have 2 Reach modules running ReachView 2.9.0

Tried 3 different routers(WiFi Thomson and TP-LINK) and a Samsung s8+ in a mobile hotspot

Before ReachView 2.9.0 Reach was able to connect and update

Getting Green LED stable on reach module but no connection on Thomson( not in hotspot mode)
Getting blinking LED if using Samsung hotspot and Reach module goes back into hotspot mode
Reach looks like connected to Thomson router but does not show up on router admin screen and no wifi connection
My file /etc/wpa_supplicant/wpa_supplicant.conf looks ok in my case.

Thanks