Asuswrt-Merlin 378.56 Beta 2 is out

[RMerlin]

Merlin,
I am wondering if you can have a look at the Administration-System page bug that I wrote about in post # 130.
Tx

In due time. I didn't have the time yet.

 

[RMerlin]

I'm getting the same in 378.56 beta2 with a AC87U...

Reduce your syslog priority from DEBUG to something lower on the System -> Administration page.

 

[RMerlin]

The dnscrypt files are from lancethepants. This configuration worked without fail on .55. With beta 1 and 2 both, NTP will not work. It doesn't matter if I populate my hosts.add file with several pool.ntp.org entries, enter in an actual IP address that resolved to pool.ntp.org in the GUI, and it doesn't matter what DNS servers (my ISP, Google, Cisco, etc) that I enter into the GUI. I even tried turning on DNS filtering in AI Protection and then selecting the "No Filtering" option. I'm out of town and won't be home until this afternoon and I'm a bit nervous to be messing around remotely with this to get a syslog.. that I might bork my network and not have remote access. If this information doesn't help, I should be able to get a syslog later this evening.

Your issue is specific to dnscrypt and its associated customization. Jump into the DNSCrypt thread, there are talks there about how to resolve its issues. This isn't a bug in beta 2.

 

[shooter40sw]

Hi @RMerlin I got the N66U I know the firmware is not up yet, so I hope its soon, I´m using the dnsmasq on the USB, everything is working fine now but if I implement this script in the post-mount do I have to delete these lines from the dnsmasq.conf.add file? or just delete the log-facility from there?
Thanks

log-facility=/tmp/mnt/sda1/logs/dnsmasq.log
log-async
log-queries

Same problem as the two other users there. Look at the postconf script I posted as a safer way to use a USB-stored logfile.

The good news is that it solves the mystery of the randomly failed ntp update - everyone affected so far were storing their dnsmasq on a USB disk, which wasn't mounted at the time the initial dnsmasq was launched.

 

[MXM]

This message should only be logged if you have Syslog set to Debug level. Check under Administration -> System what level you are using.

Also make sure you are running Beta 2, as previous releases were logging these with a lower priority level.

RMerlin,

I have the Default Message Log Level set to INFO
and Log Only Messages More Urgent Than ALL

Is that why they are popping up?

Thanks,
M

 

[XIII]

Your issue is specific to dnscrypt and its associated customization. Jump into the DNSCrypt thread, there are talks there about how to resolve its issues. This isn't a bug in beta 2.

@RogueSpear: if you find the solution, can you please share it?

I'm in the same boat as you... (ntp issues with 378.56 Beta 1/2, dnscrypt working fine with 378.55)

My current configuration can found in this Beta 1 post: #53

 

[RMerlin]

RMerlin,

I have the Default Message Log Level set to INFO
and Log Only Messages More Urgent Than ALL

Is that why they are popping up?

Thanks,
M

Yes, change the value of "Log Only Messages More Urgent" - ALL means it logs everything.

 

[RMerlin]

Hi @RMerlin I got the N66U I know the firmware is not up yet, so I hope its soon, I´m using the dnsmasq on the USB, everything is working fine now but if I implement this script in the post-mount do I have to delete these lines from the dnsmasq.conf.add file? or just delete the log-facility from there?
Thanks

log-facility=/tmp/mnt/sda1/logs/dnsmasq.log
log-async
log-queries

postconf, not post-mount.

You can keep the two other config lines in the .add file, however it would be cleaner to also move them to the postconf, by adding two more pc_append lines for them.

 

[shooter40sw]

Ok Thanks, so I´ll have to make a dnsmasq.postconf with the script that you said and another dnsmasq.add with the other code, like the adblock by host files... correct?

postconf, not post-mount.

You can keep the two other config lines in the .add file, however it would be cleaner to also move them to the postconf, by adding two more pc_append lines for them.

 

[RMerlin]

Ok Thanks, so I´ll have to make a dnsmasq.postconf with the script that you said and another dnsmasq.add with the other code, like the adblock by host files... correct?

That would work, yes.

 

[shooter40sw]

