[AusNOG] UDP Flooding Issues
james at vocus.com.au
Thu Jun 19 14:19:17 EST 2008
expect a lot of phone calls and email from the routing police, people
tend to get *really* upset when you do this.
On 19/06/2008, at 1:23 PM, Phillip Grasso wrote:
> well if it's an insignificant ISP and you wanted to do some
> *extremely* dodgy, then via the return path advertise their ASN
> (prepend the offending AN number) in your announcements. this will
> force their routers to drop your routes as it should be a bgp loop
> prevention mechanism. There are lots of things that might stop this
> from happening, including route filters on in the path inbetween.
> Otherwise the simplier method is to contact them or your isp to filter
> to traffic in question.
> 2008/6/19 Sean K. Finn <Sean.Finn at ozservers.com.au>:
>> Hi All,
>> Does anyone know any techniqiues or ways to block BGP adverts to
>> third party
>> AS's, or a similar method for dropping routes *to* our AS from a
>> non directly connected AS ?
>> For example, is there a way to inject or craft maybe a network
>> message or something that we can send to the offending A.S. to
>> remove their
>> routing information for *our* network / AS / IP ranges?
>> My scenario is that I'm trying to block UDP floods to our network,
>> and I'm
>> sure many of you have had experience with this. Im not looking for
>> a total
>> solution, although If you have any recommendations , that would be
>> What I'm really after is just once peice of the puzzle to see if we
>> selectively choose which remote networks we are visible, as a
>> direct first
>> step to stopping attacks until a human can intervene.
>> Oz Servers
>> e: sean.finn at ozservers.com.au
>> w: http://www.ozservers.com.au
>> p: 1300 13 89 69
>> AusNOG mailing list
>> AusNOG at ausnog.net
> AusNOG mailing list
> AusNOG at ausnog.net
Vocus Group Limited
Level 2, Vocus House
189 Miller Street
North Sydney, NSW 2060
(m) +61 407 496 866
(w) +61 2 9959 3913
More information about the AusNOG