1. Home
  2. Omega Talk
  3. Omega 2+ Wifi unstable and slow

Omega 2+ Wifi unstable and slow

  • Alexy Torres

    Hello everyone,

    I've taken my omega2+ out of the shelf and I'm having a weird issue now.
    I am able to connect to Wifi, but once connected the connection is really unstable, will still be connected to my wifi router but won't be able to contact any server.

    Sometimes I have 20s were everything is fine (usually just after connecting to the rooter) and then nothing. I can't even access the web based interface. Serial is working fine, here is what I got when I try to ping google.fr:

    root@Omega-4305:/# ping google.fr
PING google.fr (172.217.13.163): 56 data bytes
64 bytes from 172.217.13.163: seq=0 ttl=55 time=37.901 ms
64 bytes from 172.217.13.163: seq=1 ttl=55 time=49.629 ms
64 bytes from 172.217.13.163: seq=2 ttl=55 time=115.104 ms
64 bytes from 172.217.13.163: seq=5 ttl=55 time=25.481 ms
64 bytes from 172.217.13.163: seq=4 ttl=55 time=1025.922 ms
64 bytes from 172.217.13.163: seq=12 ttl=55 time=1060.664 ms
64 bytes from 172.217.13.163: seq=13 ttl=55 time=62.044 ms
64 bytes from 172.217.13.163: seq=14 ttl=55 time=79.197 ms
64 bytes from 172.217.13.163: seq=15 ttl=55 time=41.938 ms
64 bytes from 172.217.13.163: seq=16 ttl=55 time=94.022 ms
64 bytes from 172.217.13.163: seq=17 ttl=55 time=1590.211 ms
64 bytes from 172.217.13.163: seq=19 ttl=55 time=65.239 ms
64 bytes from 172.217.13.163: seq=22 ttl=55 time=2785.021 ms
64 bytes from 172.217.13.163: seq=29 ttl=55 time=94.102 ms
64 bytes from 172.217.13.163: seq=28 ttl=55 time=1096.048 ms
^C
--- google.fr ping statistics ---
31 packets transmitted, 15 packets received, 51% packet loss
round-trip min/avg/max = 25.481/548.168/2785.021 ms

    And here I'm lucky when I dont get a

    ping: bad address 'google.fr'

    All other devices on this network work perfectly fine. Do you have any idea? I was using 0.2.2 version of the OS and updated to the last one but the issue is still here.

    Thanks!

    0 Douglas Kryder 1 Reply
  • Douglas Kryder

    @Alexy-Torres it might be better to ping the local router if you want to pin bad network traffic on the omega2+. reason being without the hops being shown on the ping to google it's a leap of faith to accept that the onion is the bad hop.

    1
  • Alexy Torres

    You are completly right ahah,
    here are the result when I ping my router:

    root@Omega-4305:~/DomoHome/OmegaWebServer# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: seq=3 ttl=64 time=2140.563 ms
64 bytes from 192.168.0.1: seq=4 ttl=64 time=1141.855 ms
64 bytes from 192.168.0.1: seq=6 ttl=64 time=98.246 ms
64 bytes from 192.168.0.1: seq=7 ttl=64 time=30.148 ms
64 bytes from 192.168.0.1: seq=8 ttl=64 time=30.203 ms
64 bytes from 192.168.0.1: seq=9 ttl=64 time=25.562 ms
64 bytes from 192.168.0.1: seq=10 ttl=64 time=13.283 ms
64 bytes from 192.168.0.1: seq=11 ttl=64 time=28.967 ms
64 bytes from 192.168.0.1: seq=12 ttl=64 time=20.664 ms
64 bytes from 192.168.0.1: seq=13 ttl=64 time=24.341 ms
64 bytes from 192.168.0.1: seq=14 ttl=64 time=32.039 ms
64 bytes from 192.168.0.1: seq=15 ttl=64 time=39.736 ms
64 bytes from 192.168.0.1: seq=16 ttl=64 time=23.557 ms
64 bytes from 192.168.0.1: seq=17 ttl=64 time=35.133 ms
64 bytes from 192.168.0.1: seq=18 ttl=64 time=18.750 ms
64 bytes from 192.168.0.1: seq=19 ttl=64 time=27.330 ms
64 bytes from 192.168.0.1: seq=20 ttl=64 time=14.212 ms
64 bytes from 192.168.0.1: seq=21 ttl=64 time=29.913 ms
64 bytes from 192.168.0.1: seq=22 ttl=64 time=33.677 ms
64 bytes from 192.168.0.1: seq=23 ttl=64 time=18.044 ms
64 bytes from 192.168.0.1: seq=25 ttl=64 time=1101.344 ms
64 bytes from 192.168.0.1: seq=27 ttl=64 time=148.011 ms
^C
--- 192.168.0.1 ping statistics ---
31 packets transmitted, 22 packets received, 29% packet loss
round-trip min/avg/max = 13.283/230.708/2140.563 ms

    I'm 1 metter away from the wifi router

    0
  • C

    @Alexy-Torres @Douglas-Kryder I would be interested to know what your wifi configuration is.

    I would also run another test. Place your Omega next to the wifi router you are connected to and try ping again. I have found that some of my Omega2+ seem to be effected by some interference, I think it is my B&O TV but not sure. When I move the Omega away from that TV they work just fine. I can take the same Omega to my office and it works perfectly anywhere in my office. Not sure if this is your issue but I think it is worth looking at.

    0 Alexy Torres 1 Reply
  • Alexy Torres

    @crispyoz Thanks for the reply!

    Do you have a specific command in mind? I also put the omega right next to the router and get the same result. I also tried connecting the omega to my cell phone AP and get the same issue.

    Here are my wifi settings:

    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-4305'

