WAN connection dropping periodically with Asus RT-AC5300

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page 1, 2  Next
Author Message
Thefinaleofseem
DD-WRT Novice


Joined: 18 Apr 2008
Posts: 25

PostPosted: Wed Jun 15, 2022 22:22    Post subject: WAN connection dropping periodically with Asus RT-AC5300 Reply with quote
I've been having this issue for a time. My connection is dropping at least once an hour. It's only for a short time, but it's long enough to interrupt meetings, calls, games, etc. It's definitely on the WAN side of things.

I did some digging in the router config. Looks like Xfinity is giving me a whopping 2 hour DHCP lease, which seems absurdly short. It looks like the connections are dropping every 30-60 minutes, one or the other, seemingly right on the dot. Don't get me wrong, I'm definitely betting on Comcast having their heads up their rear ends, but I wanted to be sure this wasn't a DD-WRT issue (and their tech support is useless). I'm familiar with DHCP, but not the nitty-gritty happening under the hood. Is the connection supposed to drop when it passively renews the lease before the lease is up? I get the same IP when it does, but the connection is still interrupted and the WAN Connection Uptime gets reset back to 0:00 every time. I enabled the syslog and I'm seeing this:

Quote:

Jun 16 00:05:37 DD-WRT user.info : dnsmasq : daemon successfully stopped
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[5666]: exiting on receipt of SIGTERM
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: started, version 2.82 cachesize 1500
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua no-TFTP no-conntrack no-ipset no-auth DNSSEC loop-detect no-inotify no-dumpfile
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq-dhcp[6469]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: using only locally-known addresses for domain test
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: using only locally-known addresses for domain onion
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: using only locally-known addresses for domain localhost
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: using only locally-known addresses for domain local
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: using only locally-known addresses for domain invalid
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: using only locally-known addresses for domain bind
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: reading /tmp/resolv.dnsmasq
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: using only locally-known addresses for domain test
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: using only locally-known addresses for domain onion
Jun 16 00:05:37 DD-WRT user.info : dnsmasq : daemon successfully started
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: using only locally-known addresses for domain localhost
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: using only locally-known addresses for domain local
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: using only locally-known addresses for domain invalid
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: using only locally-known addresses for domain bind
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: using nameserver [redacted]
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: using nameserver [redacted]
Jun 16 00:05:37 DD-WRT daemon.info dnsmasq[6469]: read /etc/hosts - 2 addresses
Jun 16 00:05:37 DD-WRT user.info : wland : daemon successfully stopped
Jun 16 00:05:37 DD-WRT user.info : wland : daemon successfully started
Jun 16 00:05:37 DD-WRT user.info : wan : WAN is up. IP: [redacted]
Jun 16 00:05:38 DD-WRT user.info : vpn modules : vpn modules successfully unloaded
Jun 16 00:05:38 DD-WRT user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jun 16 00:05:38 DD-WRT user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jun 16 00:05:38 DD-WRT user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jun 16 00:05:38 DD-WRT user.info : vpn modules : nf_nat_pptp successfully loaded
Jun 16 00:05:38 DD-WRT user.info : sfe : shortcut forwarding engine successfully started
Jun 16 00:05:38 DD-WRT user.info : process_monitor : daemon successfully stopped
Jun 16 00:05:38 DD-WRT daemon.info process_monitor[5784]: process_monitor : cleanup timers
Jun 16 00:05:38 DD-WRT user.info : process_monitor : successfully started
Jun 16 00:05:38 DD-WRT daemon.debug ntpclient[6564]: Connecting to 2.pool.ntp.org [redacted] ...
Jun 16 00:05:38 DD-WRT daemon.info ntpclient[6564]: Time set from 2.pool.ntp.org [redacted].
Jun 16 00:05:38 DD-WRT daemon.info process_monitor[6563]: cyclic NTP Update success (servers 2.pool.ntp.org [redacted])
Jun 16 00:05:38 DD-WRT daemon.debug process_monitor[6563]: We need to re-update after 3600 seconds
Jun 16 00:05:38 DD-WRT daemon.info process_monitor[6563]: process_monitor : set timer: 3600 seconds, callback: ntp_main()


It almost looks like DNSMasq is crashing and restarting entirely, or it could be that this is normally what a DHCP renewal looks like in the logs and I just don't know enough to say. I can say that there's nothing showing up in the modem logs when it happens.
Sponsor
Alozaros
DD-WRT Guru


Joined: 16 Nov 2015
Posts: 6410
Location: UK, London, just across the river..

PostPosted: Wed Jun 15, 2022 22:34    Post subject: Reply with quote
-did you put anything in the NTP time ?
if you decide to add time server it must be an IP format...
best results leave it empty...
-update to a new build...as you didn't state your build i guess you are running old and buggy build...
-what do you have in advanced DNSmasq box ?
-renew lease must not be that bad as you describe it. but the fact DNSmasq is going down and up its another thing...in general it happens sometimes...but not for a long time...
-do you use the ISP DNS servers..or your own...
post pic of your basic settings and system settings (DNSmasq)...cover the sensitive data...


pictures worth a thousands words!

Mar 13 08:35:45 DD-WRT user.info : dnsmasq : daemon successfully started
Mar 13 08:35:45 DD-WRT daemon.info dnsmasq[3727]: using only locally-known addresses for domain test
Mar 13 08:35:45 DD-WRT daemon.info dnsmasq[3727]: using only locally-known addresses for domain onion
Mar 13 08:35:45 DD-WRT daemon.info dnsmasq[3727]: using only locally-known addresses for domain localhost
Mar 13 08:35:45 DD-WRT daemon.info dnsmasq[3727]: using only locally-known addresses for domain local
Mar 13 08:35:45 DD-WRT daemon.info dnsmasq[3727]: using only locally-known addresses for domain invalid
Mar 13 08:35:45 DD-WRT daemon.info dnsmasq[3727]: using only locally-known addresses for domain bind
Mar 13 08:35:45 DD-WRT daemon.info dnsmasq[3727]: reading /tmp/resolv.dnsmasq
Mar 13 08:35:45 DD-WRT daemon.info dnsmasq[3727]: using only locally-known addresses for domain test
Mar 13 08:35:45 DD-WRT daemon.info dnsmasq[3727]: using only locally-known addresses for domain onion
Mar 13 08:35:45 DD-WRT daemon.info dnsmasq[3727]: using only locally-known addresses for domain localhost
Mar 13 08:35:45 DD-WRT daemon.info dnsmasq[3727]: using only locally-known addresses for domain local
Mar 13 08:35:45 DD-WRT daemon.info dnsmasq[3727]: using only locally-known addresses for domain invalid
Mar 13 08:35:45 DD-WRT daemon.info dnsmasq[3727]: using only locally-known addresses for domain bind

those lines are normal and ive seen those in another user reports
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=328523&postdays=0&postorder=asc&start=0

you need to tell us more about your DNS set up...

_________________
Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913


Last edited by Alozaros on Wed Jun 15, 2022 22:51; edited 1 time in total
Thefinaleofseem
DD-WRT Novice


Joined: 18 Apr 2008
Posts: 25

PostPosted: Wed Jun 15, 2022 22:50    Post subject: Reply with quote
I redacted NTP servers. I have not manually entered any info for that. It's finding NTP servers on its own and that seems to be working fine. I just wanted to remove any potential sensitive information from the post.

Apologies, I missed the build. It's 3.0 r455715, which seems to be the latest recommended build for my router.

I have not entered any advanced DNSMasq settings. DNSMasq is enabled, but it's auto-config/defaults beyond that.

I'm relying on the ISP DNS servers. I could switch to top-level if that might help.

I've attached the basic settings, but I'm not sure where the system settings would be beyond this.



ddwrt-settings.jpg
 Description:
Basic settings
 Filesize:  164.12 KB
 Viewed:  2872 Time(s)

ddwrt-settings.jpg


Alozaros
DD-WRT Guru


Joined: 16 Nov 2015
Posts: 6410
Location: UK, London, just across the river..

