[AusNOG] BGP hold timer values

McDonald Richards mcdonald.richards at gmail.com
Wed Jan 28 20:09:22 EST 2015


DOS attack vector? ;)

(plz dont)

Macca


On Tue, Jan 27, 2015 at 11:28 PM, David Hughes <david at hughes.com.au> wrote:

>
> Yeah, but only to a lower limit that the platform thinks is sane.  My
> memory tells me that a few years back, trying to run 5/15 upstream only
> worked on some of our peers as Upstream X used Cisco and Upstream Y used
> Juniper.   One of them failed to negotiate with timers that aggressive and
> only worked if we requested 10/30.
>
>
> Thanks
>
> David
> ...
>
>
> On 28/01/2015, at 5:15 PM, "Bob Purdon" <bobp at purdon.id.au> wrote:
>
>
> Ø  I am going to go from memory here, which is a little rusty, and recall
> that the lowest set peer wins the timer battle (peer with lowest setting
> negotiates for the session).
>
> Pretty sure you’re right there.
>
> I have a vague recollection of an IX peer that was using 1/3 at one point
> (or something similarly short – short enough I was surprised it could be
> configured that low).
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20150128/6f288221/attachment.html>


More information about the AusNOG mailing list