It is global.
01:42:04.040462 194.87.13.21.1812 > x.x.x.x.1434: rad-account-req
376 [id 1] Attr[ User User User User User User User User User User User
User User User User User User User User User User User User User User User
User User User User User User User [|radius]
That is the traffic..
Agreed...I worked these attacks on UUNET's backbone and quite honestly
none of them was over 100mbit worth of traffic. We see this everyday,
this was nothing out of the ordinary except the destination...
Shrug...fear is an easy weapon to wield, eh?
On Tue, 22 Oct 2002, Richard A Steenbergen wr
Have you contacted 701?
On Thu, 26 Sep 2002, Sorin CONSTANTINESCU wrote:
>
>
> Hi,
>
> This morning we've discovered that one of our IP's was routed somewhere
> towards an ALTER.NET customer.
>
> All the "experiments" i'm going to show you are done from
> route-server.exodus.net.
>
> a show
I was about to reply with that...Oh well, nobody is perfect!
=]
On Fri, 12 Jul 2002, Phil Rosenthal wrote:
>
> Wow, I feel stupid now, they actually have a /9.
>
> Ignore me ;)
> --Phil
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
> Phil Ros
Then you are pushing out /32's and peers would need to accept them. Then
someone will want to blackhole /30's, /29's, etc. Route bloat. Yum!
Additionally you are creating a way to basically destroy the Internet as a
whole. One kiddie gets ahold of a router, say of a large backbone
provider,
http://www.secsup.org/Tracking/
UUNet uses that...others might as well, Shrug.
Quick, simple, effective tracking of DDoS attacks.
As for identifying attacks, quite honestly large ISP's are typically still
relying on customer notification. I know that's how we do it.
On Wed, 1 May 2002, Pete
