daemon sending wrong/old IP-address on update

[RedCookieLP]

daemon sending wrong/old IP-address on update

[troglobit]

What is the version of your inadyn and how did you install it? Sometimes bugs are fixed in newer versions and sometimes distributions add their own patches. Impossible for us here upstream to know.

[RedCookieLP]

I am using inadyn 2.8.1 on Ubuntu 22.10, installed using apt

[troglobit]

I was afraid of that, you should report issues with packaged software with your distribution. They often carry very old releases, v2.8.1 was released 2021-01-31, the latest release is v2.11.0 and a v2.11.1 is coming out very soon.

In this case I believe your problem is a duplicate of issue #367, fixed in 1f6ae75 for v2.9.1.

[RedCookieLP]

Ok, i manually upgraded to 2.11.0 and using custom it seems to be working fine so far.
But i noticed that [email protected] is now a supported provider.
(I am trying to use INWX's DDNS with IPv6... don't know why i censored it before)

I configured it for that using this config... (the checkip-command is the same as before)

provider [email protected] {
        ssl             = true
        username        = ...
        password        = ...
        hostname        = ...
        checkip-command = "ip -6 addr list scope global $iface | grep -v \"deprecated\" | grep -v \" fd\" | sed -n 's/.*inet6 \\([0-9a-f:]\\+\\).*/\\1/p'"
}

...but it sent the IPv6 in the wrong parameter (IPv6-address in myip-parameter, not myipv6), so INWX just discarded it and used my NAT-IPv4 instead. (<-- this was confirmed by INWX's support)
Is this a bug or did i misconfigure inadyn here?

[troglobit]

Great to hear custom works better in v2.11.0!

In v2.11.0 a LOT of new providers were added, courtesy of the DD-WRT project, but I have not had the ability to test and verify any of the changes.

It would be greatly helpful if you could debug this issue. It sounds like a bug and simply adjusting the URL the plugin uses and recompile should be enough.

[troglobit]

Any progress?

[troglobit]

I made a speculative fix which will be part of v2.12.0, which pending testing will be out any day now.