I see my wan dropping out frequently, for a 3-5 seconds at a time. There is no pattern to frequency, it happens overnight and during the day. Sometimes it happens once every 4 hours, sometimes every hour, and sometimes 2-3 times in an hour. All hardware is connected to a UPS so power is not the issue.
Can I increase the verbosity level to get a better idea of what is going on? Any other suggestions(wondering if something is wrong with the cable modem)?
I am using OpenWRT v21.02.3 on a WRT3200ACM.
This is what it looks like in the logs:
Wed Apr 27 07:06:13 2022 daemon.notice netifd: Network device 'wan' link is down
Wed Apr 27 07:06:13 2022 daemon.notice netifd: Interface 'wan' has link connectivity loss
Wed Apr 27 07:06:13 2022 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Wed Apr 27 07:06:13 2022 kern.info kernel: [407256.445892] mv88e6085 f1072004.mdio-mii:00 wan: Link is Down
Wed Apr 27 07:06:13 2022 daemon.notice netifd: wan6 (32152): Command failed: Permission denied
Wed Apr 27 07:06:13 2022 daemon.notice netifd: wan (32151): udhcpc: received SIGTERM
Wed Apr 27 07:06:13 2022 daemon.notice netifd: wan (32151): udhcpc: unicasting a release of 99.xxx.xx.xx to 99.xxx.xx.xx
Wed Apr 27 07:06:13 2022 daemon.notice netifd: wan (32151): udhcpc: sending release
Wed Apr 27 07:06:13 2022 daemon.notice netifd: wan (32151): udhcpc: entering released state
Wed Apr 27 07:06:13 2022 daemon.notice netifd: wan (32151): Command failed: Permission denied
Wed Apr 27 07:06:13 2022 daemon.notice netifd: Interface 'wan' is now down
Wed Apr 27 07:06:14 2022 daemon.notice netifd: Interface 'wan6' is now down
Wed Apr 27 07:06:18 2022 daemon.notice netifd: Network device 'wan' link is up
Wed Apr 27 07:06:18 2022 daemon.notice netifd: Interface 'wan' has link connectivity
Wed Apr 27 07:06:18 2022 daemon.notice netifd: Interface 'wan' is setting up now
Wed Apr 27 07:06:18 2022 daemon.notice netifd: Interface 'wan6' has link connectivity
Wed Apr 27 07:06:18 2022 daemon.notice netifd: Interface 'wan6' is setting up now
I also experienced similar frequent connectivity issues, same router model. Although I assumed that wireless was the culprit without digging into it further. I will switch back over to my 21.02.3 partition and see if I have similar logged events.
Stable as wifi 6 access point from Totolink X5000R, just delete the wan interface and drag it to br-lan device. Delete dnsmasq, odhcpd-ipv6only, dropbear, etc.
I use DD-WRT still as the VPN router.
Thx! And yes must be some error handling going wrong. On that link the error is slightly different though.
I do think the original fault is hopefully gone, because when testing out usteer i followed [OpenWrt Wiki] Setting up usteer and band-steering in OpenWrt. That mentioned putting the time_zone to GMT0. I did that because i though that was required, but that did not work (as I indicated above), but it got me thinking that the actualy error maybe its related to that. So instead of GMT0 I put in the exact string of /etc/TZ. Seems to be ok now, although would be good if that error handling bug gets fixed as crashing the whole wireless is a bit drastic.
The vlan thing not detecting my lan port and not receiving packets in my Mi router 4A gigabit edition is not fix yet in this version, but in 22.03.0-rc1 they fixed it there
I get red light on R7800 on some cases when there is a connected cable, but the device is turned off. E.g. my NAS causes a red LED when turned off. When NAS is on, the light is normal white.
With Netgear's default setup,
Orange/red light can be triggered by a device connecting at 100 Mb/s rather than 1000 Mb/s.
I also encountered it when a failing network cable/plug was in use.
You can easily test it out by unplugging the existing network cable out of port 4
and
Plugging in one of the cables from port 1, 2 or 3 and see if the LED changes to white.
This is awesome and a game changer. Upgraded 3 routers with this method, one of which is a wireless bridge running relayd that i was not looking forward to dismounting from it's location. Everything worked perfectly. Thank you for this tidbit of info.
Hi.
None, very stable. I have/use several devices as routers or AP.
Nevertheless I have moved all these devices to 22.03. One is even running on master snapshot.
Are you having issus with RealTek Fast Ethernet controller enabled devices. I am having issues where devices shows "Ethernet cable unplugged" and log shows something like below
The only way I found to fix this is by manually restarting the LAN interface(on the router) and turing off ARP off load and flow control from windows device manager.
Also I have 2.4Ghz device which show "wifi connected, but no internet" every 13-25mins of usage. Only disconnecting and reconnection helps, but no permanent fix. Device using is R6220.
I have not encountered any issues with the LAN nor ̶W̶i̶F̶i̶.
The 2.4GHz never had issues. It was 5 GHz that had problems with combo stated in previous stable releases.
Reminder that your R6220 is not MediaTek MT7621AT/MT7615N combo that I mentioned.
R6220 has MediaTek MT7621ST/MT7603EN combination
EDIT: Spoke too soon.
After 9 days, encountered same bug where 5 GHz connected to router without any issues, signal strength was excellent but failed to navigate/open any webpages.
Android phone displays Address Not Found
Took a quick look at the system log, nothing indicating problem.
Used android phone without any problems, it went to sleep mode due to inactivity, approximately 7 minutes later, attempted to connect/use Firefox, it displayed error stated above.
Second time error encountered within four hours.
So a possible answer to my own question is that Docker images will be published around the time the official Github release is created for the same version.
I swapped out my cable modem, and splitter leading to the cable modem. No more disconnections have appeared in about 24 hours, so I am considering this issue solved and not related to the firmware.
Profile "linksys_wrt3200acm" does not exist!
Use "make info" to get a list of available profile names.
make[1]: *** [Makefile:216: _check_profile] Error 1
make: *** [Makefile:249: manifest] Error 2
Is this an error? Or did I miss something? Thanks!
With TP-Link AC2600 things were fine after the upgrade. But I pushed the reset button accidentally which caused 5GHz wify to become stuck in disable mode and no restarting or configuration helped.
I removed the network from luci, then configured again and it started to work. If that matters, I used 60th channel with 80MHz width.