Sorry for asking so much, but if I place everything in one code, would every line I add would it have the $CONFIG at the end?
pc_append "log-async" $CONFIG and so on?
and to get it clean, what else could go in the file? I pretty much have the lonelycoder config except thath I use dnscrypt...
I ask because I was reading on the postconf config if you mess up a manual reset to factory defaults is needed, and I really dont want to do that

That would work, yes.

 

[thelonelycoder]

postconf, not post-mount.

You can keep the two other config lines in the .add file, however it would be cleaner to also move them to the postconf, by adding two more pc_append lines for them.

Thanks Merlin, it works now as advertised! I am running the beta-2 again.

For the benefit of others here's my /jffs/scripts/dnsmasq.postconf

#!/bin/sh
CONFIG=$1
source /usr/sbin/helper.sh

if [ -d "/mnt/sda1" ]; then
        pc_append "
log-facility=/mnt/sda1/dnsmasq.log" $CONFIG
        pc_append "log-async" $CONFIG
        pc_append "log-queries" $CONFIG
fi

Note the line break in pc_append "log-facility=/mnt/sda1/dnsmasq.log" $CONFIG
This is to force a new line in the dnsmasq.conf. As I have a commented out entry at the end of dnsmasq.conf.add it would append log-facility=/mnt/sda1/dnsmasq.log to that line.

With the line break it works just fine.

 

[RogerSC]

This is from 56_Beta1 system log, but that forum is closed. Is this log message something I should be concerned about:

Oct 21 23:41:59 dhcp6 client: bound address 2001:558:6045:84:1579:63e9:4b5c:f8e6/128, prefix 2601:647:cb00:b37f::/64

Kind of non-self explanatory *smile*.

Thanks.

 

[RMerlin]

Note the line break in pc_append "log-facility=/mnt/sda1/dnsmasq.log" $CONFIG
This is to force a new line in the dnsmasq.conf. As I have a commented out entry at the end of dnsmasq.conf.add it would append log-facility=/mnt/sda1/dnsmasq.log to that line.

Try using "\n" at the start of the line instead to insert a line break. I can't remember if those are escaped or not, you will have to try it.

 

[RMerlin]

This is from 56_Beta1 system log, but that forum is closed. Is this log message something I should be concerned about:

Oct 21 23:41:59 dhcp6 client: bound address 2001:558:6045:84:1579:63e9:4b5c:f8e6/128, prefix 2601:647:cb00:b37f::/64

Kind of non-self explanatory *smile*.

Thanks.

Looks to me like a typical IPv6 IP and prefix delegated to you, but I'm no expert on IPv6 (all I have here is access to a 6in4 tunnel).

 

[eddiez]

Cause is likely to be the same

But this addresses Windows Event Log messages.

The messages I am seeing are in the router syslog...

Thanks.

 

[RogerSC]

Looks to me like a typical IPv6 IP and prefix delegated to you, but I'm no expert on IPv6 (all I have here is access to a 6in4 tunnel).

Yeah, I'm not sure if this is a complaint from some client software on the router, or just a "this is what I did" kind of thing. I'm not real worried, since it doesn't have "fatal error, exiting" emblazoned on it *smile*, just wondering why the firmware thought that I should see it.

Thanks.

 

[RMerlin]

I think I found a bug on the Administration-System page. I am still in 378.56bata 1 but I am not sure that this bug was fixed in beta 2:

At the bottom of the page when trying to delete the "client list" of "Specified IP addresses" - after deleting all of them and pressing Apply button I am receiving an error: "http://192.168.1.1 Fields cannot be blank". As a result once you specified up to 4 addresses to access the router, you can only delete 3 of them but at least one must be in the table! This is preventing access to the router from anywhere but the specified client!

This is normal and by design. If you enable the access list but don't enter at least one IP, it means you will completely lock yourself out of the router, potentially requiring a factory default reset to regain access to it. The router then insists that you enter at least one IP in the list.

If you decide not to use the access list anymore, you must disable the option.

 

[fafot]

RMerlin, thank you and sorry for bothering you!
Sound very logical I did not notice that there is the ability to disable this option by using the "Allow only specified IP address" set to NO.

 

[tiko]

That bug was solved in beta 2, you can go ahead and test it whenever you can afford to reboot your router.

I just upgraded to beta 2, and now it works. Thanks!