So I've been learning a lot from searching. I am not the most knowledgeable when it comes to routers and networks and was hoping this was like a simple install the firmware and set up SSID + passwords but it wasn't and that is fine.
My PS4 disconnected once yesterday and my Oneplus 6T disconnected a few times today. The things I tried so far are -
etc/config/wireless and setting option disassoc_low_ack '0' for both SSID. And also setting DHCP lease time to 7d
However I still see a lot of weird stuff in the system logs that I am unsure if it is normal. Is this stuff normal to see? It is a home network and there are many devices I need to set up like WiFi sockets and lightbulbs, Alexas, etc that it would be extra annoying if they had to be reconnected often
Sun Dec 29 13:36:48 2019 kern.debug kernel: [74570.085996] ieee80211 phy1: staid 6 deleted
Sun Dec 29 13:36:49 2019 daemon.info hostapd: wlan1: STA 4c:11:ae:16:ef:ea IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Dec 29 13:36:50 2019 daemon.info hostapd: wlan1: STA 4c:11:ae:16:ef:ea IEEE 802.11: associated (aid 6)
Sun Dec 29 13:36:51 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 4c:11:ae:16:ef:ea
Sun Dec 29 13:36:51 2019 daemon.info hostapd: wlan1: STA 4c:11:ae:16:ef:ea WPA: pairwise key handshake completed (RSN)
Sun Dec 29 13:37:05 2019 daemon.info hostapd: wlan1: STA dc:ef:ca:4a:70:a0 IEEE 802.11: associated (aid 8)
Sun Dec 29 13:37:05 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:ef:ca:4a:70:a0
Sun Dec 29 13:37:05 2019 daemon.info hostapd: wlan1: STA dc:ef:ca:4a:70:a0 WPA: pairwise key handshake completed (RSN)
Sun Dec 29 13:37:06 2019 daemon.info dnsmasq-dhcp[5710]: DHCPREQUEST(br-lan) 192.168.1.233 dc:ef:ca:4a:70:a0
Sun Dec 29 13:37:06 2019 daemon.info dnsmasq-dhcp[5710]: DHCPACK(br-lan) 192.168.1.233 dc:ef:ca:4a:70:a0 Galaxy-S8
Sun Dec 29 13:37:06 2019 daemon.info hostapd: wlan1: STA 4c:11:ae:16:ef:ea IEEE 802.11: authenticated
Sun Dec 29 13:37:06 2019 daemon.info hostapd: wlan1: STA dc:ef:ca:4a:70:a0 IEEE 802.11: authenticated
Sun Dec 29 13:37:12 2019 kern.debug kernel: [74593.615912] ieee80211 phy1: staid 5 deleted
Sun Dec 29 13:37:12 2019 daemon.info hostapd: wlan1: STA 60:01:94:53:77:c4 IEEE 802.11: associated (aid 5)
Sun Dec 29 13:37:12 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 60:01:94:53:77:c4
Sun Dec 29 13:37:12 2019 daemon.info hostapd: wlan1: STA 60:01:94:53:77:c4 WPA: pairwise key handshake completed (RSN)
Sun Dec 29 13:37:14 2019 daemon.info hostapd: wlan1: STA dc:ef:ca:2e:eb:09 IEEE 802.11: associated (aid 9)
Sun Dec 29 13:37:15 2019 daemon.info hostapd: wlan1: STA 60:01:94:53:77:c4 IEEE 802.11: authenticated
Sun Dec 29 13:37:15 2019 daemon.info hostapd: wlan1: STA dc:ef:ca:2e:eb:09 IEEE 802.11: authenticated
Sun Dec 29 13:37:16 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED dc:ef:ca:2e:eb:09
Sun Dec 29 13:37:16 2019 daemon.info hostapd: wlan1: STA dc:ef:ca:2e:eb:09 WPA: pairwise key handshake completed (RSN)
Sun Dec 29 13:37:16 2019 daemon.info dnsmasq-dhcp[5710]: DHCPDISCOVER(br-lan) dc:ef:ca:2e:eb:09
Sun Dec 29 13:37:16 2019 daemon.info dnsmasq-dhcp[5710]: DHCPOFFER(br-lan) 192.168.1.169 dc:ef:ca:2e:eb:09
Sun Dec 29 13:37:16 2019 daemon.info dnsmasq-dhcp[5710]: DHCPREQUEST(br-lan) 192.168.1.169 dc:ef:ca:2e:eb:09
Sun Dec 29 13:37:16 2019 daemon.info dnsmasq-dhcp[5710]: DHCPACK(br-lan) 192.168.1.169 dc:ef:ca:2e:eb:09 Galaxy-S8
Sun Dec 29 13:37:50 2019 kern.debug kernel: [74631.705999] ieee80211 phy1: staid 6 deleted
Sun Dec 29 13:37:50 2019 daemon.info hostapd: wlan1: STA 4c:11:ae:16:ef:ea IEEE 802.11: associated (aid 6)
Sun Dec 29 13:37:50 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 4c:11:ae:16:ef:ea
Sun Dec 29 13:37:50 2019 daemon.info hostapd: wlan1: STA 4c:11:ae:16:ef:ea WPA: pairwise key handshake completed (RSN)
It isn't surprising that mobile devices (smartphones, tablets, etc.) go into deep sleep power states regularly, disconnecting from wireless (WLAN is requiring considerable amounts of power, so unless you explicitly configure your phone to remain continuously connected (e.g. for SIP connectivity), it will take any opportunity to drop offline regularly). Similar behaviour would be observed for devices getting out of range with the AP.
That's true. But it happened while it was in my hands using it, that's why I was curious about it. Since it was a fresh OpenWRT install besides SSID+Password
If you want to monitor this closer, you need to rule out the client's powersaving features as well as possible. E.g. by disabling mobile data (so WLAN is the only route to the internet), and keeping the phone awake (actively working on it, ideally configuring a permanent SIP account, which forces it to stay connected) - or you just wait and observe if you actually encounter any real problems.
what device are you using for the access point. I have found the Linksys WRT32X and wrt1900 drivers seem to cause this. I'm looking forward to dumping them, though the wired performance is quite good. I'm going to switch to TPlink Omada APs in their next incarnation with WIFI 6 I think.
I understand the whole thing of monitoring, but basically my devices never changed but my router firmware did. And my phone will just randomly disconnect off WiFi and not reconnect, even while in the same room. It can't possibly be the phones problem if it never did it until right after installing OpenWRT.
I am using the Linksys WRT 3200ACM. I like the performance of OpenWRT but I never had a problem with stock either. Though this disconnecting without reconnecting is inconvenient
I've searched around and saw people on a DDWRT forum saying to make sure auto channel isn't selected, which it isn't. But I downloaded a WiFi analyzer app and used it, it is showing 1/10 stars for every single 2.4Ghz channels. But my 5Ghz are all 10/10. Maybe this has to do with why I am getting disconnects? I can't see a reason Why it would be 1/10 performance, I am 10ft away in the same room. Is there some weird default setting causing it?
interference from neighbors. I've seen big apartment buildings where there were hundreds of APs in 2.4 GHz and they generally were all strewn about on different channels so basically maximal interference.
I've been trying the 5Ghz band to see if the WiFi analyzer app is showing good info and I haven't had a single disconnection the 5Ghz in over 24hrs even though I would experience many on 2.4Ghz. But the 2.4Ghz disconnects have even happened in the same room, 10 feet from the router. And it is a house so it would be pretty hard to have interference from anyone 30+ feet away through multiple walls for the closest possible routers. The good news is the 5Ghz seems stronger than ever, reaching rooms with a stronger signal than it could have done on stock firmware. Maybe that has something to do with the 2.4GHz signal? But I always thought they were supposed to work fine together and not conflict so idk
It seemed like on DD-WRT they had that problem and fixed it. Then some still have 2.4GHz problems, some 5GHz, some both. It almost seems like there is some hardware problem we can't see. Can't really complain since Linksys gave me a free velop setup from when they updated everyone's router with bad firmware, but I guess it isn't something to be worried about trying to fix.
