-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I just received reply from Sloan-Park, that they have shutdown that customer
yesterday 6:40pm CET and the customer has been requested to clean-up his config.
BR
Jens
Jason Kalai Arasu schrieb:
> I encountered it yesterday from AS47868.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Paul Vixie schrieb:
> a minor editorial comment:
>
> Jens Ott - PlusServer AG writes:
>
>> Jack Bates schrieb:
>>> Paul Vixie wrote:
>>>
>>> Do you have a miraculous way to stop DDOS? Is there n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jack Bates schrieb:
> Paul Vixie wrote:
>
> Do you have a miraculous way to stop DDOS? Is there now a way to quickly
> and efficiently track down forged packets? Is there a remedy to shutting
> down the *known* botnets, not to mention the unknown ones
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steven M. Bellovin schrieb:
> On Fri, 13 Feb 2009 16:41:41 + (WET)
> Nuno Vieira - nfsi telecom wrote:
>
>> Ok, however, what i am talking about is a competelly diferent thing,
>> and i think that my thoughts are alligned with Jens.
>>
>> We want
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
@jack: sorry for duplicate ... pressed reply instead of reply-all ;)
Jack Bates schrieb:
> valdis.kletni...@vt.edu wrote:
> Presumably, the route server would have to have the same guidelines as
> issued by service providers. ie, /32 networks injected
c from IPs listed with that community to the blackhole RR
destination(s) everywhere in there network.
BR
Jens
>
> - S
>
> -Original Message-
> From: Nuno Vieira - nfsi telecom
> Sent: Friday, February 13, 2009 07:13
> To: Jens Ott - PlusServer AG
> Cc: nanog
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
in the last 24 hours we received two denial of service attacks with something
like 6-8GBit volume. It did not harm us too much, but e.g. one of our
upstreams got his Amsix-Port exploded.
With our upstreams we have remote-blackhole sessions runnin
7 matches
Mail list logo