What's new

[Beta] Asuswrt-Merlin 384.7 Beta is now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
No errors on service restart_dnsmasq:
Code:
Sep 21 14:16:20 rc_service: service 17303:notify_rc restart_dnsmasq
Sep 21 14:16:20 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:16:23 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:16:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:16:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:16:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Thanks! There was an an issue with /jffs/scripts/dnsmasq.postconf. I had edited this file for stubby testing. The error was self-induced! It is no longer throwing the SIGTERM error! :cool:
 
Last edited:
@Xentrk, apparently I did loose dns resolving after manually restarting dnsmasq. Had to reboot my router to get it working again, not sure what happened. It looks like dnsmasq is being restarted every 30 seconds, but I don't know whether this is related to the current beta or to Diversion, as I don't have clue why and I don't see any errors either...

Code:
Sep 21 14:16:20 rc_service: service 17303:notify_rc restart_dnsmasq
Sep 21 14:16:20 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:16:23 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:16:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:16:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:16:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:17:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:17:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:17:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:17:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:17:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:17:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:18:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:18:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:18:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:18:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:18:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:18:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:19:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:19:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:19:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:19:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:19:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:19:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:20:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:20:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:20:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:20:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:20:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:20:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:21:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:21:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:21:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:21:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:21:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:21:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:22:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:22:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:22:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:22:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:22:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:22:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:23:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:23:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:23:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:23:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:23:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:23:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:24:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:24:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:24:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:24:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:24:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:24:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:25:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:25:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:25:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:25:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:25:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
 
@Xentrk, apparently I did loose dns resolving after manually restarting dnsmasq. Had to reboot my router to get it working again, not sure what happened. It looks like dnsmasq is being restarted every 30 seconds, but I don't know whether this is related to the current beta or to Diversion, as I don't have clue why and I don't see any errors either...

Code:
Sep 21 14:16:20 rc_service: service 17303:notify_rc restart_dnsmasq
Sep 21 14:16:20 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:16:23 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:16:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:16:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:16:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:17:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:17:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:17:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:17:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:17:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:17:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:18:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:18:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:18:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:18:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:18:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:18:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:19:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:19:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:19:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:19:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:19:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:19:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:20:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:20:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:20:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:20:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:20:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:20:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:21:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:21:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:21:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:21:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:21:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:21:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:22:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:22:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:22:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:22:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:22:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:22:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:23:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:23:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:23:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:23:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:23:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:23:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:24:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:24:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:24:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:24:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:24:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:24:35 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:25:03 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:25:03 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 14:25:05 Diversion: restarted Dnsmasq to apply settings, from /jffs/scripts/dnsmasq.postconf
Sep 21 14:25:33 rc_service: watchdog 292:notify_rc start_dnsmasq
Sep 21 14:25:33 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s

:eek: Appears to be a 30 second gap pattern in the messages.
 
It looks like dnsmasq is being restarted every 30 seconds

:eek: Appears to be a 30 second gap pattern in the messages.

It does, doesn't it? Not sure whether this is watchdog or Diversion related, but it's gone after a reboot. Could it be related to being connected to a VPN server while restarting dnsmasq or doesn't that have to do anything at all with it?
 
It does, doesn't it? Not sure whether this is watchdog or Diversion related, but it's gone after a reboot. Could it be related to being connected to a VPN server while restarting dnsmasq or doesn't that have to do anything at all with it?
Being connect over the VPN server shouldn't matter. watchdog appears to be Asus code and not specific to Asuswrt-Merlin 384.7 beta 1. Just keep an eye on it for now.
 
What about this:
https://github.com/RMerl/asuswrt-merlin.ng/tree/master/release/src/router/acme-client-portable

Seems to me it's an acme-portable client using classic linux-way 'webroot' challenge method.

No idea if it uses it and how it does. Throughout the LE development, Asus went down different avenues. At one point they even had a whole dedicated lighttpd instance included with the goal of handling http-based validation.

The core of their implementation lies in https://github.com/RMerl/asuswrt-merlin.ng/tree/master/release/src/router/libletsencrypt .
 
Hello,
Anyone else seeing the dnsmasq SIGTERM errors in system log?

Code:
Sep 21 03:52:05 RT-AC88U-8248 rc_service: service 9996:notify_rc updateresolv
Sep 21 03:52:05 RT-AC88U-8248 dnsmasq[21552]: exiting on receipt of SIGTERM
Sep 21 03:52:05 RT-AC88U-8248 custom_config: Appending content of /jffs/configs/dnsmasq.conf.add.
Sep 21 03:52:05 RT-AC88U-8248 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Sep 21 03:52:05 RT-AC88U-8248 ovpn-client4[21126]: SIGTERM[soft,auth-failure] received, process exiting
Sep 21 03:52:05 RT-AC88U-8248 dnsmasq[10003]: started, version 2.80test4 cachesize 1500
Sep 21 03:52:05 RT-AC88U-8248 dnsmasq[10003]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset no-auth DNSSEC no-ID loop-detect no-inotify no-dumpfile
Sep 21 03:52:05 RT-AC88U-8248 dnsmasq[10003]: warning: interface tun22 does not currently exist
Sep 21 03:52:05 RT-AC88U-8248 dnsmasq[10003]: warning: interface pptp* does not currently exist
Sep 21 03:52:05 RT-AC88U-8248 dnsmasq[10003]: asynchronous logging enabled, queue limit is 5 messages

