[SOLVED] Omega can't connect to WiFi



  • Hi @Nito-Weber, can you run the following commands:

    uci set wireless.radio0.disabled=0
    uci commit
    wifi
    


  • @Boken-Lin i did it and that was the output:
    upload-5170d23e-7bda-496e-8ad3-5b8694ac9c1a

    i tryed ping google.com and it worked and now i can finally run oupgrade !!!! thank you so much @Boken-Lin , we made it! :heart: :+1:



  • @Nito-Weber Awesome!



  • @Boken-Lin
    Hi
    I have tried eveything listed above and still no luck in connecting to my Wifi.
    If I setup a hotspot on my ohone I am able to connect and have done the firware upgrade but still am not able to connect to my wifi.
    I have an Arduino YUN that connected first time without any problems.

    My wifi is running WPA2 with aes. This is the first device that I have had problems connecting to my WiFi.

    Any help would be much appreciated.



  • Hi @Ian-Carr, Does your Omega able to serve an access point? Can you connect to the Omega via serial terminal, and copy and paste the output on the terminal when you try to connect with the wifisetup command?

    Thanks.



  • @Boken-Lin Here is the output from wifisetup.

    wifisetup
    Onion Omega Wifi Setup

    Select from the following:

    1. Scan for Wifi networks
    2. Type network info
      q) Exit

    Selection: 1
    Scanning for wifi networks...

    Select Wifi network:

    1. EnergyCybernetics2
    2. EnergyCybernetics2

    Selection: 1
    Network: EnergyCybernetics2
    Authentication type: psk2
    Enter password: **********

    Connecting to EnergyCybernetics2 network using intf 0...
    [ 227.080000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 228.560000] wlan0: authenticate with 4c:5e:0c:36:0a:bd
    [ 228.580000] wlan0: send auth to 4c:5e:0c:36:0a:bd (try 1/3)
    [ 228.580000] wlan0: authenticated
    [ 228.600000] wlan0: associate with 4c:5e:0c:36:0a:bd (try 1/3)
    [ 228.610000] wlan0: RX AssocResp from 4c:5e:0c:36:0a:bd (capab=0x431 status=0 aid=1)
    [ 228.620000] wlan0: associated
    [ 228.620000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 233.610000] wlan0: deauthenticated from 4c:5e:0c:36:0a:bd (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)
    Checking wwan device status...
    wwan is not up!!
    Checking internet connection...
    [ 244.490000] wlan0: authenticate with 4c:5e:0c:36:0a:e1
    [ 244.510000] wlan0: direct probe to 4c:5e:0c:36:0a:e1 (try 1/3)
    [ 244.720000] wlan0: direct probe to 4c:5e:0c:36:0a:e1 (try 2/3)
    [ 244.930000] wlan0: direct probe to 4c:5e:0c:36:0a:e1 (try 3/3)
    [ 245.140000] wlan0: authentication with 4c:5e:0c:36:0a:e1 timed out
    [ 245.930000] wlan0: authenticate with 4c:5e:0c:36:0a:bd
    [ 245.950000] wlan0: send auth to 4c:5e:0c:36:0a:bd (try 1/3)
    [ 245.950000] wlan0: authenticated
    [ 245.980000] wlan0: associate with 4c:5e:0c:36:0a:bd (try 1/3)
    [ 245.990000] wlan0: RX AssocResp from 4c:5e:0c:36:0a:bd (capab=0x431 status=0 aid=1)
    [ 245.990000] wlan0: associated
    [ 250.990000] wlan0: deauthenticated from 4c:5e:0c:36:0a:bd (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)
    ERROR: request timeout, internet connection not successful
    Disabling network on iface 0 ...
    Done!
    root@Omega-09C5:/# [ 271.910000] wlan0: authenticate with 4c:5e:0c:36:0a:bd
    [ 271.930000] wlan0: send auth to 4c:5e:0c:36:0a:bd (try 1/3)
    [ 271.930000] wlan0: authenticated
    [ 271.960000] wlan0: associate with 4c:5e:0c:36:0a:bd (try 1/3)
    [ 271.970000] wlan0: RX AssocResp from 4c:5e:0c:36:0a:bd (capab=0x431 status=0 aid=8)
    [ 271.970000] wlan0: associated
    [ 271.980000] wlan0: deauthenticating from 4c:5e:0c:36:0a:bd by local choice (Reason: 3=DEAUTH_LEAVING )

    root@Omega-09C5:/#



  • @Nito-Weber , might be a good idea to remove in your firs post the [resolved] from the title. So we can continue using it for the same problem with the experiences you made.



  • I installed build omega-v0.0.6-b279 from http://repo.onion.io/omega/images/
    using the method discribed in https://community.onion.io/topic/358/factory-reset-not-working/2

    The wifi setup worked first time and is running great.



  • @Nito-Weber ... Most dorm networks have 801.2x security which requires additional configuration (EAP/AUTH Type etc). This cannot be done on the omega because it ships with 'wpad-mini' by default. If you still would like to use it in your dorm then try the method in this post:

    https://community.onion.io/topic/27/wifi-wpa2-eap-peap-mschapv2/7

    @Boken-Lin & @Lazar-Demin - if I may suggest why not make 'wpad' the default rather than the 'wpad-mini'. I believe it will solve most of the connectivity issues. Of course it will eat up a few kb more space but it could be worth it.



  • @Boken-Lin Hi, I changed my wireless configuration to your config. After that I received "Invalid mode". Now I can't see any wifi from the onion. Can I hard reset it, without ssh to it? I hope I don't bricked it :(



  • My WIFI is at WEP. Omega2 does not connect to this AP, but when I tired my hotspot on my nexues 5 (which is WPA2) it connected. Any help from any one is much appreciated.



  • @Gayan-Priyanatha Same problem for me. At a customer site they are using WiFi with WEP and a code like 429a2936580b72330486c13973. Trying to configure this yields the following result:

     root@Omega-5857:~# wifisetup add -ssid Visitors -encr WEP -password     429a2936580b72330486c13973
    > Restarting wifimanager for changes to take effect
    root@Omega-5857:~# wifisetup list
    {
    
        "results": [
     {
        "ssid": "xxxxxxxxxxxxx",
        "encryption": "WPA2PSK",
        "password": "yyyyyyyyyyyyyyyy" 
    },
        {
    
        "ssid": "Visitors",
        "encryption": "WEP",
        "password": "1" 
     } 
    ] 
    }


  • @Nito-Weber I'm using WPA-TKIP and can't connect unless I go Open. I understand AES works. Is this just as good as TKIP?



  • @Gayan-Priyanatha @Peter-Lelie If it's at all possible, you should consider setting your wifi router to WPA2-AES instead of WEP (very vulnerable).
    @Don-DeGregori TKIP was deprecated in the 2012. Same advice to you!



  • @Gayan-Priyanatha Have you tried this?



  • @fossette Thanks for your advice, but sometimes there are networks which you need to use that you can not change, because the owner is not you ;-)
    And WEP is still a valid encryption method, albeit insecure.



  • HI!
    I tried all abovementioned tricks on my Omega2+ but no luck. The thing that helped was disabling "Hidden SSID" option in my router. It is sometimes called "Broadcast SSID" too (but with opposite meaning). Looks like current setup does not work with 'hidden' SSIDs.



  • @Sergey-Melekhin , i changed router and use hidden ssid to. No luck till now with omega1. So why should I expose my private network to the neighborhood just to play with IOT?!



  • @Luciano-S. hidden ssid does not make my network a tiniest bit more secure than WPA2PSK AES does, so I got rid of it with no regret.



  • I know.. it is just hidden when you browse the wifi network. The list just keeps shorter if you not expose to everyone. I believe some smart software can make it anyway visible.


Log in to reply
 

Looks like your connection to Community was lost, please wait while we try to reconnect.