Wifi unstable/unusable - disconnects every (single-digit) minutes

darklajid · January 10, 2017, 9:54am

Hey.

So, this became worse over time, but the Omnia was never stable for me. It replaced a WNDR8000 that was rock solid and I fear I have to go back to that for now. The problem: Since I don’t know how to fix the issue or drill down to the root cause, that’d make my (expensive…) Omnia a brick and paperweight. Any help would be appreciated.

Note: Devices in question are the same between original setup (OpenWRT, WNDR8000) and the Omnia. Same position for the router. Same channel. Same SSID. No, I do not have gazillion neighbors with Wifi nor did the few in range add a couple networks each: The spectrum is basically ~the same~. I’m trying to short-circuit the ‘Have you checked if a better channel is available’ replies.

When this issue occurs, the clients just stop working. I see nothing in the logs (logcat for Android devices, journal for my laptop), but all packets are silently dropped. The devices seem to think that they’re still associated, still claim to have an active lease for their address and happily throw packets at the default route - but that’s a black hole now.

On the router I see messages like the following (a snippet from a couple minutes ago). My laptop is *:b4 here, the only thing that seems weird are the repeated ‘deauthenticated due to local deauth request’ lines.

Thanks a lot for any pointers, ideas, suggestions.

2017-01-10T09:30:03+01:00 warning watchdog: Restarted nethist
2017-01-10T09:30:06+01:00 info hostapd: wlan1: STA 24:77:03:4f:3a:20 WPA: group key handshake completed (RSN)
2017-01-10T09:30:06+01:00 info hostapd: wlan1: STA be:75:0b:fe:1a:b4 WPA: group key handshake completed (RSN)
2017-01-10T09:30:06+01:00 info hostapd: wlan1: STA 70:18:8b:3c:06:63 WPA: group key handshake completed (RSN)
2017-01-10T09:30:10+01:00 info hostapd: wlan1: STA 00:0a:f5:c5:07:a4 WPA: group key handshake completed (RSN)
2017-01-10T09:30:15+01:00 info hostapd: wlan1: STA ac:22:0b:64:a9:1d IEEE 802.11: deauthenticated due to local deauth request
2017-01-10T09:30:15+01:00 info hostapd: wlan1: STA e8:50:8b:8e:05:7e IEEE 802.11: deauthenticated due to local deauth request
2017-01-10T09:30:30+01:00 info hostapd: wlan1: STA e8:50:8b:8e:05:7e IEEE 802.11: authenticated
2017-01-10T09:30:30+01:00 info hostapd: wlan1: STA e8:50:8b:8e:05:7e IEEE 802.11: associated (aid 1)
2017-01-10T09:30:30+01:00 info hostapd: wlan1: STA e8:50:8b:8e:05:7e RADIUS: starting accounting session 0A5F11C02A490E88
2017-01-10T09:30:30+01:00 info hostapd: wlan1: STA e8:50:8b:8e:05:7e WPA: pairwise key handshake completed (RSN)
2017-01-10T09:30:31+01:00 warning odhcpd[1708]: A default route is present but there is no public prefix on br-lan thus we don’t announce a default route!
2017-01-10T10:30:31+01:00 info dnsmasq-dhcp[2123]: DHCPREQUEST(br-lan) 192.168.42.124 e8:50:8b:8e:05:7e
2017-01-10T10:30:31+01:00 info dnsmasq-dhcp[2123]: DHCPACK(br-lan) 192.168.42.124 e8:50:8b:8e:05:7e android-30bf076ff26ceeff
2017-01-10T09:30:31+01:00 info hostapd: wlan1: STA ac:22:0b:64:a9:1d IEEE 802.11: authenticated
2017-01-10T09:30:31+01:00 info hostapd: wlan1: STA ac:22:0b:64:a9:1d IEEE 802.11: associated (aid 3)
2017-01-10T09:30:31+01:00 warning odhcpd[1708]: A default route is present but there is no public prefix on br-lan thus we don’t announce a default route!
2017-01-10T09:30:31+01:00 info hostapd: wlan1: STA ac:22:0b:64:a9:1d RADIUS: starting accounting session 60F990490E858659
2017-01-10T09:30:31+01:00 info hostapd: wlan1: STA ac:22:0b:64:a9:1d WPA: pairwise key handshake completed (RSN)
2017-01-10T10:30:31+01:00 info dnsmasq-dhcp[2123]: DHCPDISCOVER(br-lan) ac:22:0b:64:a9:1d
2017-01-10T10:30:31+01:00 info dnsmasq-dhcp[2123]: DHCPOFFER(br-lan) 192.168.42.24 ac:22:0b:64:a9:1d
2017-01-10T10:30:31+01:00 info dnsmasq-dhcp[2123]: DHCPREQUEST(br-lan) 192.168.42.24 ac:22:0b:64:a9:1d
2017-01-10T10:30:31+01:00 info dnsmasq-dhcp[2123]: DHCPACK(br-lan) 192.168.42.24 ac:22:0b:64:a9:1d android-4537edf0c834c252
2017-01-10T09:30:32+01:00 warning odhcpd[1708]: A default route is present but there is no public prefix on br-lan thus we don’t announce a default route!
2017-01-10T09:31:01+01:00 info /usr/sbin/cron[5007]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2017-01-10T09:32:01+01:00 info /usr/sbin/cron[5128]: (root) CMD (nethist_stats.lua)
2017-01-10T09:32:01+01:00 info /usr/sbin/cron[5129]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2017-01-10T09:32:10+01:00 warning odhcpd[1708]: A default route is present but there is no public prefix on br-lan thus we don’t announce a default route!
2017-01-10T09:33:01+01:00 info /usr/sbin/cron[5281]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2017-01-10T09:34:01+01:00 info /usr/sbin/cron[5403]: (root) CMD (nethist_stats.lua)
2017-01-10T09:34:01+01:00 info /usr/sbin/cron[5404]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2017-01-10T09:35:01+01:00 info /usr/sbin/cron[5621]: (root) CMD (/usr/bin/watchdog.sh)
2017-01-10T09:35:01+01:00 info /usr/sbin/cron[5623]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2017-01-10T09:35:01+01:00 info /usr/sbin/cron[5626]: (root) CMD (majordomo_db.sh downsize)
2017-01-10T09:35:01+01:00 info /usr/sbin/cron[5627]: (root) CMD ( /usr/bin/notifier)
2017-01-10T09:36:01+01:00 info /usr/sbin/cron[5903]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2017-01-10T09:36:01+01:00 info /usr/sbin/cron[5902]: (root) CMD (nethist_stats.lua)
2017-01-10T09:37:01+01:00 info /usr/sbin/cron[6104]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2017-01-10T09:38:01+01:00 info /usr/sbin/cron[6266]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2017-01-10T09:38:01+01:00 info /usr/sbin/cron[6267]: (root) CMD (nethist_stats.lua)
2017-01-10T09:39:01+01:00 info /usr/sbin/cron[6829]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2017-01-10T09:39:33+01:00 warning odhcpd[1708]: A default route is present but there is no public prefix on br-lan thus we don’t announce a default route!
2017-01-10T10:39:48+01:00 debug kernel: [1408086.094901] ath10k_pci 0000:02:00.0: ath10k_pci ATH10K_DBG_BUFFER:
2017-01-10T10:39:48+01:00 debug kernel: [1408086.094912] ath10k: [0000]: 05F2785F 10004C1D 004378F0 00000001 00000000 000000E2 05F27860 10004C1D
2017-01-10T10:39:48+01:00 debug kernel: [1408086.094917] ath10k: [0008]: 004378F0 00000001 00000006 000000E2 05F27860 14004C52 004378F0 000000E2
2017-01-10T10:39:48+01:00 debug kernel: [1408086.094921] ath10k: [0016]: 00000001 00000002 00004108
2017-01-10T10:39:48+01:00 debug kernel: [1408086.094925] ath10k_pci 0000:02:00.0: ATH10K_END
2017-01-10T09:40:01+01:00 info /usr/sbin/cron[7520]: (root) CMD (/usr/bin/watchdog.sh)
2017-01-10T09:40:01+01:00 info /usr/sbin/cron[7523]: (root) CMD (nethist_stats.lua)
2017-01-10T09:40:01+01:00 info /usr/sbin/cron[7524]: (root) CMD ( /usr/bin/notifier)
2017-01-10T09:40:01+01:00 info /usr/sbin/cron[7525]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2017-01-10T09:40:01+01:00 info /usr/sbin/cron[7526]: (root) CMD (majordomo_db.sh downsize)
2017-01-10T09:40:05+01:00 warning watchdog: Restarted nethist
2017-01-10T09:40:06+01:00 info hostapd: wlan1: STA 24:77:03:4f:3a:20 WPA: group key handshake completed (RSN)
2017-01-10T09:40:06+01:00 info hostapd: wlan1: STA 70:18:8b:3c:06:63 WPA: group key handshake completed (RSN)
2017-01-10T09:40:06+01:00 info hostapd: wlan1: STA be:75:0b:fe:1a:b4 WPA: group key handshake completed (RSN)
2017-01-10T09:40:15+01:00 info hostapd: wlan1: STA ac:22:0b:64:a9:1d IEEE 802.11: deauthenticated due to local deauth request
2017-01-10T09:40:15+01:00 info hostapd: wlan1: STA e8:50:8b:8e:05:7e IEEE 802.11: deauthenticated due to local deauth request
2017-01-10T09:40:15+01:00 info hostapd: wlan1: STA 00:0a:f5:c5:07:a4 IEEE 802.11: deauthenticated due to local deauth request
2017-01-10T09:40:28+01:00 info hostapd: wlan1: STA e8:50:8b:8e:05:7e IEEE 802.11: authenticated
2017-01-10T09:40:28+01:00 info hostapd: wlan1: STA e8:50:8b:8e:05:7e IEEE 802.11: associated (aid 1)
2017-01-10T09:40:28+01:00 info hostapd: wlan1: STA e8:50:8b:8e:05:7e IEEE 802.11: disassociated
2017-01-10T09:40:28+01:00 info hostapd: wlan1: STA e8:50:8b:8e:05:7e IEEE 802.11: authenticated
2017-01-10T10:40:28+01:00 info hostapd: Last message ‘wlan1: STA e8:50:8b:’ repeated 1 times, supressed by syslog-ng on turris
2017-01-10T09:40:28+01:00 info hostapd: wlan1: STA e8:50:8b:8e:05:7e IEEE 802.11: associated (aid 1)
2017-01-10T09:40:28+01:00 info hostapd: wlan1: STA e8:50:8b:8e:05:7e RADIUS: starting accounting session 46D0F0936163D490
2017-01-10T09:40:28+01:00 info hostapd: wlan1: STA e8:50:8b:8e:05:7e WPA: pairwise key handshake completed (RSN)
2017-01-10T10:40:29+01:00 info dnsmasq-dhcp[2123]: DHCPREQUEST(br-lan) 192.168.42.124 e8:50:8b:8e:05:7e
2017-01-10T10:40:29+01:00 info dnsmasq-dhcp[2123]: DHCPACK(br-lan) 192.168.42.124 e8:50:8b:8e:05:7e android-30bf076ff26ceeff
2017-01-10T09:40:29+01:00 warning odhcpd[1708]: A default route is present but there is no public prefix on br-lan thus we don’t announce a default route!
2017-01-10T10:40:33+01:00 warning odhcpd: Last message ‘A default route is p’ repeated 1 times, supressed by syslog-ng on turris
2017-01-10T09:40:33+01:00 info hostapd: wlan1: STA ac:22:0b:64:a9:1d IEEE 802.11: authenticated
2017-01-10T09:40:33+01:00 info hostapd: wlan1: STA ac:22:0b:64:a9:1d IEEE 802.11: associated (aid 2)
2017-01-10T09:40:33+01:00 info hostapd: wlan1: STA ac:22:0b:64:a9:1d RADIUS: starting accounting session ED511D6759891D13
2017-01-10T09:40:33+01:00 info hostapd: wlan1: STA ac:22:0b:64:a9:1d WPA: pairwise key handshake completed (RSN)
2017-01-10T10:40:33+01:00 info dnsmasq-dhcp[2123]: DHCPDISCOVER(br-lan) ac:22:0b:64:a9:1d
2017-01-10T10:40:33+01:00 info dnsmasq-dhcp[2123]: DHCPOFFER(br-lan) 192.168.42.24 ac:22:0b:64:a9:1d
2017-01-10T10:40:33+01:00 info dnsmasq-dhcp[2123]: DHCPREQUEST(br-lan) 192.168.42.24 ac:22:0b:64:a9:1d
2017-01-10T10:40:33+01:00 info dnsmasq-dhcp[2123]: DHCPACK(br-lan) 192.168.42.24 ac:22:0b:64:a9:1d android-4537edf0c834c252
2017-01-10T09:40:34+01:00 warning odhcpd[1708]: A default route is present but there is no public prefix on br-lan thus we don’t announce a default route!
2017-01-10T09:40:38+01:00 info hostapd: wlan1: STA 00:0a:f5:c5:07:a4 IEEE 802.11: authenticated
2017-01-10T09:40:38+01:00 info hostapd: wlan1: STA 00:0a:f5:c5:07:a4 IEEE 802.11: associated (aid 3)
2017-01-10T09:40:38+01:00 info hostapd: wlan1: STA 00:0a:f5:c5:07:a4 RADIUS: starting accounting session 4ACB8B464F7B7682
2017-01-10T09:40:38+01:00 info hostapd: wlan1: STA 00:0a:f5:c5:07:a4 WPA: pairwise key handshake completed (RSN)
2017-01-10T10:40:38+01:00 info dnsmasq-dhcp[2123]: DHCPREQUEST(br-lan) 192.168.42.72 00:0a:f5:c5:07:a4
2017-01-10T10:40:38+01:00 info dnsmasq-dhcp[2123]: DHCPACK(br-lan) 192.168.42.72 00:0a:f5:c5:07:a4
2017-01-10T09:41:01+01:00 info /usr/sbin/cron[8069]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2017-01-10T09:41:31+01:00 info hostapd: wlan1: STA be:75:0b:fe:1a:b4 IEEE 802.11: authenticated
2017-01-10T09:41:31+01:00 info hostapd: wlan1: STA be:75:0b:fe:1a:b4 IEEE 802.11: associated (aid 5)
2017-01-10T09:41:31+01:00 info hostapd: wlan1: STA be:75:0b:fe:1a:b4 RADIUS: starting accounting session 46DA2F15B608BA9C
2017-01-10T09:41:31+01:00 info hostapd: wlan1: STA be:75:0b:fe:1a:b4 WPA: pairwise key handshake completed (RSN)
2017-01-10T10:41:31+01:00 info dnsmasq-dhcp[2123]: DHCPREQUEST(br-lan) 192.168.42.202 be:75:0b:fe:1a:b4
2017-01-10T10:41:31+01:00 info dnsmasq-dhcp[2123]: DHCPACK(br-lan) 192.168.42.202 be:75:0b:fe:1a:b4 tislaptop2016
2017-01-10T09:41:32+01:00 warning odhcpd[1708]: A default route is present but there is no public prefix on br-lan thus we don’t announce a default route!
2017-01-10T09:41:33+01:00 warning odhcpd[1708]: DHCPV6 CONFIRM IA_NA from 0004a7f104eecf7d4cb8eb974613cbfbf1c8 on br-lan: not on-link fd7e:3ea4:37f7::69c/128
2017-01-10T09:41:33+01:00 warning odhcpd[1708]: DHCPV6 SOLICIT IA_NA from 0004a7f104eecf7d4cb8eb974613cbfbf1c8 on br-lan: ok fd7e:3ea4:37f7::69c/128
2017-01-10T09:41:34+01:00 warning odhcpd[1708]: DHCPV6 REQUEST IA_NA from 0004a7f104eecf7d4cb8eb974613cbfbf1c8 on br-lan: ok fd7e:3ea4:37f7::69c/128

