DDNS update not working after update to 386.9

[dciarnie]

After updating my RT-AC68U to 386.9, ddns updates stopped working.

Before the update, the log contained entries such as

Jan 28 07:46:46 rc_service: dhcp6c 16819:notify_rc restart_ddns
Jan 28 07:46:46 start_ddns: update CUSTOM , wan_unit 0
Jan 28 07:46:47 start_ddns: Clear ddns cache.
Jan 28 07:46:47 custom_script: Running /jffs/scripts/ddns-start (args: xxx.xxx.xxx.xxx)
Jan 28 07:46:49 ddns: Completed custom ddns update

after, though

Jan 28 10:36:02 watchdog: start ddns.
Jan 28 10:36:02 rc_service: watchdog 354:notify_rc restart_ddns watchdog
Jan 28 10:36:02 ddns: eth0 has not yet obtained an WAN IPv6 address.(9)

The ddns-start script works fine if run manually.

I'm assuming that there's a bug in the latest firmware that's causing this but I'm wondering if there's anything that can be done to workaround the problem until a fix is in place.

 

[L&LD]

Did you try simply reboot your router?

What firmware did you update from?

When was the last time you fully reset this long supported router?

 

[RMerlin]

DIsable IPv6 DDNS support, as reported in your log it looks like your WAN interface isn't getting an IPv6.

 

[Dabombber]

I'm getting the same thing.

Is the logic for this right?

#ifdef RTCONFIG_IPV6
    if (nvram_get_int("ddns_ipv6_update")
        && ipv6_enabled() && (_get_ipv6_addr(wan_ifname, ip6_addr, sizeof(ip6_addr)) != 0))
    {
        logmessage("ddns", "%s has not yet obtained an WAN IPv6 address.(%d)", wan_ifname, ddns_check_retry);
        /* Trigger watchdog when start fails */
        nvram_unset("ddns_updated");
        nvram_set("ddns_return_code", "ddns_query"); /* for Retry mechanism */
        nvram_set("ddns_return_code_chk", "-1");
        return -1;
    }
#endif

cat /proc/net/if_inet6
fe80000000000000xxxxxxxxxxxxxxxx 09 40 20 80     eth1
fe80000000000000xxxxxxxxxxxxxxxx 0f 0a 20 80     ppp0
fe80000000000000xxxxxxxxxxxxxxxx 03 40 20 80     ifb1
fe80000000000000xxxxxxxxxxxxxxxx 0e 40 20 80      br0
fe80000000000000xxxxxxxxxxxxxxxx 0b 40 20 80    vlan1
fe80000000000000xxxxxxxxxxxxxxxx 07 40 20 80     eth0
fe80000000000000xxxxxxxxxxxxxxxx 0a 40 20 80     eth2
fe80000000000000xxxxxxxxxxxxxxxx 02 40 20 80     ifb0
fe80000000000000xxxxxxxxxxxxxxxx 08 40 20 c0    dpsta
fe80000000000000xxxxxxxxxxxxxxxx 06 40 20 c0      agg
fe80000000000000xxxxxxxxxxxxxxxx 04 40 20 c0     fwd0
fe80000000000000xxxxxxxxxxxxxxxx 05 40 20 80     fwd1
xxxxxxxxxxxxxx000000000000000001 0e 40 00 80      br0
00000000000000000000000000000001 01 80 10 80       lo

Posted this in the other thread. IPv6 is working fine for me, just the DDNS which is having issues.

 

[dciarnie]

Did you try simply reboot your router?

What firmware did you update from?

When was the last time you fully reset this long supported router?

Yes, I did reboot the router.

I updated from 386.7_2.
It's been so long that I don't remember. I have hesitated doing so because I don't relish the idea of setting up the router again.

If I were to do so, would I lose my jffs partition?

 

[dciarnie]

DIsable IPv6 DDNS support, as reported in your log it looks like your WAN interface isn't getting an IPv6.

Disabling the "IPv6 Update" option looks like it has fixed the problem. Thanks.

I should have looked at the 386.8 release notes

Not sure why there should be a problem with this as my ISP supports IPv6.

 

[RMerlin]

Not sure why there should be a problem with this as my ISP supports IPv6.

Asus' implementation is simply not working properly yet.

 

[archiel]

Disabling the "IPv6 Update" option looks like it has fixed the problem. Thanks.

I should have looked at the 386.8 release notes

Not sure why there should be a problem with this as my ISP supports IPv6.

I don't know if this would work on a RT-AC68U, but for my RT-AX88U I have a similar issue in that DDNS would fail when IPv6 Native mode was enabled as (Asus) DDNS needs to pick up the IPv6 WAN address (on eth0 on theAX88U), but on my setup it was only showing on br0 - you can use ifconfig br0, ifconfig eth0 to check. I then used nvram get ipv6_rtr_addr get the WAN IPv6 address on the AX88U, it may be a different nvram variable on the AC68U.

And up creating ipv6add.sh in /jffs/addons/ddnsipv6

#!/bin/sh
sleep 10s
ip -6 address add dev eth0 $(nvram get ipv6_rtr_addr)/128
nvram set ddns_ipv6_update=1
service restart_ddns

and calling it from post-mount by adding
Code:

sh /jffs/addons/ddnsipv6/ipv6add.sh

as the last entry.

 

[unsynaps]

Having the exact same issues here to the letter.
Can not resolve IPv6 addresses on my Windows machine or directly on the router either. Yet all web tests say everything is fine.
EDIT: Using this script in /jffs/scripts/wan-event

#!/bin/sh
FILENAME=`basename "$0"`

if [ $1 = "0" ] && [ $2 = "connected" ]; then
    loop=0
    while [ -z "$(nvram get ipv6_rtr_addr)" ] && [ $loop -lt 60 ]
    do
        sleep 1s
        loop=$((loop+1))
    done
   
    ip -6 address add dev eth0 $(nvram get ipv6_rtr_addr)/$(nvram get ipv6_prefix_length)
    nvram set ddns_ipv6_update=1
    service restart_ddns
fi