Internet connection cannot be provided on the openwrt router after a power outage.
After the interruption, I can restart the asus router manually and get internet output without asking any questions.
ASUS RT-AX53U # OpenWrt SNAPSHOT r22071
I got the following logs when the internet was not available after the outage:
https://logpaste.com/lNvBrybL
https://logpaste.com/kDiThx03
In addition, I tried the adguard home solution in the link and did not get any results.
These two statements are contradictory... can you provide more detail?
From your logs, it appears there is an upstream router... have you verified that the device in front of the OpenWrt router is working as expected?
Is there a reason you are using snapshot? In many cases, it is recommended to use the stable release of OpenWrt, unless snapshot is needed by the user.
https://firmware-selector.openwrt.org/?version=22.03.3&target=ramips%2Fmt7621&id=asus_rt-ax53u
To see if it's a DNS problem, try pinging a numeric IP such as 8.8.8.8. Also try pinging your upstream modem / router 192.168.1.1.
It's concerning that the WAN Ethernet is only linked at 100 Mb instead of 1000, unless the modem is some old ADSL box that does not support GbE.
Microsoft Windows [Version 10.0.22621.1265]
(c) Microsoft Corporation. All rights reserved.
C:\Windows\System32>ping 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=31ms TTL=110
Reply from 8.8.8.8: bytes=32 time=30ms TTL=110
Reply from 8.8.8.8: bytes=32 time=30ms TTL=110
Reply from 8.8.8.8: bytes=32 time=30ms TTL=110
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 31ms, Average = 30ms
C:\Windows\System32>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=3ms TTL=63
Reply from 192.168.1.1: bytes=32 time=7ms TTL=63
Reply from 192.168.1.1: bytes=32 time=2ms TTL=63
Reply from 192.168.1.1: bytes=32 time=2ms TTL=63
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 7ms, Average = 3ms
I restarted by cutting off the modem and router power. After we turned on, I can ping, but I cannot out to the internet with my pc and mobile phone.
If I restart the openwrt router manually, I can connect without any problems.
"and I just updated to the most recent SNAPSHOT r22124"
try pinging google.com
This doesn't answer why you are using snapshot... do you need snapshot for a specific reason?
And you also didn't answer the question about the upstream router -- if you connect to that device, does the internet work normally?
I had this same issue many years ago and it turned out to be with the Motorola cable modem. The modem DHCP wouldn't work if the router powering up wasn't timed right (I don't remember if it was sooner or later though that made it work).
I solved by using a timed power on sequence from a power loss.
I only use snapshot to be the most up-to-date version and yes I can connect to the internet with the main router (modem) without any problems.
After the following commands, I can out the internet without the need to restart openwrt.
service adguardhome disable
service adguardhome enable
service adguardhome start
How can I prepare a script as in the link below.
I think if adguardhome works after a certain period of time after openwrt is opened, the problem can be solved.
This will obviously have you at the bleeding edge, but sometimes there can be problems with snapshots. Typically, unless you need a patch/feature/bug-fix that doesn't existing in the stable release images, you don't need to worry about being up to date using snapshots. It's up to you, of course. And this is not likely what is wrong with your situation.
If this is your problem, you can brute-force it by adding sleep n into the start service section where n is the number of seconds you want to delay the startup of AGH.
Have AGH already changed their init.d script, so it starts last during boot ?
I'd there a S99adguardhome in /etc/rc.d ?
Thanks for sharing your workaround this insue.
I do not have AdGuard bit I was having this problem after a power loss (when reboot was not a problem).
After change the domains for theirs IP's all works perfect.
Tks very much.