Hi. First things first - huge thanks for keeping this alive!
My good old RT-N66U was running 374.43_44EAj9527 for quite a while but recently I noticed it drops packages over WiFi between the router and the clients from time to time, at least on 5GHz (I wasn't monitoring 2.4GHz closely as my main work machines are connected to 5GHz). It's kind of random, not in similar time periods. Sometimes it's a single package, sometimes it's a few, so it can break the streaming of internet radios, hang my work VPN connection, or disturb the feed on video calls. I monitored the pings to the router (simply 192.168.1.1) and to Google's DNS server (8.8.8.8) with PingPlotter.
First thing I did - I replaced the power supply with over two times more powerful one, as I read some threads saying that the original power supply may deteriorate over time (mine is ~7 years old) and cause such effects. Unfortunately - that didn't help.
So I've just flashed the development firmware: 3.0.0.4.374.43_45D5j9527
This apparently didn't help either, as I've just noticed another lost pings. I checked the logs and couldn't find anything suspicious except:
Code:
Sep 7 20:30:15 (none) cron.err crond[402]: time disparity of 5094390 minutes detected
but I presume it's also normal as the router updated the time from the NTP after the reboot after flashing the firmware. I pasted the full log (after a bit of anonymization
) at:
https://pastebin.com/49Ymyp9F
FYI, otherwise the build looks stable after 2 hours of testing.
But any idea what might cause those lost packages? I don't really have the need to buy a new router, if not that...
EDIT01 after a day: I've just got a huge package drop lasting over 30 seconds (from 10:08:43 to 10:09:14). This surely came in the worst possible moment, killing my video conference call
I checked the router logs but I can't see nothing else but plenty DHCP-related entries around that time (I'm not sure though how well the time of my PC and the router are synced), like those (I manually replaced last bytes of MAC with xx:xx):
Code:
Sep 9 10:06:54 (none) user.info kernel: device br0 entered promiscuous mode
Sep 9 10:06:57 (none) daemon.info dnsmasq-dhcp[651]: DHCPDISCOVER(br0) ac:9e:17:e9:xx:xx
Sep 9 10:06:57 (none) daemon.info dnsmasq-dhcp[651]: DHCPOFFER(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:06:57 (none) daemon.info dnsmasq-dhcp[651]: DHCPREQUEST(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:06:57 (none) daemon.info dnsmasq-dhcp[651]: DHCPACK(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:07:09 (none) user.info kernel: device br0 left promiscuous mode
Sep 9 10:07:10 (none) daemon.info dnsmasq-dhcp[651]: DHCPDISCOVER(br0) ac:9e:17:e9:xx:xx
Sep 9 10:07:10 (none) daemon.info dnsmasq-dhcp[651]: DHCPOFFER(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:07:10 (none) daemon.info dnsmasq-dhcp[651]: DHCPREQUEST(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:07:10 (none) daemon.info dnsmasq-dhcp[651]: DHCPACK(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:07:12 (none) user.info kernel: device br0 entered promiscuous mode
Sep 9 10:07:15 (none) daemon.info dnsmasq-dhcp[651]: DHCPRELEASE(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:07:44 (none) daemon.info dnsmasq-dhcp[651]: DHCPDISCOVER(br0) ac:9e:17:e9:xx:xx
Sep 9 10:07:44 (none) daemon.info dnsmasq-dhcp[651]: DHCPOFFER(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:07:44 (none) daemon.info dnsmasq-dhcp[651]: DHCPDISCOVER(br0) ac:9e:17:e9:xx:xx
Sep 9 10:07:44 (none) daemon.info dnsmasq-dhcp[651]: DHCPOFFER(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:07:44 (none) daemon.info dnsmasq-dhcp[651]: DHCPREQUEST(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:07:44 (none) daemon.info dnsmasq-dhcp[651]: DHCPACK(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:07:55 (none) daemon.info dnsmasq-dhcp[651]: DHCPDISCOVER(br0) ac:9e:17:e9:xx:xx
Sep 9 10:07:55 (none) daemon.info dnsmasq-dhcp[651]: DHCPOFFER(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:07:55 (none) daemon.info dnsmasq-dhcp[651]: DHCPREQUEST(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:07:55 (none) daemon.info dnsmasq-dhcp[651]: DHCPACK(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:08:16 (none) daemon.info dnsmasq-dhcp[651]: DHCPDISCOVER(br0) ac:9e:17:e9:xx:xx
Sep 9 10:08:16 (none) daemon.info dnsmasq-dhcp[651]: DHCPOFFER(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:08:16 (none) daemon.info dnsmasq-dhcp[651]: DHCPREQUEST(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:08:16 (none) daemon.info dnsmasq-dhcp[651]: DHCPACK(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:08:41 (none) daemon.info dnsmasq-dhcp[651]: DHCPDISCOVER(br0) ac:9e:17:e9:xx:xx
Sep 9 10:08:41 (none) daemon.info dnsmasq-dhcp[651]: DHCPOFFER(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:08:41 (none) daemon.info dnsmasq-dhcp[651]: DHCPREQUEST(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:08:41 (none) daemon.info dnsmasq-dhcp[651]: DHCPACK(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:10:03 (none) daemon.info dnsmasq-dhcp[651]: DHCPDISCOVER(br0) ac:9e:17:e9:xx:xx
Sep 9 10:10:03 (none) daemon.info dnsmasq-dhcp[651]: DHCPOFFER(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:10:04 (none) daemon.info dnsmasq-dhcp[651]: DHCPREQUEST(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:10:04 (none) daemon.info dnsmasq-dhcp[651]: DHCPACK(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:10:13 (none) daemon.info dnsmasq-dhcp[651]: DHCPDISCOVER(br0) ac:9e:17:e9:xx:xx
Sep 9 10:10:13 (none) daemon.info dnsmasq-dhcp[651]: DHCPOFFER(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:10:13 (none) daemon.info dnsmasq-dhcp[651]: DHCPREQUEST(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:10:13 (none) daemon.info dnsmasq-dhcp[651]: DHCPACK(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:10:21 (none) daemon.info dnsmasq-dhcp[651]: DHCPRELEASE(br0) 192.168.1.56 ac:9e:17:e9:xx:xx
Sep 9 10:12:02 (none) user.info kernel: device br0 left promiscuous mode
Is there a way to log/check what actually happened causing packages drop?
Why there's so many DHCP-related activity for a single node spanning over 5 minutes in the logs above? I see similar logs for other nodes in my network, too.
EDIT02:
I don't know if that matters, but that node 192.168.1.56 is an old RT-N18U working as a Media Bridge. Can this cause issues?
EDIT03:
I realized there's over 4 minutes difference in clocks between my PC and RT-N66U. PC has correct time while the router is lagging behind. Surprising, as the router settings seem correct: