Posted: Mon Jan 05, 2026 23:55 Post subject: Linksys MR7350 frequent disconnection
Router Model: Linksys MR7350
Firmware Version: DD-WRT v3.0-r63257 std (01/03/26)
Kernel Version: Linux 6.6.119-rt29 #4938 SMP Fri Jan 2 15:01:42 +07 2026 aarch64
Previous version: DD-WRT r63230
Services: samba, wireguard client, openvpn client, dhcp, wifi 2.4 ghz, 5 ghz, usb, nas
Status: working
Updated: via webgui
Mode: AP/gateway
Issues: router disconnects after 20 minutes or longer but less than 50 minutes
Reset/reboot: no/yes
Uptime: 33 min n since last disconnected
Load Average: 0.00, 0.02, 0.05
Errors with red background: as reported in the syslog below
Dec 31 20:00:11.952 DD-WRT kern.err kernel: [ 0.079251] qcom_rpm_smd_regulator remoteproc:glink-edge:rpm-requests:regulators: Supply for l2 (l2) resolved to itself
Dec 31 20:00:11.953 DD-WRT kern.err kernel: [ 1.049730] Block protection check failed
Dec 31 20:00:11.954 DD-WRT kern.alert kernel: [ 2.178497] mtdsplit: no squashfs found in "rootfs"
Dec 31 20:00:11.957 DD-WRT kern.alert kernel: [ 9.659836] node size 2 # items 4
Dec 31 20:00:11.957 DD-WRT kern.alert kernel: [ 9.666739] memory: 40000000 536870912 (avl 434663424) items 4 active_cores 1
Dec 31 20:00:11.957 DD-WRT kern.alert kernel: [ 9.670066] avail_ddr 434663424, ddr size 536870912
Dec 31 20:00:11.957 DD-WRT kern.alert kernel: [ 9.677294] ffffffc078f7d180: NSS core 0 DDR from 40000000 to 41000000
Dec 31 20:00:11.957 DD-WRT kern.alert kernel: [ 9.708787] Register data plane workqueue on core 1
Dec 31 20:00:11.957 DD-WRT kern.alert kernel: [ 9.708835] ffffffc078f7d180: send DDR info
Dec 31 20:00:11.957 DD-WRT kern.alert kernel: [ 9.712495] node size 2 # items 4
Dec 31 20:00:11.957 DD-WRT kern.alert kernel: [ 9.716641] memory: 40000000 536870912 (avl 434663424) items 4 active_cores 1
Dec 31 20:00:11.957 DD-WRT kern.alert kernel: [ 9.720121] avail_ddr 434663424, ddr size 536870912
Dec 31 20:00:12.380 DD-WRT daemon.crit smartd[1547]: In the system's table of devices NO devices found to scan
Dec 31 20:00:12.910 DD-WRT kern.alert kernel: [ 12.914171] ffffffc078f7d180: Phys If Open, id:1, TxDesc: 0, RxDesc: 0, mode 0
Dec 31 20:00:12.950 DD-WRT kern.alert kernel: [ 12.949002] ffffffc078f7d180: Phys If Open, id:2, TxDesc: 0, RxDesc: 0, mode 0
Dec 31 20:00:12.980 DD-WRT kern.alert kernel: [ 12.983835] ffffffc078f7d180: Phys If Open, id:3, TxDesc: 0, RxDesc: 0, mode 0
Dec 31 20:00:13.020 DD-WRT kern.alert kernel: [ 13.018493] ffffffc078f7d180: Phys If Open, id:4, TxDesc: 0, RxDesc: 0, mode 0
Dec 31 20:00:23.944 DD-WRT daemon.crit smartd[1801]: In the system's table of devices NO devices found to scan
Dec 31 20:00:25.554 DD-WRT kern.alert kernel: [ 25.554970] == for dynamic interface types read following file ==
Dec 31 20:00:25.554 DD-WRT kern.alert kernel: [ 25.554986] /sys/kernel/debug/qca-nss-drv/stats/dynamic_if/type_names
Dec 31 20:00:25.554 DD-WRT kern.alert kernel: [ 25.556025] NSS PPE VP create: echo > /proc/sys/nss/ppe_vp/create
Dec 31 20:00:25.570 DD-WRT kern.alert kernel: [ 25.562207] NSS PPE VP destroy: echo > /proc/sys/nss/ppe_vp/destroy
Dec 31 20:00:25.580 DD-WRT kern.alert kernel: [ 25.568695] == for dynamic interface types read following file ==
Dec 31 20:00:25.593 DD-WRT kern.alert kernel: [ 25.579713] /sys/kernel/debug/qca-nss-drv/stats/dynamic_if/type_names
Dec 31 20:00:25.593 DD-WRT kern.alert kernel: [ 25.588185] NSS PPE VP create: echo > /proc/sys/nss/ppe_vp/create
Dec 31 20:00:25.962 DD-WRT kern.alert kernel: [ 25.594260] NSS PPE VP destroy: echo > /proc/sys/nss/ppe_vp/destroy
Dec 31 20:00:25.962 DD-WRT kern.alert kernel: [ 25.953836] ffffffc078f7d180: Phys If Open, id:5, TxDesc: 0, RxDesc: 0, mode 0
Dec 31 20:00:29.445 DD-WRT user.err : error starting threads: errno 2 (No such file or directory)
Dec 31 20:00:31.278 DD-WRT local5.err ksmbd: [ksmbd.mountd/2583]: ERROR: Invalid lock entry `2087'
Dec 31 20:00:32.346 DD-WRT local5.err ksmbd: [ksmbd.mountd(manager)/2583]: ERROR: Worker fatally killed: Bus error
Dec 31 20:00:32.440 DD-WRT kern.err kernel: [ 32.443106] /dev/sda3: Can't open blockdev
Dec 31 20:00:32.440 DD-WRT kern.err kernel: [ 32.443867] /dev/sda3: Can't open blockdev
Dec 31 20:00:32.450 DD-WRT kern.err kernel: [ 32.447965] /dev/sda3: Can't open blockdev
Dec 31 20:00:32.450 DD-WRT kern.err kernel: [ 32.451948] /dev/sda3: Can't open blockdev
Dec 31 20:00:32.959 DD-WRT local5.err ksmbd: [ksmbd.mountd/2863]: ERROR: Invalid lock entry `2583'
Dec 31 20:00:32.970 DD-WRT kern.err kernel: [ 32.969467] ksmbd: Reconnect to a new user space daemon
Dec 31 20:00:34.655 DD-WRT user.emerg smartdns: process exit with signal 11, code = 1, errno = 0, pid = -1783597928, self = 1894, pc = 0x7f9625c640, addr = 0x7f95b07498, build(Jan 3 2026 14:45:45 arm64)
Dec 31 20:00:34.656 DD-WRT user.emerg smartdns: Stack:
Dec 31 20:00:34.656 DD-WRT user.emerg smartdns: #01: 0x41a6ac print_stack() from /usr/sbin/smartdns+0x1a6ac
Dec 31 20:00:34.656 DD-WRT user.emerg smartdns: #02: 0x41a7ec () from /usr/sbin/smartdns+0x1a7ec
Dec 31 20:00:34.656 DD-WRT user.emerg smartdns: #03: 0x7f9624c964 __setjmp() from /lib/ld-musl-aarch64.so.1+0x4a964
Dec 31 20:00:34.656 DD-WRT user.emerg smartdns: #04: 0x7f9625c640 () from /lib/ld-musl-aarch64.so.1+0x5a640
Dec 31 20:00:35.911 DD-WRT user.emerg smartdns: process exit with signal 11, code = 1, errno = 0, pid = -1396468584, self = 3000, pc = 0x7fad38e640, addr = 0x7facc39498, build(Jan 3 2026 14:45:45 arm64)
Dec 31 20:00:35.912 DD-WRT user.emerg smartdns: Stack:
Dec 31 20:00:35.912 DD-WRT user.emerg smartdns: #01: 0x41a6ac print_stack() from /usr/sbin/smartdns+0x1a6ac
Dec 31 20:00:35.912 DD-WRT user.emerg smartdns: #02: 0x41a7ec () from /usr/sbin/smartdns+0x1a7ec
Dec 31 20:00:35.912 DD-WRT user.emerg smartdns: #03: 0x7fad37e964 __setjmp() from /lib/ld-musl-aarch64.so.1+0x4a964
Dec 31 20:00:35.912 DD-WRT user.emerg smartdns: #04: 0x7fad38e640 () from /lib/ld-musl-aarch64.so.1+0x5a640
Dec 31 20:00:39.564 DD-WRT kern.alert kernel: [ 39.563795] == for dynamic interface types read following file ==
Dec 31 20:00:39.564 DD-WRT kern.alert kernel: [ 39.563802] /sys/kernel/debug/qca-nss-drv/stats/dynamic_if/type_names
Dec 31 20:00:39.570 DD-WRT kern.alert kernel: [ 39.565461] NSS PPE VP create: echo > /proc/sys/nss/ppe_vp/create
Dec 31 20:00:39.580 DD-WRT kern.alert kernel: [ 39.571699] NSS PPE VP destroy: echo > /proc/sys/nss/ppe_vp/destroy
Dec 31 20:00:39.590 DD-WRT kern.alert kernel: [ 39.578168] == for dynamic interface types read following file ==
Dec 31 20:00:39.590 DD-WRT kern.alert kernel: [ 39.587784] /sys/kernel/debug/qca-nss-drv/stats/dynamic_if/type_names
Dec 31 20:00:39.602 DD-WRT kern.alert kernel: [ 39.597625] NSS PPE VP create: echo > /proc/sys/nss/ppe_vp/create
Jan 5 18:33:21.708 DD-WRT kern.alert kernel: [ 39.603663] NSS PPE VP destroy: echo > /proc/sys/nss/ppe_vp/destroy
an 5 18:33:21.907 DD-WRT user.emerg smartdns: process exit with signal 11, code = 1, errno = 0, pid = -1462111080, self = 3011, pc = 0x7fa94f4640, addr = 0x7fa8d9f498, build(Jan 3 2026 14:45:45 arm64)
Jan 5 18:33:21.908 DD-WRT user.emerg smartdns: Stack:
Jan 5 18:33:21.908 DD-WRT user.emerg smartdns: #01: 0x41a6ac print_stack() from /usr/sbin/smartdns+0x1a6ac
Jan 5 18:33:21.908 DD-WRT user.emerg smartdns: #02: 0x41a7ec () from /usr/sbin/smartdns+0x1a7ec
Jan 5 18:33:21.908 DD-WRT user.emerg smartdns: #03: 0x7fa94e4964 __setjmp() from /lib/ld-musl-aarch64.so.1+0x4a964
Jan 5 18:33:21.908 DD-WRT user.emerg smartdns: #04: 0x7fa94f4640 () from /lib/ld-musl-aarch64.so.1+0x5a640
Jan 5 18:33:26.271 DD-WRT kern.alert kernel: [ 45.533172] == for dynamic interface types read following file ==
Jan 5 18:33:26.271 DD-WRT kern.alert kernel: [ 45.533179] /sys/kernel/debug/qca-nss-drv/stats/dynamic_if/type_names
Jan 5 18:33:26.271 DD-WRT kern.alert kernel: [ 45.534868] NSS PPE VP create: echo > /proc/sys/nss/ppe_vp/create
Jan 5 18:33:26.287 DD-WRT kern.alert kernel: [ 45.540976] NSS PPE VP destroy: echo > /proc/sys/nss/ppe_vp/destroy
Jan 5 18:33:26.287 DD-WRT kern.alert kernel: [ 45.547459] == for dynamic interface types read following file ==
Jan 5 18:33:26.303 DD-WRT kern.alert kernel: [ 45.556938] /sys/kernel/debug/qca-nss-drv/stats/dynamic_if/type_names
Jan 5 18:33:26.303 DD-WRT kern.alert kernel: [ 45.566984] NSS PPE VP create: echo > /proc/sys/nss/ppe_vp/create
Jan 5 18:33:27.158 DD-WRT kern.alert kernel: [ 45.573069] NSS PPE VP destroy: echo > /proc/sys/nss/ppe_vp/destroy
Jan 5 18:33:29.050 DD-WRT user.emerg smartdns: process exit with signal 11, code = 1, errno = 0, pid = -1460382568, self = 3331, pc = 0x7fa969a640, addr = 0x7fa8f45498, build(Jan 3 2026 14:45:45 arm64)
Jan 5 18:33:29.050 DD-WRT user.emerg smartdns: Stack:
Jan 5 18:33:29.050 DD-WRT user.emerg smartdns: #01: 0x41a6ac print_stack() from /usr/sbin/smartdns+0x1a6ac
Jan 5 18:33:29.050 DD-WRT user.emerg smartdns: #02: 0x41a7ec () from /usr/sbin/smartdns+0x1a7ec
Jan 5 18:33:29.051 DD-WRT user.emerg smartdns: #03: 0x7fa968a964 __setjmp() from /lib/ld-musl-aarch64.so.1+0x4a964
Jan 5 18:33:29.051 DD-WRT user.emerg smartdns: #04: 0x7fa969a640 () from /lib/ld-musl-aarch64.so.1+0x5a640
an 5 18:33:30.299 DD-WRT user.emerg smartdns: process exit with signal 11, code = 1, errno = 0, pid = -1608674152, self = 3779, pc = 0x7fa092e640, addr = 0x7fa01d9498, build(Jan 3 2026 14:45:45 arm64)
Jan 5 18:33:30.299 DD-WRT user.emerg smartdns: Stack:
Jan 5 18:33:30.299 DD-WRT user.emerg smartdns: #01: 0x41a6ac print_stack() from /usr/sbin/smartdns+0x1a6ac
Jan 5 18:33:30.299 DD-WRT user.emerg smartdns: #02: 0x41a7ec () from /usr/sbin/smartdns+0x1a7ec
Jan 5 18:33:30.299 DD-WRT user.emerg smartdns: #03: 0x7fa091e964 __setjmp() from /lib/ld-musl-aarch64.so.1+0x4a964
Jan 5 18:33:30.299 DD-WRT user.emerg smartdns: #04: 0x7fa092e640 () from /lib/ld-musl-aarch64.so.1+0x5a640
Jan 5 18:33:38.963 DD-WRT kern.alert kernel: [ 58.225002] == for dynamic interface types read following file ==
Jan 5 18:33:38.963 DD-WRT kern.alert kernel: [ 58.225009] /sys/kernel/debug/qca-nss-drv/stats/dynamic_if/type_names
Jan 5 18:33:38.963 DD-WRT kern.alert kernel: [ 58.226693] NSS PPE VP create: echo > /proc/sys/nss/ppe_vp/create
Jan 5 18:33:38.979 DD-WRT kern.alert kernel: [ 58.232789] NSS PPE VP destroy: echo > /proc/sys/nss/ppe_vp/destroy
Jan 5 18:33:38.979 DD-WRT kern.alert kernel: [ 58.239371] == for dynamic interface types read following file ==
Jan 5 18:33:39.002 DD-WRT kern.alert kernel: [ 58.248788] /sys/kernel/debug/qca-nss-drv/stats/dynamic_if/type_names
Jan 5 18:33:39.002 DD-WRT kern.alert kernel: [ 58.258829] NSS PPE VP create: echo > /proc/sys/nss/ppe_vp/create
Jan 5 18:57:39.936 DD-WRT kern.alert kernel: [ 58.264888] NSS PPE VP destroy: echo > /proc/sys/nss/ppe_vp/destroy
I am a novice who does not know if I have complied with the photo requirements.
I need help in stopping the router from constantly rebooting.
I flushed the dns cache
I disabled dns in services and unticked the use dnsmasq for dns in basic setup.
Results; still constant rebooting.
Joined: 16 Nov 2015 Posts: 7090 Location: UK, London, just across the river..
Posted: Tue Jan 06, 2026 4:42 Post subject: Re: Linksys MR7350 frequent disconnection
Abboo wrote:
I am a novice who does not know if I have complied with the photo requirements.
I need help in stopping the router from constantly rebooting.
I flushed the dns cache
I disabled dns in services and unticked the use dnsmasq for dns in basic setup.
Results; still constant rebooting.
there are few mistakes i can spot....
-disable/untick Recursive DNS (unbound)
-try disable SFE and QCA NSS sybsystem...
-add to advanced DNSmasq config no-resolv this command will stop any other DNS and point only to those specified at server=
-on DDWRT DHCP daemon usually starts from ether 64 or 100 and in your case its 192.168.3.2 amd its wrong it should be 192.168.3.100
and yes those last few builds are bit wonky on some devices....there is also a transition from iptables to iptables-nft so if you have any rules you need to adapt/translate those and some rules do not do so easy...
_________________ Atheros
TP-Link WR1043NDv2 -DD-WRT 62606 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 63600 GTW/SmDNS/DoT,AD-Blk,Forced DNS,AP&Net Isolation,x2VLAN,Vanilla
Netgear R7800 --DD-WRT 62606 Gateway/DNSCryptv2,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla,VPN cli
Netgear R9000 --DD-WRT 62606 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Dynalink DL-WRX36-DDWRT 62606
Broadcom
Netgear R7000 --DD-WRT 63600 GTW/DNScrypt-proxy2/AD-Block,IPset Firewall,Forced DNS,x4VLAN,VPN cli
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Posted: Wed Jan 07, 2026 1:29 Post subject: Re: Linksys MR7350 frequent disconnection
Alozaros wrote:
Abboo wrote:
I am a novice who does not know if I have complied with the photo requirements.
I need help in stopping the router from constantly rebooting.
I flushed the dns cache
I disabled dns in services and unticked the use dnsmasq for dns in basic setup.
Results; still constant rebooting.
there are few mistakes i can spot....
-disable/untick Recursive DNS (unbound)
-try disable SFE and QCA NSS sybsystem...
-add to advanced DNSmasq config no-resolv this command will stop any other DNS and point only to those specified at server=
-on DDWRT DHCP daemon usually starts from ether 64 or 100 and in your case its 192.168.3.2 amd its wrong it should be 192.168.3.100
and yes those last few builds are bit wonky on some devices....there is also a transition from iptables to iptables-nft so if you have any rules you need to adapt/translate those and some rules do not do so easy...
These are the changes I made
- on setup basic tab, I ticked ignore WAN dns
- I kept ticked qca nss subsystem, otherwise, dns will stop responding
- short cut forwarding engine: nss-ecm
- start ip address 192.168.3.64
- static dns 1, 2, & 3 are all zeros
- ticked use dnsmasq for dns and dhcp-authoritative
-on services services tab
- I disabled dhcp classless routes (option 121)
- I enabled resolver and serve expired
- enabled dnsmasq
- enabled query dns in strict order
- in additional option:
domain-needed
no-negcache
no-resolv
server=149.112.112.112
server=9.9.9.9
server=1.0.0.1
server=/pool.ntp.org/time.google.com/149.112.112.112
server=/pool.ntp.org/time.google.com/1.0.0.1
server=/pool.ntp.org/time.google.com/9.9.9.9
- I don't have any rules in the iptables
And the router still reboots, roughly, after an hour. It is now running 18 minutes after the last disconnection.
Would switching to vpn cause any corruption or issues?
Joined: 08 May 2018 Posts: 16756 Location: Texas, USA
Posted: Wed Jan 07, 2026 2:58 Post subject:
It seems you are using smartdns. Please read the guide on how to properly configure dnsmasq and smartdns to be used together. And there are probably things that you are not showing us that could be culprit in your configs.
Joined: 16 Nov 2015 Posts: 7090 Location: UK, London, just across the river..
Posted: Wed Jan 07, 2026 7:13 Post subject:
kernel-panic69 wrote:
It seems you are using smartdns. Please read the guide on how to properly configure dnsmasq and smartdns to be used together. And there are probably things that you are not showing us that could be culprit in your configs.
yep indeed, a messy setup... _________________ Atheros
TP-Link WR1043NDv2 -DD-WRT 62606 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 63600 GTW/SmDNS/DoT,AD-Blk,Forced DNS,AP&Net Isolation,x2VLAN,Vanilla
Netgear R7800 --DD-WRT 62606 Gateway/DNSCryptv2,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla,VPN cli
Netgear R9000 --DD-WRT 62606 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Dynalink DL-WRX36-DDWRT 62606
Broadcom
Netgear R7000 --DD-WRT 63600 GTW/DNScrypt-proxy2/AD-Block,IPset Firewall,Forced DNS,x4VLAN,VPN cli
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
It seems you are using smartdns. Please read the guide on how to properly configure dnsmasq and smartdns to be used together. And there are probably things that you are not showing us that could be culprit in your configs.
yep indeed, a messy setup...
I went to Wiki, tutorial, dnsmasq as dhcp server. I hope this is the guide you referred to to properly configue dnsmasq.
I discovered 2 new information:
1) in dnsmasq addition options, domain-needed, seems to imply 'needed' is the name of the domain on setup basic, setup tab, hence, I entered the name 'needed' there in domain name.
2) 'expand-hosts' was added to additional options
I also disabled smartdns resolver
The result is the router still disconnects around 60 minutes of uptime repeatedly.
If the wiki article is not the guide you were referring to, please provide a link to it.
Joined: 04 Aug 2018 Posts: 1577 Location: Appalachian mountains, USA
Posted: Thu Jan 08, 2026 20:26 Post subject:
I haven't been following this thread closely so don't want to try to get deep here, but "domain-needed" most certainly does NOT imply "needed" is a domain name. To see what dnsmasq options mean, the proper resource is https://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html
Look there for the option "--domain-needed" because they show all options with the leading "--" one would use in calling dnsmasq from the command line. In Additional Options the "--" is NOT used. Just use "domain-needed" without the quotes.
In fact the "Domain" entry in the basic setup should be left empty for most users' setups. _________________ On 61465: 3x Dynalink DL-WRX36, Linksys MX4200v2, 2x MR7350. WPA2personal/WPA3 w/ AES, VAPs, NAS, station mode, OpenVPN client (AirVPN), wireguard server (AirVPN port forward) and clients (AzireVPN, AirVPN, private), Two SmartDNS/DoT providers and one DNSCrypt provider via VPNs. DNSmasq manages that plus ad blocking and local DNS.
Joined: 08 May 2018 Posts: 16756 Location: Texas, USA
Posted: Thu Jan 08, 2026 21:41 Post subject:
Abboo wrote:
I went to Wiki, tutorial, dnsmasq as dhcp server. I hope this is the guide you referred to to properly configue dnsmasq.
I discovered 2 new information:
1) in dnsmasq addition options, domain-needed, seems to imply 'needed' is the name of the domain on setup basic, setup tab, hence, I entered the name 'needed' there in domain name.
2) 'expand-hosts' was added to additional options
I also disabled smartdns resolver
The result is the router still disconnects around 60 minutes of uptime repeatedly.
If the wiki article is not the guide you were referring to, please provide a link to it.
Router Model: Netgear R9000
Firmware Version DD-WRT v3.0-r63257 std (01/03/26)
Problems: OpenVPN server is not working. The client connects but there is no internet coming through. It seems to be happening in every build using 6.12 kernel.
Downgrading to r62606 std (11/12/25) fixes the problem as it is still using the old 4.9 kernel
I haven't been following this thread closely so don't want to try to get deep here, but "domain-needed" most certainly does NOT imply "needed" is a domain name. To see what dnsmasq options mean, the proper resource is https://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html
Look there for the option "--domain-needed" because they show all options with the leading "--" one would use in calling dnsmasq from the command line. In Additional Options the "--" is NOT used. Just use "domain-needed" without the quotes.
In fact the "Domain" entry in the basic setup should be left empty for most users' setups.
I went to Wiki, tutorial, dnsmasq as dhcp server. I hope this is the guide you referred to to properly configue dnsmasq.
I discovered 2 new information:
1) in dnsmasq addition options, domain-needed, seems to imply 'needed' is the name of the domain on setup basic, setup tab, hence, I entered the name 'needed' there in domain name.
2) 'expand-hosts' was added to additional options
I also disabled smartdns resolver
The result is the router still disconnects around 60 minutes of uptime repeatedly.
If the wiki article is not the guide you were referring to, please provide a link to it.
That Wiki was written when there was more than one option for DHCP server for the LAN. It's not quite a very good reference and probably needs to be re-written in entirety. As was already said, you misunderstood "domain-needed"... the only tip I can give is to change your NTP sync interval to 86400 (daily), because it seems that might be part of the "issue"...
Thanks, I have implemented the advice given by everyone.
I haven't been following this thread closely so don't want to try to get deep here, but "domain-needed" most certainly does NOT imply "needed" is a domain name. To see what dnsmasq options mean, the proper resource is https://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html
Look there for the option "--domain-needed" because they show all options with the leading "--" one would use in calling dnsmasq from the command line. In Additional Options the "--" is NOT used. Just use "domain-needed" without the quotes.
In fact the "Domain" entry in the basic setup should be left empty for most users' setups.
Is there an article on how to properly set up dnsmasq? I have found some information on the internet. I have made some changes and the router keeps hourly rebooting.
