You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2015/06/16 16:22:57 UTC

[Bug 7211] ASN shows ipv4 ranges on ipv6 recieved range

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7211

Kevin A. McGrail <km...@pccc.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kmcgrail@pccc.com
         Resolution|---                         |WORKSFORME
             Status|NEW                         |RESOLVED

--- Comment #1 from Kevin A. McGrail <km...@pccc.com> ---
I think it's a configuration error.  For example, the IPv6 address below in
your example in reverse notation becomes

7.7.0.c.9.e.e.f.f.f.9.c.e.1.2.0.0.0.0.0.c.a.5.0.d.d.9.2.2.0.0.2

So the lookup becomes:

dig
7.7.0.c.9.e.e.f.f.f.9.c.e.1.2.0.0.0.0.0.c.a.5.0.d.d.9.2.2.0.0.2.aspath.routeviews.org.
IN TXT

That returns: ;; ANSWER SECTION:
2.0.0.2.aspath.routeviews.org. 86400 IN TXT     "293 5511 3215" "2.0.0.0" "16"

Which means either perhaps we aren't doing IPv6 lookups correctly or
routeviews.org doesn't support IPv6.  I'm guessing the later since it is
truncating all but the last 4 octets received (note the ANSWER section and
compare to the answer section below).

So looking up one of my IPs and using origin6.asn.cymru.com, I see:

6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.0.0.0.0.a.2.0.5.5.0.1.0.0.2.origin6.asn.cymru.com.
14400 IN TXT "174 | 2001:550::/32 | US | arin | 2002-12-17"

So I think you need something like this from the note in the ASN.pm

# Some zones also support IPv6 lookups, for example:
#   asn_lookup origin6.asn.cymru.com [_ASN_ _ASNCIDR_]

I don't use this plugin so feedback appreciated perhaps on dev list since I'm
going to close this as worksforme for now.

-- 
You are receiving this mail because:
You are the assignee for the bug.