ubermutant · January 10, 2017, 9:56am

what firmware are you using ?
SSID separate for 2.4 and 5GHz?
which frequency your devices use?

I would suggest to upgrade to latest firmware in the first run.

and please do some search on the forum, there are a bunch of similar topics, maybe some might help you.

darklajid · January 10, 2017, 10:14am

Firmware: I … don’t know. Turris OS version 3.4 / Kernel 4.4.38-efe609c5e5f25db4116d69128330872c-1
That said, I have auto-updates enabled and kinda expect that thing to be ‘current’.

Yes, SSIDs are separate (and different) for 2.5/5Ghz.
Channel is 11.

I did search the forum, but haven’t found anything helpful quite yet - the only other post is full of ‘Maybe it is a microwave oven’ stuff or people consistently jumping in with ‘maybe too many interference sources’ every 4th post
I’m not trying to spam the forum, but I tried to make the focus of this problem (not 5Ghz, not interference, location of the router, clients, neighbors, phase of the moon) clear in the first couple lines. Wifi problem threads tend to read like voodoo recipes a lot…

SQBI · January 10, 2017, 10:18am

Version 3.5 will have another fixes for wifi.

darklajid · January 10, 2017, 10:57am

Any due date (is that on some sort of schedule like Firefox, Rust etc.) or is this more of the “It’s done when it’s done” variety?

