nanog mailing list archives
Re: Verizon Routing issue
From: Jared Mauch <jared () puck nether net>
Date: Mon, 24 Jun 2019 11:03:19 -0400
On Jun 24, 2019, at 11:00 AM, ML <ml () kenweb org> wrote: On 6/24/2019 10:44 AM, Jared Mauch wrote:It was impacting to many networks. You should filter your transits to prevent impact from these more specifics. - Jared https://twitter.com/jaredmauch/status/1143163212822720513 https://twitter.com/JobSnijders/status/1143163271693963266 https://puck.nether.net/~jared/blog/?p=208$MAJORNET filters between peers make sense but what can a transit customer do to prevent being affected by leaks like this one?
Block routes from 3356 (for example) that don’t go 701_3356_ 701_2914_ 701_1239_ etc (if 701 is your transit and you are multi homed) Then you won’t accept the more specifics. If you point default it may not be any help. - Jared
Current thread:
- Re: CloudFlare issues?, (continued)
- Re: CloudFlare issues? Ca By (Jun 25)
- Re: CloudFlare issues? Mark Tinka (Jun 24)
- Re: CloudFlare issues? Fredrik Korsbäck (Jun 24)
- Re: CloudFlare issues? Jaden Roberts (Jun 24)
- Re: CloudFlare issues? Andree Toonk (Jun 24)
- Re: CloudFlare issues? Max Tulyev (Jun 24)
- Re: CloudFlare issues? Filip Hruska (Jun 24)
- Re: CloudFlare issues? Christopher Morrow (Jun 24)
- Verizon Routing issue Jared Mauch (Jun 24)
- Re: Verizon Routing issue ML (Jun 24)
- Re: Verizon Routing issue Jared Mauch (Jun 24)
- Re: Verizon Routing issue Max Tulyev (Jun 24)
- Re: Verizon Routing issue Jared Mauch (Jun 24)
- Re: CloudFlare issues? Filip Hruska (Jun 24)
- Re: CloudFlare issues? Max Tulyev (Jun 24)