What's new

[Beta] Asuswrt-Merlin 384.11 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!

Embarrassed to ask this, but how could I tell if the B1b "took"? On Tools|System information I'm showing a Friday build--should that be Saturday?
Since he says he didn't recompile the code itself, I suspect the Friday build date would be expected, if not confusing. I'm waiting for some hashes to be published before I update, so I can't say for certain. I think of it like re-zipping a document. Didn't change the document, just re-zipped it (kinda sorta).
 
Embarrassed to ask this, but how could I tell if the B1b "took"? On Tools|System information I'm showing a Friday build--should that be Saturday?

There's no way to tell, it's the exact same code, only the TRX file was regenerated.

If you can get into the GUI 9’ your ac87u, then you are fine.

Filesystem corruption was at different locations. In the RT-AC87U case, it was the snmp libraries located in /usr/lib/ that were corrupted. The following command would cause read errors on the RT-AC87U:

Code:
cp /usr/lib/*snmp* /tmp/
 
Have not experienced any trouble on my 87u but doing the update to the newer beta1 right now

Edit:
Done
Logged in and out a lot today(on first beta1) testing out different dns servers (been bored)
Can't see any difference in the compiled date/time of firmware
All is up and running ;)
 
Last edited:
Small Q, When I use DoT with VPN Client and select DNS Exclusive with a policy rule 192.168.1.0/24. I will get 1 DNS from my VPN provider (dns leaktest). When I use Exclusive and Redirect traffic set to ALL. I will get 1 DNS from my VPN provider plus a bunch DNS numbers from Cloudfare (dns Leaktest). In case of DNS (leaks) what do you recommend?
 
Have some canadian pride, @skeal: use time.nrc.ca or time.chu.nrc.ca
and I think on the ntp site, USask has a few ntp servers, which would likely be your best bet for locality/short ping.

Code:
This one gives me the best ping.

C:\Users\i7>ping 0.ca.pool.ntp.org

Pinging 0.ca.pool.ntp.org [54.39.13.155] with 32 bytes of data:
Reply from 54.39.13.155: bytes=32 time=10ms TTL=50
Reply from 54.39.13.155: bytes=32 time=10ms TTL=50
Reply from 54.39.13.155: bytes=32 time=10ms TTL=50
Reply from 54.39.13.155: bytes=32 time=10ms TTL=50

Ping statistics for 54.39.13.155:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 10ms, Average = 10ms
 
Small Q, When I use DoT with VPN Client and select DNS Exclusive with a policy rule 192.168.1.0/24. I will get 1 DNS from my VPN provider (dns leaktest). When I use Exclusive and Redirect traffic set to ALL. I will get 1 DNS from my VPN provider plus a bunch DNS numbers from Cloudfare (dns Leaktest). In case of DNS (leaks) what do you recommend?

Use Exclusive and policy rules, it will be stricter than using All.
 
Code:
This one gives me the best ping.

C:\Users\i7>ping 0.ca.pool.ntp.org

Pinging 0.ca.pool.ntp.org [54.39.13.155] with 32 bytes of data:
Reply from 54.39.13.155: bytes=32 time=10ms TTL=50
Reply from 54.39.13.155: bytes=32 time=10ms TTL=50
Reply from 54.39.13.155: bytes=32 time=10ms TTL=50
Reply from 54.39.13.155: bytes=32 time=10ms TTL=50

Ping statistics for 54.39.13.155:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 10ms, Average = 10ms

Great, find the best/fasted for you.
There are plenty of options.

If more people paid attention to and implemented clocking properly, the interweb experience would be better for everyone, so spread the word, fellow disciples.


Sent from my iPhone using Tapatalk
 
I have regenerated all the SDK6/SDK7 firmware images with the new compression option disabled. They should appear on Onedrive/Sourceforce in a little while. The ZIP filename will have beta1b . The firmware version will still show as beta1 - I haven't recompiled the code, simply rebuilt the .trx files with the mksquashfs change.

I recommend everyone to upgrade, just in case there might also be filesystem corruption issues with other models.

I haven't rebuilt the HND models (AC86U and AX88U) because they use ubifs, as well as a newer kernel, so in theory these should be fine.

Interesting thing is the corrupted images will read just fine on my Linux VM, but mounting them on a loopback on the routers themselves will generate read errors while accessing certain files. I suspect it could be a bug in the older kernel, or an incompatibility between mksquashfs and these kernel releases.

I'm not 100% sure this was the cause, but it's what made the most sense (unfortunately, I cannot reproduce the problem every time I build an image). Only testing in the long run will confirm this was the issue.

a few hours ago updated RT-AC5300 and RT-AC3100 <----- both seem to be in good working order so far no issues to report.
 
I just bought an RT-AX88U this week to replace my RT-AC66U B1. Then gave my RT-AC66U B1 to my brother. Looking forward to installing this beta build on the RT-AX88U. Just had one question. I know AiMesh is not supported. Which is fine because I will only have this one router anyways. What I was curious to know was if any other features are missing or not functioning correctly well using Merlin. Only ask because this is the most expensive router I've ever purchased. Also thanks for all the hard work you put into these builds for us. Have been using your firmware for several years now.

Except for AiMesh, Merlin is normally at the leading edge for fixes & enhancements. Try it, you won’t go back!
If I was setting up a new AX88U, a Merlin install would be my first job. (As it was with my 86).
 
Can anyone confirm if the network map is stable on the ac86u, (devices disappearing/reappearing). I believe this has the fix from Asus that sorts that finally.

Everything that should be there, is.
I’m not seeing any issues....
 
yes it is better to use dnssec via dnsmasq as it relies more on hard coding for validation and handles caching better. --- I like the default caching is set to 1500 nice...

- on top of this alot of the dnssec features built into stubby are still under development-- makes me feel like it is not 100%

But DNSSEC still has to be enabled in the GUI for it to work?
Or, no longer required to be enabled, it will just work by default?
 
Reason/s?
Just interested to know.....
It bypasses your DNS configuration. For example, if you are using CleanBrowsing, the DoH Firefox would use unfiltered Cloudflare.
 
I updated to beta1b and everything seems to be fine. I had no issues with the initial beta. Thanks for the heads up and new builds, RMerlin!
 
a few hours ago updated RT-AC5300 and RT-AC3100 <----- both seem to be in good working order so far no issues to report.

Which one did you have? Did the 5300 have the same problem of no GUI access after flash? Thought it was only 3100+87U.
 

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