That's not an error, that's your router issuing a restart of dnsmasq - see the first line of your quoted code. It's issued by a change to your DNS/hostname configuration.

Small typo in the log file.. waiting spelled as waitting

rc_notify code is closed source.
 
First, I'm running 384.7-Beta1 on my "real" ASUS RT-AC68U.

Can someone explain what the Highest ... Lowest "buttons" do on the Bandwidth monitor tab of the Adaptive QOS panel as shown below?

upload_2018-9-21_18-45-11.png


I read somewhere that you could drag one of those "buttons" and drop it on a device icon but I don't actually understand what that does in relation to Adaptive QOS. For example, I dragged the Highest "button" to my raspberrypi3 because I use that with Unbound and Pi-Hole as my DNS resolver. I did that when I had Adaptive QOS turned on. However, I turned off Adaptive QOS to troubleshoot something but I notice my device icons still reflect those speed categories.

So, do these speed categories operate independent of Adaptive QOS? And what exactly do they do?
 
Last edited:
First, I'm running 384.7-Beta1 on my "real" ASUS RT-AC68U.

Can someone explain what the Highest ... Lowest "buttons" do on the Bandwidth monitor tab of the Adaptive QOS panel as shown below?

View attachment 14526

I read somewhere that you could drag one of those "buttons" and drop it on a device icon but I don't actually understand what that does in relation to Adaptive QOS. For example, I dragged the Highest "button" to my raspberrypi3 because I use that with Unbound and Pi-Hole as my DNS resolver. I did that when I had Adaptive QOS turned on. However, I turned off Adaptive QOS to troubleshoot something but I notice my device icons still reflect those speed categories.

So, do these speed categories operate independent of Adaptive QOS? And what exactly do they do?

AFAIK it's to prioritize devices when using QOS. When QOS is disabled it should have no effect but maybe I'm mistaken..
 
hmm seems oddly with this beta that adjusting dhcp query frequency and turning off spanning tree protocol seem to allow my main pc to show up my nas and my xbox one first gen to get open nat, odd, i dont understand why setting dhcp query frequency to normal, lets my main pc see my nas via ftp, even though all my spare pc and lap top could accesses the nas via ftp, odd, the xbox one and the main pc xbox app had mod nat and the other pc and lap top ahd open in the xbox app.
does it restart the firewall when you adjust the query frequency?
 
It looks like dnsmasq is being restarted every 30 seconds

This most likely means dnsmasq is unable to start, so it gets restarted by the watchdog. Double check your dnsmasq config file.
 
Off-topic posts removed. Please stay on the topic of testing the 384.7 beta releases.
 
Does anyone know why I get the following using dnsomatic?

start_ddns: update WWW.DNSOMATIC.COM default@dnsomatic.com, wan_unit 0
Sep 22 16:22:20 inadyn[16920]: Failed resolving hostname all.dnsomatic.com: Name or service not known

Do you have that address entered on the webui? If not, then it seems inadyn's dnsomatic support requires specific content.
 
Do you have that address entered on the webui? If not, then it seems inadyn's dnsomatic support requires specific content.
It seems dnsomatic needs a blank hostname or it will throw that error, do you know what file it writes to so I can edit it out and test it?
 
Does this allow for OverClocking the SoC and the output to 200mW?

No. CPU clock is overridden at boot time, and power control is forbidden by regulations.
 
It seems dnsomatic needs a blank hostname or it will throw that error, do you know what file it writes to so I can edit it out and test it?

/etc/inadyn.conf. You can override it by copying the existing file to /jffs/configs/ then editing it. When the DDNS server is started, the config file will be replaced by the one in /jffs.

Other DDNS services would cause Inadyn to complain if there was no hostname provided, so I'll have to dig through the documentation to figure out if DNSomatic is a special case.
 
No. CPU clock is overridden at boot time, and power control is forbidden by regulations.
Is there any way to modify the regulations code inside the router? That's all it has to be right, just some code?

What about a way to make the clock stick after boots?
 
Is there any way to modify the regulations code inside the router? That's all it has to be right, just some code?

What about a way to make the clock stick after boots?

By regulations, I mean legal regulations. It's illegal to bypass the power limitations that are allowed in one's region, therefore I don't support it.

As for the clock, some people were able to bypass it through scripting. I don't remember the details however, you will have to do a forum search to track down previous discussions about it.
 
Status
Not open for further replies.

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top