Thank you. So as the lease renewal only triggers inadyn for IPv6, where the first step in the log sequence is
Code:
rc_service: dhcp6c 17123:notify_rc restart_ddns
which in turn triggers
Code:
custom_script: Running /jffs/scripts/service-event (args: restart ddns)
start_ddns: update WWW.ASUS.COM update@asus.com, wan_unit 0
do you know where can I look to see why the same lease renewal does not trigger
service-event (args: restart ddns) for IPv4?
AFIK and going back to my post #11 in this thread, the change of process, i.e. the active inclusion of IPv6 has happened only
after the change in Merlin firmware from 384.19 and 386.1_2 (but as a result of an Asus firmware change...) hence, post #13 from
@RMerlin still makes perfect sense IF, your IPv6 WAN address is being renewed and/or is not present and this is
regardless of DDNS being active.
If DDNS IS active, then as you've seen yourself above
@archiel (and as my own post #11 also confirms), the IPv6 action then triggers the IPv4 DDNS verification too (even if it's not actually necessary!)
The ideal
solution to all, would
appear to be, having the ability to disable the IPv6 check process, by way of adding a comment out # prefix in the right area of code or ultimately, a Yes/No GUI value.
This, would then accommodate a) All those that don't use IPv6 at all b) All those that have a static IPv6 address c) All those that have a static IPv6 address
but only static as far as a firm, non variable LAN IPv6 Prefix (hence IPv6 pool of addresses below on the router) is concerned, as their own specific WAN IPv6 may / will change, after a router re-boot (unlike IPv4) but change only within the relative WAN IPv6 pool, thus still allowing the firm, non variable LAN IPv6 Prefix value on the router to remain. All those with a dynamic IPv6 address would / should be able to use this as intended i.e. check enabled I think?
The GUI value option is one for a possible inclusion in future firmware, but, after some detective work, it
should be possible to work out how to comment out the specific requirement within the current code?