I was having some troubles with ddclient on my server here so I started looking into it.
There were seven bugs open and it was a micro version behind upstream. I fixed all of that by accident.
I sneezed.
Hardened users should be happy as now it’ll use iproute2 (only if you have the ‘hardened’ USE flag enabled) instead of ifconfig to grab the IP address of the given adapter.
Also, 3.8.0 introduced the ability to handle multiple IP address. So, for those of you lucky enough to have multiple connections to the Internet, that should make you happy. 3.8.0 has been available for quite some time, but I think it’s a noteworthy item.
If all goes well, net-dns/ddclient-3.8.1-r1 will be a candidate for stabilization a month from now.
Any reason why not to _always_ use iproute2 (on Linux, that is)?
I’d pitch it upstream…if I knew why ifconfig is less desirable.
Well, in general iproute2 is supposed to be the “new” one of the two, and thus preferred. Any reason why it is considered only for hardened? 😉
I guess my point is that anything that’s good for hardened is good for vanilla, when it does not involve SSP/PaX or other negative-performance approaches.
ifconfig will not work in many use cases. For example, dhcpcd sometimes (depending on the router) will store the “external” address such that it is visible with “ip route show” while ifconfig/route only shows local addresses.
Just FYI: while 3.8.0 worked nicely with multiple “use=if, if=pppX” lines but 3.8.1-1 seems to have a regression and this doesn’t work. I’ve had to roll back (Arch not Gentoo but might still be relevant).
That’d be a bug for upstream. The only change I made to the code is to use iproute2 when ‘hardened’ is enabled.
Awesome! Love ddclient. 🙂
I’m still on net-tools personally due to lack of time. I’ve also read there’s really no good reason not to make the switch to iproute2.