SQBI · January 10, 2017, 11:07am

Should be available soon in stable branch, there’s no exact timeline widely known. You can switch to the master nightly branch to get it now, if you can’t wait for a stable release.

ubermutant · January 10, 2017, 2:37pm

https://www.turris.cz/doc/en/howto/test_branches
here is the manual entry for changing branch.

yes 3.5 is the latest firmware in master nightly.

Pepe · January 10, 2017, 3:05pm

Yes, there is.
TurrisOS 3.5 should be released this week.

SQBI · January 10, 2017, 3:34pm

Not widely, I can’t see it mentioned here by the team on this board.

tonyquan · January 10, 2017, 5:04pm

definitely looking forward to 3.5. been testing the master branch to get a preview, wifi is definitely much better there (have had no issues with it) It looks like Tomas mentioned in https://forum.test.turris.cz/t/swich-ports-offline-if-plugged-during-boot/1611/62 that the issue where some Ethernet devices don’t work at router reboot or power up is planned to be fixed there as well, which is another of the really nagging issues.

Pepe · January 10, 2017, 5:31pm

It is. Community manager said it in Czech section and also there is mention it on Twitter (again in Czech).
And I also think that one from Turris team said it to me on IRC.

SQBI · January 10, 2017, 6:39pm

In Czech? So, still not widely mentioned