Beta Asuswrt-Merlin 386.4 beta is now available

[PorscheT]

Dirty flashed Beta 4 from 386.3 on AC88U and all is fine. Only issue is the known Adaptive QoS not working and OpenVPN speed is half (20 Mbps vs 40 Mbps) of what it used to be. Thanks for the continued support RMerlin.

 

[RMerlin]

Ok, When IPv6 is enabled, I will not be able to register DDNS

Known issue as indicated earlier, you will need to retest that after I apply the latest DDNS patches from Asus.

@RMerlin What's the best forum/email to write to Asus that what's holding me (and others I know) from upgrading to AXE11000 is the lack of your support?

Contacting Asus about this won't do anything. It's currently a technical issue, and both Asus and Broadcom are involved. Until they resolve this, nothing that can be done.

could you please clarify what the new hostname implementation means,

The only change is how this is stored in nvram. Functionality is 100% identical to 386.3.

 

[XIII]

Several times lost internet connectivity on wired and wireless devices in the last 24 hours

No idea whether it is related, but I see this in the system log:

Dec 20 09:40:00 lldpd[2173]: removal request for address of 10.8.0.1%107, but no knowledge of it

What does this mean?

Note: I use 192.168.x.y (not 10.a.b.c) locally...

Also weird: ssh was extremely slow for a while; though "top" did not show much CPU usage...

 

[ColinTaylor]

Several times lost internet connectivity on wired and wireless devices in the last 24 hours

No idea whether it is related, but I see this in the system log:

Dec 20 09:40:00 lldpd[2173]: removal request for address of 10.8.0.1%107, but no knowledge of it

What does this mean?

Note: I use 192.168.x.y (not 10.a.b.c) locally...

Those are normal messages. It just means that lldpd has noticed that interface 10.8.0.1 has disappeared, probably because the WAN interface has gone down. 10.8.0.1 is usually a VPN interface.

 

[skeal]

Dec 20 09:40:00 lldpd[2173]: removal request for address of 10.8.0.1%107, but no knowledge of it

This range is used by the OVPN Server on your router at least it is on mine.

 

[Elmer]

FYI. the disconnected bug due to the dns query stuff. you only need to enable it and add the dns info back into the entry box (or commit to nvram in shell) , reboot, then you can turn dns query back off and it still works correctly. at least in my case. dirty flashed from alpha2 to beta1

Did all of those things:

 

[heysoundude]

Non-functional ipv6-ddns is a bummer in the face of WireGuard being added to amtm...
we may be right on the bleeding edge here with the Asus folk, trying to make everything proper, right and correct.
Patience...this will get sorted as to be brilliant. just the first beta, after all.

 

[ColinTaylor]

Not a "bug" as such, and not specific to the beta... just a bit annoying.

Since the manually reserved hostnames were moved from the hosts file into dnsmasq.conf the router will not resolve any of these names if they are unqualified unless the device has already obtained its lease via DHCP.

This is usually not noticeable by clients like Windows as they try different query combinations with and without domain suffixes. But if doing a local lookup on the router itself (e.g. nslookup nuc) the command will fail because the hosts file doesn't contain a matching unqualified entry.

Unless it breaks something else might I suggest changing this line:

                fprintf(fp, "%s %s.%s\n", ip, hostname, lan_domain);

to this:

                fprintf(fp, "%s %s %s.%s\n", ip, hostname, hostname, lan_domain);

 

[Zastoff]

FYI. the disconnected bug due to the dns query stuff. you only need to enable it and add the dns info back into the entry box (or commit to nvram in shell) , reboot, then you can turn dns query back off and it still works correctly. at least in my case. dirty flashed from alpha2 to beta1

Did all of those things:
View attachment 37914

Reported on this in the 386.4 alpha tread with these lines:

dns.msftnci.com probes:
To permanently disable the probing enter this into the terminal, probing will stop immediately:
Code:
nvram set dns_probe=0;nvram set dns_probe_content=;nvram commit
To restore it, enter this:
Code:
nvram set dns_probe=0;nvram set dns_probe_content='131.107.255.255 112.4.20.71 fd3e:4f5a:5b81::1';nvram commit

The first line disable the probes and you will get internet status : disconnected in router gui Network Map tab but internet is still workning..
(Think the dns.msftnci.com probes is now needed for displaying internet status: connected from now on)
Did some more testing in the router gui in administration/system tab "Network Monitoring" unchecking the DNS Query box does not disable the probes when i check dnsmasq.log (same after rebooting the router also)

Spoiler: dnsmasq.log

