1. Home
  2. Omega Talk
  3. Omega2+ fails to connect to wifi

Omega2+ fails to connect to wifi

  • C

    So here's a good one for y'all couldn't get it to connect tried accessing it several times through web interface then through SSH no luck on either end

    But then right as I was about to give up on it I took a smoke break and came back and low and behold the web interface worked... I really want to beat my head against the screen...

    0
  • D

    I must have read all these messages a hundred times without success and finally bought a new router that uses AES instead of TKIP and that was the breakthrough. So after owning two Omega2+ for 6-8 months and not being able to get past first base I started to build something useful. Then I connected an I2C device to one of them and found that the i2cdetect python command does not work There are many many messages devoted to this topic and again the developers of this product sit on their hands.

    Life is too short to spend playing around with a bug ridden immature device such as the Omega2 so you've lost me Onion Community. Bin your Omega2 and sleep again at night.

    0 F 1 Reply
  • F

    @David-Lochlin je suis d'accord, dommage sa petite taille été un super avantage mais bon les développeurs on tellement passé de temps a vouloir le vendre a tout prix en dénigrant les autres produits du même genre qu'ils ont oublié de finir leurs propre produit.
    Au suivant!!!

    0
  • C

    @pvadam
    Good. Really good answer. Enable appcli did the trick !

    0
  • M

    I have had the same issue with an Onion 2+, the annoying thing is, to get connectivity to the internet to see if an update works....
    I fired up an Omega 1, which works no problem on the same wifi.
    Then connect the wifi on the Omega 2 to the AP on the Omega 1 and so through.
    So internet works, but wifi will still not connect to my wireless, so what has changed to make it not work between versions.

    0 Douglas Kryder 1 Reply
  • Douglas Kryder

    @MB hello, i suggest you do some searches on wifi router because last year there were many posts about the abilities of the omega2[+] to connect or not connect to some wireless router models. it seems the omega2 devices have problems with some models of wireless routers.

    0 M 1 Reply
  • M

    @Douglas-Kryder Yeah, thanks, I know it works with other wifi, I have it working on a wifi in my house, its more the fact that the Omega 2+ has poorer wifi support than the original omega, which connects fine. Just thought it was a downgrade in wifi support from the old one, more of me throwing that out there as an FYI.

    0
  • P

    For me the WiFi has also been a mayor pain in the ass. In the end I have now setup a Omega2 to connect to an original Omega which in turn connects to my WiFI network.

    0
  • A

    For those with Mikrotik routers.. I can confirm that Michal Rok's solution works..
    i.e. you need to initially set the mode to 'sta' (in /etc/config/wireless) to allow Omega2+ to associate with a configured AP. The default mode of '9' cannot seem to associate with the configured AP even though it is visible. The trick in Michael's solution is the switch the mode to '9' as the last step in the boot process, in order to get an IP address.

    Stupid.. but works. Not a good start to the Omega2+ journey!

    0 S 1 Reply
  • S

    I'm just dusting these things off after awhile and I'm hitting this issue. Nothing seems to work, not even the proposed changes above by @VLADIMIR VASHURIN . Did Onion just die off? What's going on here?

    0
  • S

    I just flashed the latest firmware on my Omega2+ manually to Ω-ware: 0.2.2 b202

    Still doesn't work.

    Garbage.

    0
  • S

    @Lazar-Demin It has been more than two(2) and a half years and this is still an issue. What are you guys doing? Wifi is a fundamental part of your platform and it is broken in a nuclear fashion.

    0
  • C

    @Stephen-Tunney I think you need to cool down. I have about 80 Omega2+ based IoT devices spread across APAC in both Home and office environments, all of which are connected to whatever WiFi their location provides. I have millions of JSON requests processed. WiFi connectivity is not even in my top 50 list of potential improvements.

    Since your thread is old and very long maybe it would be better to create a new thread with a new specific set of details of your problem so the onion community can try to assist you.

    Developing any device or software is a long series of disappointments and frustrations, it is better to channel your energy into engaging with the community in order to seek help to resolve your issues than it is to attack the guys who worked so hard to provide a device that we have all benefitted from.

    1
  • S

    Well, upgraded to the latest F/W 0.3.2 b230 and I still can't connect. I continue to get the following for infinity... no connectivity as a wifi client.

    [ 168.508792] Interface apcli0 link up! (WPA2PSK AES)
    [ 175.074039] Interface apcli0 link up! (WPA2PSK AES)
    [ 181.710379] Interface apcli0 link up! (WPA2PSK AES)
    [ 187.952151] Interface apcli0 link up! (WPA2PSK AES)
    [ 193.467633] Interface apcli0 link up! (WPA2PSK AES)
    [ 201.154177] Interface apcli0 link up! (WPA2PSK AES)
    [ 206.669601] Interface apcli0 link up! (WPA2PSK AES)
    [ 213.307635] Interface apcli0 link up! (WPA2PSK AES)
    [ 223.374207] Interface apcli0 link up! (WPA2PSK AES)
    [ 228.506452] Interface apcli0 link up! (WPA2PSK AES)
    [ 235.070035] Interface apcli0 link up! (WPA2PSK AES)
    [ 240.668915] Interface apcli0 link up! (WPA2PSK AES)

    0
  • C

    @Stephen-Tunney I prefer to go back to basics first so I know I haven't msade any changes that are causing my issues. First run firstboot -y then reboot your device so you have a stock standard setup. Once it hsd rebooted connect either via serial connection or connect via hostapd and SSH. Then run wifisetup and configure your wifi.

    What version of RouterOS are you running on your router?

    -1
  • S

    I done so many hard factory resets I've lost count, however...

    I ran the commands as you instructed, in the order you instructed and I am still getting the exact same results. All failure.

    I'm running a Ubiquity Unify AP-AC-Lite v.3.9.19.8123

    0 A 1 Reply
  • S

    Firmware 0.1.5 b130 works mind you on the exact same Omega2. After the firmware update to 0.2.2 or 0.3.2 the device no longer functions.

    Someone on the Onion team should be able to diff what was changed in the driver and see what broke this.

    0
  • S

    Upgraded my AP-AC-Lite to firmware version 4.0.42.10433 and it still does not work.

    0
  • C

    @Stephen-Tunney Coincidentally I am using the same Ubiquity Unify AP-AC-Lite at home to which I have 7 or 8 Omega2 connected. I'm also running 4.0.42.10433 firmware on these AP.

    My next step would be to open the UniFi controller and look in the Alerts page, for any clues. Also turn off Automatically Optimize Network in the Settings page, this has cause me no end of issues with some other WiFi clients.

    To troubleshoot further I turn on Enable Remote Syslog Server and Enable debug logging, both are on the Site settings page. You'll need a rsyslog server running so you can see the output, but the output is very informative to understand what the AP is doing with your connection. I expect you will find the cause in this logging.

    0 A Alexandr Didenko 2 Replies
  • S

    First off... I'm not sure why I have to jump through so many hoops. The firmware worked at one point, which I and many others have PROVEN. This is clearly a bug on Onion's part. Why make excused and point it at the router/AP?

    =========== End completely valid argument tangent ==============

    Results of diagnostics:
    I archived all alerts (I only had warnings about another client/MAC address that is not Onion-related)
    Nothing appears in the alerts.

    I turned on my device and I get the following after a clean factory reset (holding the reset button until the amber light is flashing). Run wifisetup and confirmed my password is entered correctly.
    Also confirmed that my date/time on the onion are the same as the AP.

    Some logs here for the Onion's MAC address from SysLog server:
    hostapd: ath1: STA 40:a3:6b:c0:9a:fc IEEE 802.11: disassociated

    : wevent[4788]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ath1: 40:a3:6b:c0:9a:fc / 4

    hostapd: ath1: STA 40:a3:6b:c0:9a:fc IEEE 802.11: deauthenticated due to local deauth request

    : wevent[4788]: wevent.ubnt_handle_custom_alert_sta_assoc(): EVT_AP_STA_ASSOC_TRACKER_DBG: event_id: 9 vap: ath1 sta_mac: 40:a3:6b:c0:9a:fc auth_ts: 2092.386283 auth_delta: 0 assoc_delta: 10000 wpa_auth_delta: -1 radius_auth_delta: -1 radius_auth_status: N/A ip_delta: -1 ip_assign_type: N/A disassoc_count: 0 auth_failures: 0 assoc_failures: 0 wpa_auth_failures: 2 ip_failures: 0 assoc_status: 0 arp_status: N/A dns_status: N/A event_type: failure

    hostapd: ath1: STA 40:a3:6b:c0:9a:fc IEEE 802.11: deauthenticated due to local deauth request

    Result of ifconfig from onion:
    apcli0 Link encap:Ethernet HWaddr 40:A3:6B:C0:9A:FC
    inet6 addr: fe80::42a3:6bff:fec0:9afc/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 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)
    br-wlan Link encap:Ethernet HWaddr 40:A3:6B:C0:9A:FB
    inet addr:192.168.3.1 Bcast:192.168.3.255 Mask:255.255.255.0
    inet6 addr: fe80::42a3:6bff:fec0:9afb/64 Scope:Link
    inet6 addr: fd1d:48c4:7633::1/60 Scope:Global
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:7205 (7.0 KiB)

    eth0 Link encap:Ethernet HWaddr 40:A3:6B:C0:9A:FD
    inet6 addr: fe80::42a3:6bff:fec0:9afd/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:11916 (11.6 KiB)
    Interrupt:5

    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:84 errors:0 dropped:0 overruns:0 frame:0
    TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:5412 (5.2 KiB) TX bytes:5412 (5.2 KiB)

    ra0 Link encap:Ethernet HWaddr 40:A3:6B:C0:9A:FB
    inet6 addr: fe80::42a3:6bff:fec0:9afb/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 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)
    Interrupt:6

    0
omega2+ 335 wifi 271 setup 47 wifi fails 31 connectivity 13
Log in to reply
 

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