https://issues.apache.org/SpamAssassin/show_bug.cgi?id=4964
--- Comment #17 from Justin Mason <[EMAIL PROTECTED]> 2008-03-11 16:58:08 PST
---
looking into this more: I've run into several more Net::IP bugs, and their
rt.cpan.org queue is full of nasties that are several years old. so I finally
agree, depending on an unmaintained and buggy module may not be a good idea!
on the other hand, NetAddr::IP seems to be working fine for me in testing,
apart from that one issue. but I think we can easily hack around that.
question. Should ::ffff:127.0.0.1, ipv4 127.0.0.1, and ::1 be considered
equivalent? ::ffff:127.0.0.1 is ipv4 127.0.0.1 represented as an IPv4-mapped
address. ::1 is the ipv6-native loopback address.
I think all 3 represent the loopback and should be considered equivalent in our
code. at least, ::ffff:127.0.0.1 and 127.0.0.1 are the same addr represented
differently so should be equal. NetAddr::IP doesn't seem to agree, as I noted
previously:
perl -we 'use NetAddr::IP; print
NetAddr::IP->new("::ffff:127.0.0.1")->contains(NetAddr::IP->new("127.0.0.1"))'
0
But ::1 is a different address entirely -- it's not equal to the ipv4 loopback.
however it has the same meaning to our NetSet class, I think.
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