19:43:27 dnsmasq[6768]: query[A] dns.msftncsi.com from 127.0.0.1
19:43:27 dnsmasq[6768]: cached dns.msftncsi.com is 131.107.255.255
19:43:42 dnsmasq[6768]: query[A] dns.msftncsi.com from 127.0.0.1
19:43:42 dnsmasq[6768]: cached dns.msftncsi.com is 131.107.255.255
19:43:47 dnsmasq[6768]: query[A] dns.msftncsi.com from 127.0.0.1
19:43:47 dnsmasq[6768]: cached dns.msftncsi.com is 131.107.255.255

 

[Elmer]

Reported on this in the 386.4 alpha tread with these lines:

dns.msftnci.com probes:
To permanently disable the probing enter this into the terminal, probing will stop immediately:
Code:
nvram set dns_probe=0;nvram set dns_probe_content=;nvram commit
To restore it, enter this:
Code:
nvram set dns_probe=0;nvram set dns_probe_content='131.107.255.255 112.4.20.71 fd3e:4f5a:5b81::1';nvram commit

The first line disable the probes and you will get internet status : disconnected in router gui Network Map tab but internet is still workning..
(Think the dns.msftnci.com probes is now needed for displaying internet status: connected from now on)
Did some more testing in the router gui in administration/system tab "Network Monitoring" unchecking the DNS Query box does not disable the probes when i check dnsmasq.log (same after rebooting the router also)

Okay, it's back, and thanks! Did this, per your instruction:
nvram set dns_probe=0;nvram set dns_probe_content=;nvram commit
then
nvram set dns_probe=0;nvram set dns_probe_content='131.107.255.255 112.4.20.71 fd3e:4f5a:5b81::1';nvram commit

No need to reboot - worked immediately.

 

[Yota]

