Intermittent wifi outages


#1

Hi!

I am a happy user of the Omnia Turris router. It’s being kept up to date with weekly updates. Last reboot happened about 2 days ago, so the machine should have the latest upstream software.

It seems there are problems with the wireless device on the Omnia. Every once in a while (it feels like every 15-30 minutes), the network goes down completely: I can’t ping the router over wifi at all anymore (100% packet loss). While the wifi still looks like it’s up, if I try to reconnect, it fails:

Jun  7 10:15:52 curie wpa_supplicant[24204]: wlp1s0: SME: Trying to authenticate with 04:f0:21:23:2d:7d (SSID='CrapN6' freq=2437 MHz)
Jun  7 10:15:52 curie kernel: [137742.262864] wlp1s0: authenticate with 04:f0:21:23:2d:7d
Jun  7 10:15:52 curie kernel: [137742.271672] wlp1s0: send auth to 04:f0:21:23:2d:7d (try 1/3)
Jun  7 10:15:52 curie kernel: [137742.273917] wlp1s0: authenticated
Jun  7 10:15:52 curie NetworkManager[24202]: <info>  [1496844952.4091] device (wlp1s0): supplicant interface state: disconnected -> authenticating
Jun  7 10:15:53 curie kernel: [137742.885723] iwlwifi 0000:01:00.0: No association and the time event is over already...
Jun  7 10:15:53 curie kernel: [137742.885769] wlp1s0: Connection to AP 04:f0:21:23:2d:7d lost
Jun  7 10:15:57 curie kernel: [137747.271941] wlp1s0: aborting authentication with 04:f0:21:23:2d:7d by local choice (Reason: 3=DEAUTH_LEAVING)
Jun  7 10:15:57 curie NetworkManager[24202]: <info>  [1496844957.4105] device (wlp1s0): supplicant interface state: authenticating -> disconnected
Jun  7 10:15:57 curie NetworkManager[24202]: <info>  [1496844957.5106] device (wlp1s0): supplicant interface state: disconnected -> scanning
Jun  7 10:15:57 curie wpa_supplicant[24204]: wlp1s0: SME: Trying to authenticate with 04:f0:21:24:11:81 (SSID='CrapN6' freq=5180 MHz)
Jun  7 10:15:57 curie kernel: [137747.398330] wlp1s0: authenticate with 04:f0:21:24:11:81
Jun  7 10:15:57 curie kernel: [137747.407211] wlp1s0: send auth to 04:f0:21:24:11:81 (try 1/3)
Jun  7 10:15:57 curie NetworkManager[24202]: <info>  [1496844957.5351] device (wlp1s0): supplicant interface state: scanning -> authenticating
Jun  7 10:15:57 curie kernel: [137747.408234] wlp1s0: authenticated
Jun  7 10:15:58 curie kernel: [137748.021600] iwlwifi 0000:01:00.0: No association and the time event is over already...
Jun  7 10:15:58 curie kernel: [137748.021618] wlp1s0: Connection to AP 04:f0:21:24:11:81 lost
Jun  7 10:16:02 curie kernel: [137752.411306] wlp1s0: aborting authentication with 04:f0:21:24:11:81 by local choice (Reason: 3=DEAUTH_LEAVING)
Jun  7 10:16:02 curie NetworkManager[24202]: <info>  [1496844962.5475] device (wlp1s0): supplicant interface state: authenticating -> disconnected
Jun  7 10:16:02 curie NetworkManager[24202]: <info>  [1496844962.6478] device (wlp1s0): supplicant interface state: disconnected -> scanning
Jun  7 10:16:04 curie wpa_supplicant[24204]: wlp1s0: SME: Trying to authenticate with 04:f0:21:23:2d:7d (SSID='CrapN6' freq=2437 MHz)
Jun  7 10:16:04 curie kernel: [137753.945171] wlp1s0: authenticate with 04:f0:21:23:2d:7d
Jun  7 10:16:04 curie NetworkManager[24202]: <info>  [1496844964.0814] device (wlp1s0): supplicant interface state: scanning -> authenticating

…etc. After a few seconds, wifi kicks back in and networks goes back to normal. I haven’t found any significant things in the logs on the router or my workstation that indicate a hardware problem (nothing in dmesg and /var/log/messages are normal: it just looks like the client disconnects and reconnects back).

I was previously using a secondary wifi access point in bridge mode and I was usually connected to the network with a wire, only using the wifi infrequently through my phone or laptop from time to time. So it’s possible the problem has been there for a long time without me noticing.

Also, I have received and setup the router before the advisory regarding the antenna sockets was issued, all the way back then. This means when I screwed in one of antennas, it made the antenna socket rotate and, unfortunately, I held the plastic board to keep it from rotating, so I’m worried I may have damaged one of the antennas.

How can I diagnose this further? Anyone else experienced such issues?

Thanks!


#2

I have just made a change to make sure the ESSID is different between the 5GHz and 2.4GHz APs. I had noticed I was switching between the two APs when reconnecting, so I wonder if that could be an issue.


#3

It sure looks like this solved the problem for me, sorry for the noise!


closed #4