[107218] in North American Network Operators' Group
RE: Revealed: The Internet's well known BGP behavior
daemon@ATHENA.MIT.EDU (John Lee)
Wed Aug 27 23:48:01 2008
From: John Lee <john@internetassociatesllc.com>
To: Adrian Chadd <adrian@creative.net.au>
Date: Wed, 27 Aug 2008 22:47:53 -0500
In-Reply-To: <20080828033212.GE30494@skywalker.creative.net.au>
Cc: NANOG list <nanog@merit.edu>
Errors-To: nanog-bounces@nanog.org
Adrian,
The traceroute utility that I used gave me a list of hops that the packet I=
was interested in transited and a time when it transited the hop. When the=
TTL was reached it would terminate the listing.
When ever I had performance issues on my networks or with my networks links=
it would indicate if the standard route was being taken or another one. Wh=
en certain links went down several additional hops would be added to the li=
st.
John (ISDN) Lee
________________________________________
From: Adrian Chadd [adrian@creative.net.au]
Sent: Wednesday, August 27, 2008 11:32 PM
To: John Lee
Cc: Patrick W. Gilmore; NANOG list
Subject: Re: Revealed: The Internet's well known BGP behavior
On Wed, Aug 27, 2008, John Lee wrote:
> Patrick,
>
> VPN's and MPLS control intermediate hops and IPsec and SSL do not allow t=
he info to be seen.
>
> Rewriting the TTL only hides the number of hop count, trace route will st=
ill show the hops the packet has transited.
No, traceroute shows the hops which returned "time to live exceeded."
This only maps to "the hops the packet has transited" if the TTL is setup
and decremented correctly.
Adrian
