Beta Asuswrt-Merlin 386.4 beta is now available

Status
Not open for further replies.

Elmer

Regular Contributor
AX88/Beta3: Still no ipv6 (native ATT); everything else is great including aimesh. Tried factory reset just to make sure. Didn't help and OMG is aimesh hard to get back online (listening Asus?). Thanks.
 

MattMofDoom

Occasional Visitor
I do note a curious thing though - initially IPv6 addresses are allocated to my Windows 11 PC that has an Intel AX210 wireless adapter, but they seem to disappear after a while.

Not observing the same issue with my Samsung S21 Ultra, so I'm not positive that this is related to the router and not something else. I'll test some more devices and keep an eye on it periodically.

E: May have been the result of turning on an OpenVPN server - not sure. After a disconnect/reconnect, the IPv6 address returned, so I just have to keep an eye on it for a while.
E2: No, it definitely disappeared after ~5 - 10 mins. Now only have a link local IPv6 address on the PC. Same happened on the S21 Ultra. Waiting to see on a laptop with Win11 and Intel Killer AX1650.
 
Last edited:

PDinDetroit

Regular Contributor
Dirty flashed beta 2 over 386.3_2 on Router/AiMesh Nodes (backed up router cfg and jffs first). WiFi was working almost entirely from main router instead of nodes (about 3 clients max connected to each node). Guest Network 1 was working from main router only. AiMesh would not display clients connected to some nodes, but Network Map -> View List would.

Dirty flashed 386.3_2 back on Router/AIMesh nodes and restored jffs/cfg. Everything back working how it was before, which was rock-solid.

ETA - Will look at beta 3 now that it is released.
 

MattMofDoom

Occasional Visitor
Observation - the IPv6 behaviour I'm seeing may be the result of roaming between AIMesh router and node, or vice versa. I haven't seen the same issue with the laptop using Intel Killer AX1650, which is configured to prefer the AIMesh router.

An ipconfig /renew6 does reallocate an IPv6 IP.

I'm going to turn off the OpenVPN server 'just in case' because I see it re-initialising periodically.
 

octopus

Part of the Furniture
Just updated to beta3.

But what happend here? just snapshot.

iptables -vL -t filter

Code:
Chain OUTPUT (policy ACCEPT 89842 packets, 74M bytes)
 pkts bytes target     prot opt in     out     source               destination         
  167 10835 OUTPUT_DNS  udp  --  any    any     anywhere             anywhere             udp dpt:domain u32 "0x0>>0x16&[email protected]>>0xf&0x1=0x0"
    0     0 OUTPUT_DNS  tcp  --  any    any     anywhere             anywhere             tcp dpt:domain u32 "0x0>>0x16&[email protected]>>0x1a&[email protected]>>0xf&0x1=0x0"
89842   74M OUTPUT_IP  all  --  any    any     anywhere             anywhere

