ports/60940: Port ez-ipupdate requires updating to new release.
Stefan Eßer
se at FreeBSD.org
Tue Jan 6 23:31:36 UTC 2004
On 2004-01-05 16:18 -0800, Clement LAFORET <clement at FreeBSD.org> wrote:
> Synopsis: Port ez-ipupdate requires updating to new release.
>
> Responsible-Changed-From-To: freebsd-ports-bugs->se
> Responsible-Changed-By: clement
> Responsible-Changed-When: Mon Jan 5 16:18:10 PST 2004
> Responsible-Changed-Why:
> Over the maintainer.
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=60940
Sorry, but I can't reproduce this problem on my -CURRENT box:
$ ez-ipupdate -V
ez-ipupdate: - 3.0.11b7 - $Id: ez-ipupdate.c,v 1.48 2001/07/17 00:49:41 amackay Exp $
I have just verified, that my DynDNS.org entry is automatically updated.
The code difference between 3.0.11b7 and b8 is only the declaration
of the errno variable (as mentioned in the 'Notes' section on the
ez-ipupdate web-site:
version 3.0.11b8 is a fix for accessing errno directly
and it is largely untested by me but it should work.
which I verified by performing a recursive diff over the b7 and b8
source trees.)
I need more details about the problem observed under FreeBSD. I had
prepared a port upgrade to b8 more than half a year ago. But when I
found, that there was no actual code change and that the b8 tar file
was not available from all mirrors, I decided to stay with b7 ...
In which way does the Linksys WRT54G problem affect the FreeBSD port
of ez-ipupdate ?
Is DynDNS.org going to block clients that identify themselves as
ez-ipupdate 3.0.11b7, since this is how they recognize the buggy WRT54G
firmware version ?
In that case the b7 version should have stopped working three weeks
ago. But it continues to work for me ...
Regards, STefan
More information about the freebsd-ports-bugs
mailing list