Omega2+ fails to connect to wifi



  • @Stephen-Tunney Myself and others are trying to help you, using our own free time, I don't see anyone making excuses.

    Your error is consistent with the insufficient entropy issue which is clearly reported by multiple sources on multiple hardware devices. Since entropy randomness is effected by environmental factors such as radio noise even a change in environment may have an impact. Try installing haveged daemon which was designed to address this issue.

    Make sure you have uncommented the package repository in /etc/opkg/disfeeds.conf
    src/gz openwrt_packages http://downloads.openwrt.org/releases/18.06-SNAPSHOT/packages/mipsel_24kc/packages

    run opkg update
    run opkg install haveged

    restart your omega.



  • @crispyoz said in Omega2+ fails to connect to wifi:

    haveged

    Okay so first off. I don't see anyone from Onion.io actually contributing to the resolution of this issue. Second of all, it effects EVERY device they currently sell. This post in the community is the most viewed by everyone by over an order of magnitude and there is no new kernel available to resolve this issue. Why not have "haveged" on by default? Why not revert the MT7688 driver to the version that was working in 0.1.5 b130?

    Third, if I don't have a working internet connection on the device how should I go about running opkg *??? This seems like a tough thing to accomplish. I don't have an Ethernet board to connect to this to magically create a valid network connection.



  • @crispyoz

    I connected to an OPEN ssid (not recommended for ANYONE, this is just plain dumb) and did the opkg update and installed haveged.

    Didn't fix the problem.

    @Lazar-Demin what is Onion doing about this? There is no end in sight for a simple, secure network connection.



  • @Ganescu-Theodor I believe this has solved my problem. Not exactly a resolution but at least not @onion has something they can change.

    @onion please REMOVE the 'option country 'US' from the canned /etc/config/wireless file that comes with the firmware!

    Could this be necessary for US encryption export laws?



  • @Ganescu-Theodor I can concur on three different Onion 2(+) devices (one plus, two just 2s) that this fix works on 0.2.2 (latest stable) and 0.3.2 (latest).

    You deserve a $10,000 USD bug bounty for this.

    @onion.... BOOOOOOOOO!!!! I spent like a week of evenings on this. For SHAME! Fix it or hang it up and let the rest of us sleep.



  • All of my Omega have this option set to US, even though I am in Oz. I have no issue with 80+ Omega set this way. In OZ we tend to receive products designed for US market.

    It would be interesting to know if there there is an issue when using WiFi provided by devices designed for European market etc. Logically this would explain the setting to which you refer. You're suggesting it is a defect, it would appear to be a configuration option that needs to be further documented.



  • I live in Canada. Sadly, this is as close to American WiFi as it gets :)
    If the channel is set to auto, does it really matter what country I'm in? Shouldn't the driver scan and auto-negotiate all of this? Why was this working in 0.1.15 b130 WITHOUT removing this option?

    Still smells A LOT like a defect given the fact that it worked with canned configured out of the box in prior releases of the firmware.



  • I've just dusted off my original kickstarter 2's and 2+'s and have wasted a day doing the wifi dance.

    So i've updated a 2 to latest firmware, factory reset it and the wifi flatly refuses to connect to any network. I've tried my regular home router. A mobile phone hotspot, my windows 10 desktop hotspot and a shared AP on an Orange Pi Zero.

    All of these I can successfully connect to using esp32 and esp8266 so the wifi networks are configured fine. The problem is clearly with the OO2 firmware.



  • Digging deeper... can these things handle (or be configured to handle) connecting to an access point using CCMP encryption?



  • @Stephen-Tunney Ah! A fellow Ubiquity networks user. I have been getting grey hairs trying to get my Onion Omega2 to connect to my Unify Ap-AC-Lite and Pro. Latests firmwares on APs.
    Tried Omega2 firmware 0.2.2 and 0.3.2 to no avail.

    The Omegas can scan the network fine, but they simply will never-ever connect to it. Unify logs show no trials whatsoever, neither is my DHCP server.

    Good to know there is at least some --very old-- firmware which works.

    What else I did: tried to connect the Omega2 to an ssid on an Fritzbox router, very widely used in Germany: Nothing as well.

    I will try @Ganescu-Theodor 's suggestion next (have already disabled the US option, but perhaps I should do it directly after 'firstboot -y'



  • @crispyoz Thanks for the tip to turn off Automatically Optimize Network. I will try that.

    However, it took me 10 minute to find the setting. For future reference: it is in the top "Site" tab, not any of the 30 other pages in the 'Settings'.



  • @crispyoz Thank you for this tech insight.

    I do wonder with @Stephen-Tunney why no-one from Onion is remotely looking and solving this issue, after TWO years!
    Luckily I have an ethernet dock, otherwise I would go bonkers.



  • @Axel-Roest I think Onion should just document the country option setting so users can understand what it is used for, since the warp core driver is not opensource, otherwise we could just look at the source.

    I still don't see it as a defect, since switching the country option off fixes the issue.



  • @Ganescu-Theodor

    OMG, this worked! I have been working on this for days. Tried your 'remove option US' all the time, but the devil is in the details.
    I connected using the ethernet dock, as the AP wifi would disconnect every 30 seconds.

    My steps

    1. firstboot -y
    2. sync
    3. reboot
    4. Connect to the AP wifi (Omega-####). This seems to setup some networking.
    5. Connect to the Omega over ethernet (but first purge ssh_key in .ssh/known_hosts)
    6. Removed the line 'option country 'US' from /etc/config/wireless
    7. reboot, again
    8. Added wifi network with wifisetup add -ssid MyNetwork -encr WPA2 -password MyPassword
      (wifisetup list shows a disabled network)
    9. Added another wifi network wifisetup add -ssid MySecond -encr WPA2 -password MyPassword
      (I do not know if this is necessary, but we are in voodoo mode now, so just listing all the steps)
      (now wifisetup list shows the first network enabled)
    10. ifconfig shows the Omega connected to apcli0, eth0 and br-wlan!

    Even better: my UniFi AP-AC-LR router shows the Omega in its client list.

    Hurray!

    This was all on BusyBox v1.28.3 () built-in shell (ash), with Ω-ware: 0.3.2 b230

    Disconnected the ethernet cable and reset the Omega, and it keeps connecting to the wifi. Incredible.

    Now I just want to know how I can safely remove the default Access Point (ap) network, as that is a big security issue? Nothing about that in the Onion documentation of course...



  • @crispyoz
    In that I respectfully disagree, as it is a default value for only 5% of the world's population. Furthermore, it is only documented for people well versed in OpenWRT setups, which is not the target audience of this 'user friendly' device, and the feature is completely undocumented on Onion's website. So I would call that a defect.

    If they spent 10% of the money on the beautiful packaging on proper testing, we might not have had this issue.

    Just my $0.02 opinion.

    Also just installed haveged, thanks, but I don't know if the better random generator will help here.



  • @Axel-Roest I'm not sure the issue effects 95% of the world, I have my devices spread across Australia, New Zealand and a few in Indonesia, none of which have the issue. My suspicion is that the issue is some compatibility between wifi hardware sold in different markets, just as I shouldn't by a mobile phone designed for the US market as I will have some issues here in Australia since there are differences in the radio used. Some simple documentation would resolve the issue, just as we set the timezone, we should set the country. We just need the information made available.

    Ubiquiti Unifi hardware also runs OpenWRT and I probably have a dozen sites using Ubiquiti hardware so this suggests to me it is not an underlying compatibility problem.

    Regarding removing the default access point, you can't, if you disable it you disable client as well, there have been many threads on this issue. My solution is twofold, 1) hide the SSID; 2) set a complex password.



  • @crispyoz Oh wow. I have not even seriously looked into that issue, first-things-first, so to speak.
    I did notice nothing worked when I simply tried to remove the 'ap', or set the mode option to 'sta' instead of 'apsta'.

    Thanks for the enlightenment. There are already 40 access points visible on my laptop, so I will just need to think of a funny name.

    A Raspberry-Pi Zero is also starting to look more and more enticing for this project, but alas, I bought three of these Onion Omega2s and they should be put to good use.



  • @Axel-Roest in your /etc/config/wireless section config.wifi-iface 'ap' add th option:

    option 'hidden' '1'

    This will hide the ap ssid.



  • @Axel-Roest said in Omega2+ fails to connect to wifi:

    Now I just want to know how I can safely remove the default Access Point (ap) network, as that is a big security issue? Nothing about that in the Onion documentation of course...

    Please let us know what is that Omega2 AP "big security issue"?



  • @György-Farkas

    Any visible wifi network is bound to get attacks and WPA/2 crack attacks, which is an attack vector into your home or office network. Especially since OpenWRT is set up by default as an access point, which forwards traffic to the wwan network, i.e. your main network.
    I've set up firewall rules for the VLAN my iot devices are on, but still, less than optimal.

    Would you rather have an extra door or a solid wall in your bank vault?

    Cheers.



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