Code:
Chain OUTPUT_DNS (2 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 logdrop_dns  all  --  any    any     anywhere             anywhere             STRING match  "|10706f697579747975696f706b6a666e6603636f6d00|" ALGO name bm TO 65535 ICASE
    0     0 logdrop_dns  all  --  any    any     anywhere             anywhere             STRING match  "|0d72666a656a6e666a6e65666a6503636f6d00|" ALGO name bm TO 65535 ICASE
    0     0 logdrop_dns  all  --  any    any     anywhere             anywhere             STRING match  "|1131306166646d617361787373736171726b03636f6d00|" ALGO name bm TO 65535 ICASE
    0     0 logdrop_dns  all  --  any    any     anywhere             anywhere             STRING match  "|0f376d667364666173646d6b676d726b03636f6d00|" ALGO name bm TO 65535 ICASE
    0     0 logdrop_dns  all  --  any    any     anywhere             anywhere             STRING match  "|0d386d617361787373736171726b03636f6d00|" ALGO name bm TO 65535 ICASE
    0     0 logdrop_dns  all  --  any    any     anywhere             anywhere             STRING match  "|0f3966646d617361787373736171726b03636f6d00|" ALGO name bm TO 65535 ICASE
    0     0 logdrop_dns  all  --  any    any     anywhere             anywhere             STRING match  "|1265666274686d6f6975796b6d6b6a6b6a677403636f6d00|" ALGO name bm TO 65535 ICASE
    0     0 logdrop_dns  all  --  any    any     anywhere             anywhere             STRING match  "|086861636b7563647403636f6d00|" ALGO name bm TO 65535 ICASE
    0     0 logdrop_dns  all  --  any    any     anywhere             anywhere             STRING match  "|076c696e77756469056633333232036e657400|" ALGO name bm TO 65535 ICASE
    0     0 logdrop_dns  all  --  any    any     anywhere             anywhere             STRING match  "|0f6c6b6a68676664736174727975696f03636f6d00|" ALGO name bm TO 65535 ICASE
    0     0 logdrop_dns  all  --  any    any     anywhere             anywhere             STRING match  "|0b6d6e627663787a7a7a313203636f6d00|" ALGO name bm TO 65535 ICASE
    0     0 logdrop_dns  all  --  any    any     anywhere             anywhere             STRING match  "|077131313133333303746f7000|" ALGO name bm TO 65535 ICASE
    0     0 logdrop_dns  all  --  any    any     anywhere             anywhere             STRING match  "|057371353230056633333232036e657400|" ALGO name bm TO 65535 ICASE
    0     0 logdrop_dns  all  --  any    any     anywhere             anywhere             STRING match  "|077563746b6f6e6503636f6d00|" ALGO name bm TO 65535 ICASE
    0     0 logdrop_dns  all  --  any    any     anywhere             anywhere             STRING match  "|0e7a786376626d6e6e666a6a66777103636f6d00|" ALGO name bm TO 65535 ICASE
    0     0 logdrop_dns  all  --  any    any     anywhere             anywhere             STRING match  "|0a65756d6d6167766e627003636f6d00|" ALGO name bm TO 65535 ICASE

Chain OUTPUT_IP (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 logdrop_ip  all  --  any    any     anywhere             193.201.224.0/24   
    0     0 logdrop_ip  all  --  any    any     anywhere             vriezekolk.org     
    0     0 logdrop_ip  all  --  any    any     anywhere             li1019-134.members.linode.com
    0     0 logdrop_ip  all  --  any    any     anywhere             190.115.18.28       
    0     0 logdrop_ip  all  --  any    any     anywhere             51-159-52-250.rev.poneytelecom.eu
    0     0 logdrop_ip  all  --  any    any     anywhere             190.115.18.86
 

RMerlin

Asuswrt-Merlin dev
Disabling IPv6 DDNS support to all DDNS providers including Asus, or,
Asus's DDNS is the only one with IPv6 support.

AX88/Beta3: Still no ipv6 (native ATT);
Look at your system log for error messages, and double check things on the ISP side. Native PD is working fine here and for many other users.

But what happend here? just snapshot.
Security-related rules Asuswrt adds. I was keeping these disabled until now, I decided to re-enable them because I don't know which other private rules may also be added by these closed source functions (I'm aware that at least in the past there were a few related to Zen Wifi models).
 

ColDen

Regular Contributor
Updated from 386.4 beta 2 to 386.4 beta 3 two hours ago and, has previously mentioned before, did not noticed any issues at this time on my RT-AC86U router.

Thanks RMerlin.
 

learning_curve

Regular Contributor
Asus's DDNS is the only one with IPv6 support.
This is the bit I don't understand (properly) yet. Asus uses inadyn within my router (which does support both IPv4 and IPv6). There are several DDND providers who do provide IPv6 support. No-IP who I use, announced this way back in 2019: https://www.noip.com/blog/2019/11/03/ip-now-offers-ipv6-dynamic-dns/ but other providers state this very clearly too e.g. https://dynv6.com For clarity, it works fine (for me) in Beta2, but I'm not referring to IPv6 DDNS over VPN or anything more intricate like in this thread: https://www.snbforums.com/threads/ipv6-ddns-noip-com-and-vpn-server-for-cg-nat-ipv4.71846/
I've obviously missed something, but what/where?
 

RMerlin

Asuswrt-Merlin dev
I've obviously missed something, but what/where?
Asus only recently switched to inadyn, by integrating my code - and I didn't implement any IPv6 support. They only started implementing it for their own service a few months ago. It's not just a matter of flipping on a switch, it requires dedicated development.

Inadyn itself would also need to implement support for other providers, that's not Asus' responsability.
 

MattMofDoom

Occasional Visitor
Router IPv6 is stable and continues to work as expected. It's only the clients that are dropping off. Checked with an Xbox and same effect.

Not much I can do with it. The IPv6 page as of now shows only a few clients, including an iPhone, a Surface Laptop Go, and what looks like a bunch of Google Home devices. As I refresh I see some of them drop off. I have quite a high number of devices on my home network (~50) so would definitely expect to see more.

I have a lot of features configured including parental control and time scheduling, a guest network for Xboxes to work around an issue I was encountering, adaptive QoS, OpenVPN (disabled), etc. No real clues appear to show up in the logs - just periodic inadyn updates for Asus DDNS and auth/deauth events for wireless devices.

I've turned on the Dhcpv6-Client/Operational logs on my PC to see if I can get any clue from here when it drops off.
 

jksmurf

Regular Contributor
There is no more dhcp_hostnames with 386.4.

Hi, I have been saving and copying back to the Router with updated F/W, reset, these files: dhcp_staticlist, custom_usericon and custom_clientlist. All the listed users come up and on first reboot it seemed all was workign fine as per old F/W. However accessing the WebUI on several different occasions I see two things, (a) Missing icons and (b) an odd extended row where the drop down list used to be.

I cleared all my Browser Caches but to no avail. Has anyone else seen this? It is not a massive issue, just a wee bit annoying.

 

Attachments

  • DHCP_Errors.jpg
    DHCP_Errors.jpg
    83.4 KB · Views: 113

MattMofDoom

Occasional Visitor
Okay so it looks like the drop of IPV6 address happens after 10 minutes, with the initiating event 51038:

The information refresh time has expired, hence triggering a new inform packet on the interface 20.

An event 51026 is logged:

A valid reply is received for Info-request on the interface 20. Status code is 0x0

and followed by event 60001:

PERFTRACK (DHCINFORMATIONREQUEST): Options received on the IPv6 interface 20.

and event 51050:

DNS registration has happened for the interface 20. Status Code is 0x0. DNS Flag settings is 8.


So I 'think' this is a problem with the stateless configuration. I'm not an expert on this.

I'm switching the router to stateful.
 

RMerlin

Asuswrt-Merlin dev
I see two things, (a) Missing icons and (b) an odd extended row where the drop down list used to be.
That typically indicates an invalid character in a device name, or a corrupted stored setting.
 

jksmurf

Regular Contributor
That typically indicates an invalid character in a device name, or a corrupted stored setting.
Thank you @ RMerlin.

Looking at my static list though, they are all either Lower or Upper Case, although two have Hyphens and one or two are 19 characters long. No other special character (I had a little look for "invalid character" AND asus AND Router). Is a Hyphen invalid? If none of those I will have to redo the list manually.

Cheers

k.
 

alchemy

Occasional Visitor
RT-AC86U Beta2 to 3, all looks good. Thanks!
 

MattMofDoom

Occasional Visitor
More or less as expected - switching to stateful mode means the IPv6 address has been retained over 10 mins, since expiry is now 86400 seconds. Not sure exactly why, but the Samsung S21 Ultra doesn't appear to like stateful mode and isn't receiving an IPv6 address.

PC and laptop appear to be good. On reflection, I'm not sure guest networks offer IPv6, so no point testing with Xbox.

Good enough for now at least. Hopefully the info I've been able to gather helps ..
 

arewhy

Occasional Visitor
Upgraded from beta 2 on AX11000 and AX86U. IPV6 Native PD working out of the box now that the missing chain was fixed:) Thank You @RMerlin!!
I definitely noticed Security-related rules Asuswrt adds to the ipv4 and ipv6 tables!
 

SomeWhereOverTheRainBow

Part of the Furniture
Asus only recently switched to inadyn, by integrating my code - and I didn't implement any IPv6 support. They only started implementing it for their own service a few months ago. It's not just a matter of flipping on a switch, it requires dedicated development.

Inadyn itself would also need to implement support for other providers, that's not Asus' responsability.
Asus should not attempt to leap their IPV6 functionality until they learn to crawl it first. There is a lot lacking under the ASUSwrt-hood that needs implemented or enabled in regards to Asuswrt having an effective modern ipv6 implementation, but it would require Asuswrt devs to over-hall a lot of the internals. In this regard it is completely understandable why you have disabled their broken logic.
 

Tech9

Part of the Furniture
There is a lot lacking under the ASUSwrt-hood that needs implemented or enabled in regards to Asuswrt having an effective modern ipv6 implementation

Since we talk about Asus routers and Asuswrt, could you please share the details you know here:


It will be good to know if enabling IPv6 in Asuswrt is actually a good thing. Few pages of beta thread turned into IPv6 score competition.

Thank you!
 
Status
Not open for further replies.

Sign Up For SNBForums Daily Digest

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