Bug#505736: updated webgeo2ipct.pl
c.herwig at checon.de
Sat Nov 15 21:31:31 UTC 2008
-----BEGIN PGP SIGNED MESSAGE-----
gregor herrmann wrote:
| There's one other issue where you maybe could help:
| With the new database the test script fails because some IP ranges
| change. No surprise so far. The failure
| Now I'm not sure what to do:
umh, this is certainly non-trivial on second thoughts.
What I've found when trying to figure it out:
Does it break general backward compatibility? Yes, it does.
- - Unassigned IPs: old "--", new database treats them (mostly) as
belonging to the last preceding assigned IP range.
- - IANA reserved IPs: old "--", "US" or "I0", "L0" (as you mentioned),
- - some new ccTLDs: "RS" (serbia), "ME" (montenegro) for example
Does it work with awstats anyway? Yes, it does.
- - "ZZ" gets reported properly on its own line as "unknown"
- - "RS" and "ME" get listed as "unknown", each on their own line
- - awstats could list "I0" (not "L0") as "local network host" (this is in
Does it break handling of local IPs?
I wouldn't say so, because handling of local IPs is more or less
incorrect with the old version anyway. 172.16.0.0/12 and a lot of other
special blocks are wrong/missing in the old database. See
What to do?
I would support your first solution. Patch the test, document the
changes, forget about the obscure special cases mentioned in these
Of course, a more satisfying solution could be to patch the
webgeo2ipct.pl to distinguish between the different types of reserved IP
ranges (private use, loopback, link local, multicast...) correctly and
to recognize unallocated space properly. But this still wouldn't be
backward compatible or improve compatibility with awstats. And honestly,
I doubt that it would be real useful to anybody ;-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the pkg-perl-maintainers