config wifi-iface 'sta'
        option device 'radio0'
        option mode 'sta'
        option ifname 'apcli0'
        option encryption 'psk2'
        option network 'wwan'
        option disabled '0'
        option ssid 'Torres 2.4GHz'
        option key 'REDACTED'
        option led 'omega2p:blue:wifi'

config wifi-config
        option ssid 'Torres 2.4GHz'
        option encryption 'psk2'
        option key 'REDACTED'

config wifi-config
        option ssid 'AlexyAPS'
        option encryption 'psk2'
        option key 'REDACTED'
    0
  • C

    @Alexy-Torres That looks pretty normal. My first thought is that it seems some users have had issues with their wifi due to some differences with US configuration. Try removing "option country ''US"

    0 Alexy Torres 1 Reply
  • Alexy Torres

    @crispyoz I tried that but unfortunately I still have the same results. If that could help someone, the issue appeared like 3 days ago and wasn't present 1 week ago.

    0
  • C

    @Alexy-Torres that is interesting. It suggests something has changed. If this happened to me I would do as follows:

    1. Factory reset
    2. Use wifisetup to configure wifi
    3. oupdate
    0 Alexy Torres 1 Reply
  • Alexy Torres

    @crispyoz I already did. At first I factory reset the omega, then updated the firmware (that was a pain in the ass with this connection issue ahah) and nothing changed.

    0
  • C

    @Alexy-Torres How are you powering your Omega?

    0 Alexy Torres 1 Reply
  • Alexy Torres

    @crispyoz Through the dock, plugged by USB on my computer, I also tried to plug it to a usb charger directly

    0
  • Alexy Torres

    Just an update, I used the omega today and everything was fine, I don't know what happened...

    0 L 1 Reply
  • L

    @Alexy-Torres Something I noticed is that the AP mode is using the same channel as my home router so big and random interference might happen from time to time.

    Can you check with any wifi scanner if the AP wifi or your Onion is using the same channel as your home router?

    Regards

    0
  • P

    Any further updates? This always happens to me from time to time. Sometimes it just resolves itself after I do a full power off and on.

    0
  • R

    Hi, and sorry about rebreathing old topic alive.

    I finally got my Omega2+ with Power Doc through 1st Time Setup using the Command line (or somewhat completed it) and got WiFi connection to work to the outside world. Then I went and updated firmware and now I got WiFi connection unstable and slow. šŸ˜ž

    I have owned Omega2+ from the crowdfunding times but haven't got earlier just time to really try it out. Years back I got tired on not getting WiFi to work and didn't have time to solve the problem.

    So what I recently did:

    1. I struggled several days in order to get WiFi connection to work, finally this one solved the WiFi connection problem to WiFi router:
      https://community.onion.io/topic/1495/can-t-connect-to-hidden-ssid/9
      (Apparently the trick was to set ipv6 '0' in "network" and/or it was related to setting Bssid in "wireless". I'm not sure since my last trial included both additions.)
    2. After 1st Time Setup I decided to update my firmware, since it was very old, before continuing with anything else
    3. After files were downloaded there was a message on rebooting (can't recall anymore exactly what it was) but rebooting did not occurred automatically in 15-20 minutes and I did power reset
    4. Omega2+ boots up but now the WiFi is very unstable I can't get practically anything to work. FW is updated to 0.3.2 b233

    Current status:

    • No connectivity via my WiFi network, only direct connection working but it's unstable and slow
    • Omega-xxxx.local not working now, I need to go directly via 192.168.3.1
    • My edits on "wireless" and "network" disappeared instead there is new and totally different setups. Files are a lot different where I originally started from to work on functional WiFi connection
    • Some of the commands are missing like aps and ia
    • wifisetup doesn't lead to anywhere, it asks the things, restarts wifimanager but not nothing changes (as it was originally also)
    • Manual editing wireless and network is practically impossible since connection is slow and drops out every now and then (so vi-editor at least exists)
    • Factory reset nor power on/off's do not seem to affect in anyway

    I wonder if I own a brick now. Any advices for a beginner?

    0
  • C

    @Rotenone Can you post your /etc/config/wireless file so we can look.

    I suspect you may have a noisy channel, try changing the channel to a fixed channel, try channel 1, 6 or 11, if one doesn't help try another of these.

    To do this, open /etc/config/wireless find the section "config wifi-device 'radio0'" usually at the top, change the option "option channel 'auto'" to one of these channels, I find 6 is generally a good option.

    Also you can comment out the option " option country 'US'" and see if this helps you.

    0
  • R

    @crispyoz I will make capture when I get back to home today but do notice that WiFi worked like a charm when I did updates according to this:
    https://community.onion.io/topic/1495/can-t-connect-to-hidden-ssid/9 so I doubt noisy channel. WiFi network analyzer doesn't show much disturbance on the channel I'm using the home WiFi. Closest neighbours are 30 meters away.

    Yes, 'US' removal has been the first thing I have done. That was one of the edits that I managed to make in time when I had connection up for short period. What I will make when get back to home is that I will make edits ready and try to copy-paste them at once when I get connection up and running for short period. I wonder why I didn't think of that yesterday.

    Upon unstable WiFi there is also problem with these vanished commands. Like aps, ia and nr would be nice to have.

    0 C 1 Reply
  • C

    @Rotenone Don't you have a power dock or mini dock so you can connect to terminal?

    Please run wifisetup -v debug then post /tmp/wifidebug.log

    0
wifi 271 connection 16 wifi issue 5 unstable 3 lost packet 1
Log in to reply
 

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