Opened at 2007-09-29T04:44:28Z
Closed at 2007-10-13T06:38:50Z
#153 closed defect (fixed)
iputil returns 0.0.0.0
Reported by: | zooko | Owned by: | zooko |
---|---|---|---|
Priority: | minor | Milestone: | 0.6.1 |
Component: | code-network | Version: | 0.6.0 |
Keywords: | Cc: | ||
Launchpad Bug: |
Description
I thought I was supposed to fix this, but I just saw it on cygwin.
Leaving this ticket here for myself to come back to it after I demo Tahoe to Seb.
Change History (5)
comment:1 Changed at 2007-09-29T16:01:41Z by zooko
- Status changed from new to assigned
comment:2 Changed at 2007-10-02T20:53:21Z by zooko
So, if I just make iputil filter out all IP addresses that end in ".0", this will solve this issue, right? Is there any other filtering or munging that I should do?
comment:3 Changed at 2007-10-02T20:55:18Z by zooko
(Note that iputil is intended to return non-routeable, private IP addresses, because foolscap can use those if both ends are on the same network and foolscap isn't harmed by them.)
comment:4 Changed at 2007-10-11T03:14:46Z by warner
actually, just filter out 0.0.0.0 . There are valid addresses that end in .0 (any subnet larger than /24 will have some host addresses that have 0 as a last octet).
0.0.0.0 is well-defined as a special "INADDR_ANY" address, and is never valid as a host address. So just filter out that one case.
comment:5 Changed at 2007-10-13T06:38:50Z by zooko
- Resolution set to fixed
- Status changed from assigned to closed
Fixed by af0edec753033339.
Correction: it is the Solaris version of iputil that returns 0.0.0.0. The cygwin version doesn't.