You can override what Ip address detection methods gets used to register your ddns using custom scripts. Unfortunately certain environments may require users to do such. Where asuswrt may not be flexible in this regards, asuswrt-merlin branch is. Inadyn is very flexible in this regards. I suggest you take a look at the custom scripts wiki specifically sections that talk about ddns services. As for registering two addresses at the same time, it really all depends on your ddns service and whether inadyn will send them both in the same configuration segment. For dynv6, I have to do two separate instances, one for ipv4 and one for ipv6 to assure both get properly registered. I tried to do both at the same instance, but what would happen is only the first request would get sent, -i.e. if ipv4 was sent to go first, it would be the only one that got registered because inadyn saw it as successful ( or not needed if it didn't change) and did not finish the operation by updating the ipv6..

Thank you so much, I think a custom script may be able to achieve my needs.

 

[RMerlin]

Reported on this in the 386.4 alpha tread with these lines:

dns.msftnci.com probes:
To permanently disable the probing enter this into the terminal, probing will stop immediately:
Code:
nvram set dns_probe=0;nvram set dns_probe_content=;nvram commit
To restore it, enter this:
Code:
nvram set dns_probe=0;nvram set dns_probe_content='131.107.255.255 112.4.20.71 fd3e:4f5a:5b81::1';nvram commit

The first line disable the probes and you will get internet status : disconnected in router gui Network Map tab but internet is still workning..
(Think the dns.msftnci.com probes is now needed for displaying internet status: connected from now on)
Did some more testing in the router gui in administration/system tab "Network Monitoring" unchecking the DNS Query box does not disable the probes when i check dnsmasq.log (same after rebooting the router also)

Spoiler: dnsmasq.log

19:43:27 dnsmasq[6768]: query[A] dns.msftncsi.com from 127.0.0.1
19:43:27 dnsmasq[6768]: cached dns.msftncsi.com is 131.107.255.255
19:43:42 dnsmasq[6768]: query[A] dns.msftncsi.com from 127.0.0.1
19:43:42 dnsmasq[6768]: cached dns.msftncsi.com is 131.107.255.255
19:43:47 dnsmasq[6768]: query[A] dns.msftncsi.com from 127.0.0.1
19:43:47 dnsmasq[6768]: cached dns.msftncsi.com is 131.107.255.255

Since so many users seem to have messed with that parameter and are now flooding both this beta thread and the official Asuswrt threads about non-working notification, and that monitoring can no longer be disabled, I am considering hardcoding a default server to be used whenever that nvram is missing or empty.

 

[Yota]

no IPv6 / DDNS with Asus.

I think Asus is now starting to support IPv6 [1]. Of course, we may need to wait for beta 2 to know, because I can confirm that 386.3_2 and previous firmware does not support it. 386.4 beta 1 cannot use this feature due to some problems. nslookup www.asuscomm.com, this is Asus's own url, and you can see that their server has IPv6.

Have you ever tried another DDNS provider on your 386.3_2 firmware? EG No IP? That would rule out one area of concern / suspicion wouldn't it? That setup works for me i.e. FTTH and IPv4 / IPv6 from my ISP but no CGNAT remember and then DDNS IPv4 / IPv6 from No IP not Asus. I think we're using the same router too FWIW

Because the OpenVPN server of 386.3_2 does not support IPv6, I have never enabled IPv6 for my home network, so I have never enabled DDNS since my ISP no longer provides public IPv4.

I think DDNS should register all IP addresses anyway, even local addresses. Just like I can resolve my domain to any IP address, how to respond to that IP address is a matter of the client.

However, the OpenVPN client does not allow you to choose to only accept IPv6. In fact, they do have an option "Only IPv4 tunnel/Combined IPv4/IPv6 tunnel/no preference". So I must only provide IPv6 when registering for DDNS. Maybe I can implement it with a custom script, but I would prefer to see an option appear in the router GUI.

[1] https://www.snbforums.com/threads/a...beta-for-ipv6-ddns-and-ipv6-vpn-server.75829/

 

[Yota]

expect to have a working routable ipv6 internet connection coming from your openvpn tunnel

Another hypothesis waiting to be tested:
If I connect to my home network through an IPv6 tunnel, will it IPv6 to IPv4 locally? For example, can I ping 192.168.50.0/24 through the OpenVPN tunnel?

And, if the OpenVPN server does not route IPv6, will it route IPv4? So I can make a 6to4 internet connection through this IPv6 tunnel?


Edit:

Can I respectfully suggest that you refrain from posting speculations in this thread and just report actual issues/bugs discovered with this beta. That way RMerlin can see the wood for the trees.

You are right, please forgive me, this thread is full of noise from me. so sorry. I won't do this anymore, I will test it in next beta version.

 

[ColinTaylor]

Another hypothesis waiting to be tested:
If I connect to my home network through an IPv6 tunnel, will it IPv6 to IPv4 locally? For example, can I ping 192.168.50.0/24 through the OpenVPN tunnel?

And, if the OpenVPN server does not route IPv6, will it route IPv4? So I can make a 6to4 internet connection through this IPv6 tunnel?

Can I respectfully suggest that you refrain from posting speculations in this thread and just report actual issues/bugs discovered with this beta. That way RMerlin can see the wood for the trees.

 

[SomeWhereOverTheRainBow]

Why dont you test it and let us know.

 

[octopus]

After a couple of days i dicivered this, same in all Alpha builds. This is Beta1

May 5 07:05:10 dnsmasq-script[1313]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory
May 5 07:05:13 dnsmasq-script[1313]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory
Dec 20 16:57:03 dnsmasq-script[3270]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory
Dec 20 16:58:42 dnsmasq-script[3270]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory
Dec 20 19:49:44 dnsmasq-script[3270]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory
Dec 20 19:50:04 dnsmasq-script[3270]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory

But it's there:

octopus@RT-AX86U-EA08:/tmp/home/root# cat /jffs/nmp_vc_json.js

{"04:8C:9A:xx:xx:xx":{"mac":"04:8C:9A:xx:xx:xx","vendorclass":"HUAWEI:android:VOG"},"88:3D:24:xx:xx:xxx":{"mac":"88:3D:24:xx:xx:xx","vendorclass":"dhcpcd-6.8.2:Linux-3.8.13+:armv7l:Marvell"},"A08:07:xx:xx:xx":{"mac":"A08:07:xx:xx:xx","vendorclass":"HUAWEI:android:VOG"},"38:0B:40:xx:xx:xx":{"mac":"38:0B:40:xx:xx:xx","vendorclass":"dhcpcd-5.5.6"},"D4:5D:64:xx:xx:xx":{"mac":"D4:5D:64:xx:xx:xx","vendorclass":"MSFT 5.0"}}octopus@RT-AX86U-EA08:/tmp/home/root#

 

[ColinTaylor]

Since so many users seem to have messed with that parameter and are now flooding both this beta thread and the official Asuswrt threads about non-working notification, and that monitoring can no longer be disabled, I am considering hardcoding a default server to be used whenever that nvram is missing or empty.

What I'm struggling to understand is why the Network Monitoring > DNS Query check box even exists if un-checking it doesn't actually stop it (because its function is now mandatory). Maybe the checkbox should be removed and the Resolve Hostname/IP Addresses fields left permanently enabled (similar to the NTP Server field), and those fields cannot be null. Just a thought.

 

[ColinTaylor]

After a couple of days i dicivered this, same in all Alpha builds. This is Beta1

Dec 20 19:50:04 dnsmasq-script[3270]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory

But it's there:

I noticed the same message after doing a factory reset + initialise, because that deletes the file. By the time I logged into the router the file had been recreated and I never saw the message again.

 

[octopus]

I noticed the same message after doing a factory reset + initialise, because that deletes the file. By the time I logged into the router the file had been recreated and I never saw the message again.

I saw that after I rebooted after I have messed with Aimesh. File is there but dnsmasq seem not catch it.