[150011] in North American Network Operators' Group
Re: Common operational misconceptions
daemon@ATHENA.MIT.EDU (Mike Lyon)
Fri Feb 17 11:47:01 2012
From: Mike Lyon <mike.lyon@gmail.com>
In-Reply-To: <4F3E76C5.8010902@brightok.net>
Date: Fri, 17 Feb 2012 08:46:02 -0800
To: Jack Bates <jbates@brightok.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Sent from my iPhone
On Feb 17, 2012, at 7:48, Jack Bates <jbates@brightok.net> wrote:
>
>
> On 2/17/2012 9:18 AM, Steve Clark wrote:
>> Having worked with many people over the last 40 years, the good trouble
>> shooters understood how things
>> were suppose to work. This helps immeasurably in determining where to
>> start looking.
>>
>
> Ran into this not too long ago with a transport problem. The behavior I w=
as seeing was indicative of the transport not stripping their outer tag. Th=
ey put wireshark on a windows laptop and sent me the traffic captures. Whil=
e I didn't know that M$ decided to do something silly like removing a singl=
e tag, all indicators were that the M$ stack "fixed" whatever was broken pr=
ior to wireshark. We took a capture from another device and proved the prob=
lem.
>
> Which is a common transport problem I often see, "Our configuration looks=
right, it must be on your end."
>
>
> Jack
>
If i had a dollar for everytime i've heard that from a telco, i'd be a
rich man...
