[164901] in North American Network Operators' Group
Re: Spoofing ASNs (Re: SNMP DDoS: the vulnerability you might not
daemon@ATHENA.MIT.EDU (Blake Dunlap)
Thu Aug 8 14:08:53 2013
In-Reply-To: <EFBC2A9A-91D2-4F31-9565-2713B092034B@puck.nether.net>
From: Blake Dunlap <ikiris@gmail.com>
Date: Thu, 8 Aug 2013 13:07:56 -0500
To: Jared Mauch <jared@puck.nether.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On a related note, how are you actually getting this data?
What you have said previously ( Number of unique IPs that spoofed a packet
to me. (eg: I sent a packet to 1.2.3.4 and 5.6.7.8 responded). ) doesn't
even make sense.
-Blake
On Thu, Aug 8, 2013 at 12:51 PM, Jared Mauch <jared@puck.nether.net> wrote:
> Oops, I pulled the wrong data (off by one column) out before a trip and
> didn't realize it until now.
>
> This is not the spoofer list, but the list of ASNs with open resolvers.
>
> Let me reprocess it.
>
> Apologies, corrected data being generated.
>
> - Jared
>
> On Aug 8, 2013, at 1:29 PM, Jared Mauch <jared@puck.nether.net> wrote:
>
> > The following is a sorted list from worst to best of networks that allow
> spoofing: (cutoff here is 25k)
> >
> > (full list -
> http://openresolverproject.org/full-spoofer-asn-list-201307.txt )
>
>
>
