Beta Asuswrt-Merlin 3004.388.4 beta is now available

[RMerlin]

I loaded it up this morning and it's been running fine for around 8 hours.
Then I thought I'd test a problem that Beta3 should fix (no DDNS update on WAN reconnect) so I unplugged my WAN connection, waited a few minutes and reconnected.

Asus made a lot of changes to the DDNS handling, including that new "timed recovery" feature. I fixed all the issues I could observe, however I guess there are still issues remaining with that retry handling that I couldn't reproduce.

As a simple workaround for now, reboot your router.

Which DDNS provider do you use? Asus also handles that differently for asuscomm.net vs other providers.

 

[Damit1]

Just upgraded Beta2, into B3.

Small hiccup on first load for AX56U,
had to reboot each unit apart so it will sync.
Ax56u eventually was reset and reconnect

Now it is been 30m after the upgrade.
Small issues of clients re-connect.
Will do a physical rebooot in 20m or so, and report back

 

[alan6854321]

As a simple workaround for now, reboot your router.

Which DDNS provider do you use? Asus also handles that differently for asuscomm.net vs other providers.

I found an even simpler workaround - I hit the "Apply" button on the WAN/DDNS page which forced an update and stopped the 30 second restarts.

I'm using WWW.NO-IP.COM as a DDNS provider.

 

[bartj12]

Beta 3 on my AX86U with AX86S (on stock firmware) and RP-AX58 (on stock firmware) as nodes. clean issuelog on warning.

 

[Damit1]

Well, did 2 system restarts.
Physcial one and via GUI.
Sadly, 5Ghz takes more time now to start, not sure why or if related to anything.

In Beta 2 it used to be pretty fast.
It was trully better then.
I hope on the stable version it will be resolved somehow.

 

[SuperFreaky]

Well, did 2 system restarts.
Physcial one and via GUI.
Sadly, 5Ghz takes more time now to start, not sure why or if related to anything.

In Beta 2 it used to be pretty fast.
It was trully better then.
I hope on the stable version it will be resolved somehow.

5Ghz is scanning for dfs channel on boot, change it on your wireless settings to a channel that isn’t dfs

 

[RMerlin]

In Beta 2 it used to be pretty fast.

Zero change to wifi. Your issue is most likely DFS scanning taking the required minute to ensure the channel is free.

 

[Damit1]

5Ghz is scanning for dfs channel on boot, change it on your wireless settings to a channel that isn’t dfs

36 As far as I remember is non DFS.
Eric mentioned the same.
Well, it still works great on 160Mhz, I will suffice with that.

 

[Ripshod]

I'm now seeing 5G refusing to switch back to 160MHz for my notebook. Maybe I was just lucky before but this issue was solved in the last 2 betas.
I'm going to switch back to beta 2, see what happens.

 

[MDM]

36 As far as I remember is non DFS.
Eric mentioned the same.
Well, it still works great on 160Mhz, I will suffice with that.

160 wide is Always DFS...

 

[RMerlin]

36 As far as I remember is non DFS.
Eric mentioned the same.
Well, it still works great on 160Mhz, I will suffice with that.

160 MHz requires it to overlap with DFS channels, hence the scanning. There is only room for 80 MHz in the non-DFS channels.

 

[RMerlin]

I'm going to switch back to beta 2, see what happens.

Zero wifi changes in beta 3...

 

[Damit1]

160 MHz requires it to overlap with DFS channels, hence the scanning. There is only room for 80 MHz in the non-DFS channels.

Thank you for this explanation.
Was always weird for me

 

[RMerlin]

I found an even simpler workaround - I hit the "Apply" button on the WAN/DDNS page which forced an update and stopped the 30 second restarts.

I'm using WWW.NO-IP.COM as a DDNS provider.

Thanks.

Can you test something for me please?

1) Re-create the situation where watchdog keeps trying to update ddns
2) Connect over SSH then run the following command:

ddns_updated

3) See if the update attempts stop

If it works, then I will just need to re-run that function whenever an automated update ends up in an unchanged IP.

 

[Ripshod]

Zero wifi changes in beta 3...

Yh I know. And now it's working fine on beta3. It's a strange world indeed. Time to reinstall my add-ons.

 

[alan6854321]

1) Re-create the situation where watchdog keeps trying to update ddns
2) Connect over SSH then run the following command:

ddns_updated

3) See if the update attempts stop

If it works, then I will just need to re-run that function whenever an automated update ends up in an unchanged IP.

No, the "ddns_updated" command didn't make any difference, the syslog messages continued. There was no output from the command either.

 

[bluepoint]

No, the "ddns_updated" command didn't make any difference, the syslog messages continued. There was no output from the command either.

Was this statement after you've recreated the ddns problem?

 

[alan6854321]

Was this statement after you've recreated the ddns problem?

Yes, recreated it by powering my modem on & off.

 

[RMerlin]

There was no output from the command either.

That was normal. What it does is just instruct the firmware that a DDNS update had been completed.

So far I am unable to reproduce the issue, because my own public IP is dynamic (so it changes every time), and testing on a router within my LAN does not trigger the issue either (possibly because it has a non public IP). I suspect that in your case, your DDNS fails on its first attempt (possibly because it runs a fraction of a second before your public IP is ready), and it's the retry code that gets stuck in a loop.

While the issue happens, can you provide me with the output from this? (you can remove the private info such as IP, username, password, etc...):

nvram show | grep ddns_

This will let me see the state in which the DDNS is.

 

[alan6854321]

While the issue happens, can you provide me with the output from this? (you can remove the username/hostname/password settings from the list):

nvram show | grep ddns_

This will let me see the state in which the DDNS is.

nvram show | grep ddns_
ddns_act=update
ddns_cache=1692202869,31.111.222.1
ddns_check_retry=3
ddns_enable_x=1
ddns_hostname_old=xxxxxxxxxxxx.ddns.net
ddns_hostname_x=xxxxxxxxxxxx.ddns.net
ddns_hostname_x_old=
ddns_ipaddr=31.111.222.1
ddns_ipv6_update=1
ddns_last_wan_unit=0
ddns_passwd_x=????????????
ddns_realip_x=0
ddns_refresh_x=21
ddns_regular_check=1
ddns_regular_period=60
ddns_replace_status=0
ddns_return_code=
ddns_return_code_chk=200
ddns_server_x=WWW.NO-IP.COM
ddns_server_x_old=WWW.NO-IP.COM
ddns_status=1
ddns_transfer=7C:10:AA:BB:CC:DD
ddns_update_by_wdog=1
ddns_username_x=zzzzzzz@xxxxxxxxxxxx.me.uk
ddns_wan_unit=-1
ddns_wildcard_x=0
size: 82426 bytes (48646 left)

(removed personal infos. -rm)