PostPosted: Wed Jun 15, 2022 23:22    Post subject: Reply with quote
https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2022/

those are the last builds...06-14-2022-r49197 is the very last ATM...

45715 is a know buggy build recommended by the data base please ignore it, as well compared to the recent builds, it has many security flaws...and unpatched/not updated stuff...

after update, not bad idea to reset holding reset button for 10 sec or via GUI reset to defaults and rebuild settings manually...

i can see you are using the ISP DNS...that is fetched by auto DHCP...(i usually stay away from those)
it wont hurt to add a static DNS's at least 1-2 like 9.9.9.9 or 1.0.0.1...if you want to totally ignore the ISP DNS and use only yours, than click ignore WAN DNS at the top and add yours in static...

ignore WAN DNS and adding a static DNS's, should be enough to make use only of your DNS..
last thing Shortcut Forwarding Engine (SFE) if you don't use it turn it off, it tends to break things...

_________________
Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
dale_gribble39
DD-WRT Guru


Joined: 11 Jun 2022
Posts: 1899

PostPosted: Thu Jun 16, 2022 2:31    Post subject: Reply with quote
It could be the WAN dhcp lease time vs. NTP update interval and services restarting. Newer releases have the ability to change the interval in the webUI. Once per day (86400 seconds) is more than frequent enough. If you are using static leases (as indicated by the two hosts in /etc/hosts message), any non-allowed characters in hostnames or MAC addresses will also cause issues.
_________________
"The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost

"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio

<fact>code knows no gender</fact>

This is me, knowing I've ruffled your feathers, and not giving a ****
Some people are still hard-headed.

--------------------------------------
Mac Pro (Mid 2012) - Two 2.4GHz 6-Core Intel Xeon E5645 processors 64GB 1333MHz DDR3 ECC SDRAM OpenSUSE Leap 15.5
Thefinaleofseem
DD-WRT Novice


Joined: 18 Apr 2008
Posts: 25

PostPosted: Tue Jun 21, 2022 19:00    Post subject: Reply with quote
I've updated to r49197 and reset to defaults. I've done a minimal reconfiguration after the RFD, just the login/password, the wifi settings/security, and enabling the syslog. I should note that it keeps setting my time to Europe/Berlin, but I'm in the US. I've set it back to the proper timezone, but that doesn't seem to be related.

The problem persists. I can't seem to get more than an hour of uptime before my connection gets reset again. The syslog seems to have the same output as before. I'm not sure what's going on. Is there a "harder" reset I should try?
dale_gribble39
DD-WRT Guru


Joined: 11 Jun 2022
Posts: 1899

PostPosted: Tue Jun 21, 2022 19:45    Post subject: Reply with quote
Xfinity only giving you a two-hour lease means that your DHCP client is forced to renew every hour, which (may) coincide(s) with your NTP update interval. Are you using CTF/SFE? You should set your NTP update interval to 86400 (once per day) since NTP sync updates restart certain services in DD-WRT; also the current release is 49268.
_________________
"The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost

"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio

<fact>code knows no gender</fact>

This is me, knowing I've ruffled your feathers, and not giving a ****
Some people are still hard-headed.

--------------------------------------
Mac Pro (Mid 2012) - Two 2.4GHz 6-Core Intel Xeon E5645 processors 64GB 1333MHz DDR3 ECC SDRAM OpenSUSE Leap 15.5
Thefinaleofseem
DD-WRT Novice


Joined: 18 Apr 2008
Posts: 25

PostPosted: Tue Jun 21, 2022 20:59    Post subject: Reply with quote
I've upped the NTP interval and the problem still persists. I'm currently using SFE (which appears to make things snappier on faster connections from what I can tell), but I wasn't when this started, so enabling/disabling it doesn't seem to have an effect.
dale_gribble39
DD-WRT Guru


Joined: 11 Jun 2022
Posts: 1899

