Unable to connect to Wifi after update and multiple reads

Reply to Unable to connect to Wifi after update and multiple reads on Mon, 10 Dec 2018 19:27:44 GMT

Nick B — Mon, 10 Dec 2018 19:27:44 GMT

Hey guys,

After a few hours reading and trying to fix my wifi connection, I give up and must ask for help.

Using SSH, I factory resetted the Omega2+, ran wifisetup and now what??

ifconfig does not give me an IP address.

Here's the content /etc/config/wireless file

config wifi-device 'radio0'
        option type 'ralink'
        option variant 'mt7628'
        option country 'US'
        option hwmode '11g'
        option htmode 'HT40'
        option channel 'auto'
        option disabled '0'
        option device_mode 'apsta'
        option op_mode 'preference'

config wifi-iface 'ap'
        option device 'radio0'
        option mode 'ap'
        option network 'wlan'
        option ifname 'ra0'
        option encryption 'psk2'
        option key '12345678'
        option disabled '0'
        option ssid 'Omega-1439'

config wifi-iface 'sta'
        option device 'radio0'
        option mode 'sta'
        option ifname 'apcli0'
        option encryption 'psk2'
        option network 'wwan'
        option disabled '0'
        option key 'MY_PASSWORD'
        option ssid 'MY_SSID'

config wifi-config
        option key 'MY_PASSWORD'
        option ssid 'MY_SSID'
        option encryption 'psk2'

Firmware version : Ω-ware: 0.2.1 b199
I'm using putty on Windows 10.

Thanks for giving a hand in advance!

Reply to Unable to connect to Wifi after update and multiple reads on Mon, 10 Dec 2018 22:31:54 GMT

Maximilian Gerhardt — Mon, 10 Dec 2018 22:31:54 GMT

Check dmesg for messages indicating that its trying to connect to a network.

Reply to Unable to connect to Wifi after update and multiple reads on Tue, 11 Dec 2018 08:51:12 GMT

cas — Tue, 11 Dec 2018 08:51:12 GMT

@Nick-B
Please take a look here FAQ: How do I check if I'm successfully connected to a WiFi network? and try the various checks listed.

If everything checks out, posting the results of the different checks here might provide the experts reviewing the thread with some clues as to what is happening.

Reply to Unable to connect to Wifi after update and multiple reads on Wed, 12 Dec 2018 15:37:02 GMT

Nick B — Wed, 12 Dec 2018 15:37:02 GMT

Ok, I was gone for 2 days and it seems to be connected. It might be the delay it takes to get a connection.

But I'm unable to ping the device or access it using SSH via the ip address. What config should I change?

Here's the ifconfig :

apcli0    Link encap:Ethernet  HWaddr 40:A3:6B:C2:14:XX
          inet addr:192.168.X.YY  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::42a3:6bff:fec2:14XX/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:27199 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

I noticed that the dropped packets from RX is quite high.

UPDATE
After updating the firmare using oupgrade. The connection has been lost.

I've followed @cas instructions from the given link.
iwconfig gives me this result

apcli0    RTWIFI SoftAP  ESSID:"MySSID"
          Mode:Managed  Channel=3  Access Point: 70:8B:CD:31:26:XX
          Bit Rate=150 Mb/s

It shows it is connected.

ifconfigshows me this

apcli0    Link encap:Ethernet  HWaddr 40:A3:6B:C2:14:XX
          inet6 addr: fe80::42a3:6bff:fec2:14XX/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:38 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

And I'm unable to ping anything

root@Omega-1439:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
ping: sendto: Network unreachable

What are the next steps?

Reply to Unable to connect to Wifi after update and multiple reads on Thu, 13 Dec 2018 07:50:19 GMT

cas — Thu, 13 Dec 2018 07:50:19 GMT

@Nick-B

What are the next steps?

The missing 'inet addr' in the latest ifconfig output would indicate that the device has not successfully received an address via dhcp from your AP, so it isn't successfully connected.

I can replicate this by using an incorrect password when trying to connect to my AP. ie. iwconfig shows a successful looking apcli0 entry, while no inet addr on the same interface reflects in ifconfig.

Perhaps try removing the wifi network and re-adding it?

Or some additional log info may help diagnose further?