What's new

[Beta] Asuswrt-Merlin 384.12 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.
some thoughts regarding dnssec @ dnsmasq.
does anyone ever need gost algos?
teaser:
upload_2019-6-17_23-41-18.png

https://rootcanary.org/test.html
 
Last edited:
I think the vast majority of people here never reboot unless upgrading firmware or making external device changes. IIRC, most people discussing periodic reboot seem to need it because of ISP issues.
Spot on. Perfectly fine with me. This is just the point I'm trying to make. Most people don't reboot. Therefor they don't find the bug either....
But...PLS don't try to convince me that there is no bug. There is...otherwise the router would work flowless. Most probable an ASUS fix that never will happen due do that only a few experience it.
 
Unfortunately I couldn't save the logs or do the test with the iperf, lack of time. But the version 384.11 _2 is better stability of packet forwarding. I don't like 384.12 _beta2.
 
some thoughts regarding dnssec @ dnsmasq.
does anyone ever need gost algos?
https://rootcanary.org/test.html
No.
On another note, 6RD works with DoT on beta2 without stubby.yml mods. Using CF I do not need to add the CF IPV6 resolvers (but I did it anyway). Looked in the change log but could not see anything that changed 6RD or Stubby.
 
What settings (DNS servers\browser..) are you using? never seen so much green
it's browser independent dns resolver on the router implementation (i.e dnsmasq).

bad news, so much green will not be available, rsa-md5, dsa*-sha1 are deprecated, gost2001 is obseleted by gost2012 which is not standartized.
for the rest there are good chances for the neares future.

On another note, 6RD works with DoT on beta2 without stubby.yml mods. Using CF I do not need to add the CF IPV6 resolvers (but I did it anyway). Looked in the change log but could not see anything that changed 6RD or Stubby.

thanks for update, got no time yet to dig into 6rd, sorry.
 
What settings (DNS servers\browser..) are you using? never seen so much green

What setup do you have to get all these tests to validate for you?


Sent from my iPhone using Tapatalk
 
What setup do you have to get all these tests to validate for you?


Sent from my iPhone using Tapatalk
Sorry but I don't see the allure, why have capability you won't ever use? When @themiron posted these results I knew it was going to tweak some heads here for sure. Thus the reaction from @RMerlin LOL. Your system is fine. :rolleyes::rolleyes:
 
Sorry but I don't see the allure, why have capability you won't ever use? When @themiron posted these results I knew it was going to tweak some heads here for sure. Thus the reaction from @RMerlin LOL. Your system is fine. :rolleyes::rolleyes:

Was simply curious to know that is all. It was a simple inquiry.


Sent from my iPhone using Tapatalk
 
ddns-start is still getting called a few times, before they would be 30 sec apart, now they all happen at once. And I think openvpn got started by the cron check (#CheckVPNServer1#) before being "started".

DDNS most likely gets started once by the initial clock sync, and a second time by the watchdog (I've never been able to fully understand how/why Asus implemented that watchdog code. That code is a mess because of its attempt at handling Dual WAN.). For now this is the best that can be done, as ddns will always need to be run whenever there's a WAN state change - my latest changes made sure that it was only run the first time after the clock got synced. It should be intelligent enough to rely on the cache and limit the number of outbound connections.

OpenVPN: the cron job only gets created at the end of the OpenVPN instance setup, so it's definitely not restarting OpenVPN before it's even running. Best I can tell is your DDNS takes nearly a minute to complete its update attempt, which delays the time sync instance where OpenVPN gets started. You have OpenVPN getting started by the WAN update as well, hence combined with the delayed initial start, both start attempts are within a very short period of time.

Getting a completely clean boot would require scrapping the whole implementation and rewriting it from scratch. Asuswrt (and its Tomato ancestor) was simply never designed to handle so many different services starting with so many dependencies. Asuswrt/Tomato have no concept of service or dependencies, so everything gets started based on events, and these events are not occuring in a linear way.
 
Best I can tell is your DDNS takes nearly a minute to complete its update attempt

I don't have anything locally that depends on ddns being set. Is it ok to run ddns updates in the background, or will it trigger multiple attempts if ddns-start finishes before /sbin/ddns_custom_updated is called?
 
Hi, upgraded to 'official' beta2 from 'test beta2' (a private build to fix the AX88 w/OVPN reboot delays already commented by Merlin) and all is running fine for almost 2 days already. .. great job @Merlin!
 
So I finally got the QoS bug it seems to have reset my priorities to default so when I went to re set them back up with the Asus app, I set the bandwidth to automatic but left FQ-Codel GG Asus.

I hope it's fixed soon.
 
Last edited:
I don't have anything locally that depends on ddns being set. Is it ok to run ddns updates in the background, or will it trigger multiple attempts if ddns-start finishes before /sbin/ddns_custom_updated is called?

Just let it run like it currently is, there's no harmful effect from having it run twice at boot time.
 
Status
Not open for further replies.

Latest threads

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