[130383] in North American Network Operators' Group
Re: Using crypto auth for detecting corrupted IGP packets?
daemon@ATHENA.MIT.EDU (Christopher Morrow)
Fri Oct 1 19:08:43 2010
In-Reply-To: <E3835E0D-2B90-4ED7-B720-A69F5ED5BECA@puck.nether.net>
Date: Fri, 1 Oct 2010 19:08:34 -0400
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Jared Mauch <jared@puck.nether.net>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Fri, Oct 1, 2010 at 7:26 AM, Jared Mauch <jared@puck.nether.net> wrote:
>
> On Oct 1, 2010, at 3:49 AM, Dobbins, Roland wrote:
>
>>
>> On Oct 1, 2010, at 1:01 PM, Manav Bhatia wrote:
>>
>>> In 6 hours you will have around 8000K BFD packets. Add OSPF,
>>> RSVP, BGP, LACP (for lags), dot1AG, EFM and you would really get a
>>> significant number of packets to buffer.
>>
>>
>> Which isn't a 'HUGE!' amount of packets.
>>
>> ;>
>
>
> Yup, but when trying to figure out the root cause of some problem, having a few gigs of data would be helpful.
>
> In the event people have not noticed, hard drives are semi-popular in routers now, so assuming you have some variable amount of disk space greater than 8MB for an image is feasible.
on at least one platform you can get some details with traceoptions, no?
