netdev
[Top] [All Lists]

Re: icmp_unreachable uses wrong ip

To: Pekka Savola <pekkas@xxxxxxxxxx>
Subject: Re: icmp_unreachable uses wrong ip
From: Glen Turner <glen.turner@xxxxxxxxxxxxx>
Date: Wed, 04 May 2005 10:45:45 +0930
Cc: netdev@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.61.0505031239460.3205@xxxxxxxxxx>
Organization: Australian Academic and Research Network
References: <1115040079.5620.11.camel@xxxxxxxxxxxxxxxxxxxxxxxxx> <20050503092244.GA8864@xxxxxxxxxxxxxxxxx> <Pine.LNX.4.61.0505031239460.3205@xxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2-1.3.2 (X11/20050324)
Pekka Savola wrote:


There's no specification requiring or recommending either of these approaches, either for v6 or v4 AFAICS so you can't depend on that behaviour..

In the lack of a specification, doing what works best for
network operators would be nice :-)

And that behaviour is that addresses in a traceroute should
be ping-able.  That is, you're tracing the route and there's
loss at one point, so you want to determine how much loss.

The outgoing interface's address may not be reached down the
same path as used by the traceroute, whereis the incoming address
obviously is (or if it isn't, then that itself is interesting
diagnostic information).

Similarly, using the incoming interface gives more information
about asymetric routes.

In short, since using the incoming address gives more useful
output and the specification is silent as to which address
is allowable, using the incoming interface's address would
be the most useful choice.

Cheers,
Glen

--
 Glen Turner         Tel: (08) 8303 3936 or +61 8 8303 3936
 Australia's Academic & Research Network  www.aarnet.edu.au

<Prev in Thread] Current Thread [Next in Thread>