PostPosted: Tue Jun 21, 2022 21:50    Post subject: Reply with quote
I see no upstream commits after busybox 1.35.0-stable that would deem merging to fix anything; without merging current git on dnsmasq, there is no proving or disproving any commits since dnsmasq-v2.87test8 will help us. Short DHCP lease times from Xfinity has to be wreaking havoc somehow, possibly due to services restarting on WAN lease renewal. I would also look at trying CTF or CTF+FA.
_________________
"The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost

"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio

<fact>code knows no gender</fact>

This is me, knowing I've ruffled your feathers, and not giving a ****
Some people are still hard-headed.

--------------------------------------
Mac Pro (Mid 2012) - Two 2.4GHz 6-Core Intel Xeon E5645 processors 64GB 1333MHz DDR3 ECC SDRAM OpenSUSE Leap 15.5
Thefinaleofseem
DD-WRT Novice


Joined: 18 Apr 2008
Posts: 25

PostPosted: Tue Jun 21, 2022 22:06    Post subject: Reply with quote
If I'm reading the docs correctly then I don't seem to have access to CTF/FA. It should appear under SFE on the basic setup page as I know this router has a Broadcom chip (Broadcom BCM4709), but it's nowhere to be found. I only have SFE and STP options.
dale_gribble39
DD-WRT Guru


Joined: 11 Jun 2022
Posts: 1899

PostPosted: Tue Jun 21, 2022 23:00    Post subject: Reply with quote
Clear browser cache; CTRL+F5 cache override. Are you using the standard driver or experimental driver firmware image?
_________________
"The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost

"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio

<fact>code knows no gender</fact>

This is me, knowing I've ruffled your feathers, and not giving a ****
Some people are still hard-headed.

--------------------------------------
Mac Pro (Mid 2012) - Two 2.4GHz 6-Core Intel Xeon E5645 processors 64GB 1333MHz DDR3 ECC SDRAM OpenSUSE Leap 15.5
Thefinaleofseem
DD-WRT Novice


Joined: 18 Apr 2008
Posts: 25

PostPosted: Tue Jun 21, 2022 23:35    Post subject: Reply with quote
Browser cache clear doesn't change anything. I'm using the standard driver.
foreverforgotten
DD-WRT Novice


Joined: 16 Jun 2022
Posts: 16
Location: Dallas, TX

PostPosted: Tue Jun 21, 2022 23:55    Post subject: Reply with quote
You're on r49197 now which is recent. I'm also running RT-AC5300 but now with the latest build r49268 which is running fine. But I'm not serviced via Xfininity (Comcast), but I used to be a few years ago.

Were you running DD-WRT prior the issue? If so, perhaps contact the ISP to come out and check your line. Maybe you have a signal issue from house -> box that's triggering your modem/router to reset and attempt a DHCP lease renewal. Feels like a long-shot if you're seeing the issue consistently on a fixed time interval, but if the timing is more varied, then could be a line quality issue.

ISPs will often renew a DHCP lease with the same IP even if the lease is short. And that shouldn't be a disruptive operation. So I'm less inclined to suspect it has anything to do with the lease timing and more to do with something that's triggering the router/modem to recheck its lease as a recovery mechanism for a loss-in-connectivity response.
Thefinaleofseem
DD-WRT Novice


Joined: 18 Apr 2008
Posts: 25

PostPosted: Wed Jun 22, 2022 5:10    Post subject: Reply with quote
I've been running DD-WRT for over a decade and for a couple of years on this router. The interruptions seem to be happening every hour almost on the dot. It does seem to be a DHCP renewal issue, though I'm not sure what's going on or why. It's definitely not the modem. I can access the logs on it and there's nothing to indicate any trouble in the line.
Thefinaleofseem
DD-WRT Novice


Joined: 18 Apr 2008
Posts: 25

PostPosted: Wed Jun 22, 2022 17:53    Post subject: Reply with quote
Just watched it happen. Two hour lease time, and when it hits 1 hour precisely the connection gets reset and uptime starts counting up from 0 again. It's definitely something screwy with the lease renewal. Maybe Xfinity is doing something screwy or maybe there's some kind of issue with DD-WRT renewing the lease.
Goto page 1, 2  Next Display posts from previous:    Page 1 of 2
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum