Pierre Fortin <[EMAIL PROTECTED]> wrote:
> ...
> Note... traceroute is not the same... it tries to discover a path from X to Y
> by probing 1-hop deeper on each attempt; but may not discover all the alternate
> paths which may exist, or find intermittent paths. "ping -R" records the path
> (outbound interfaces) it really took as a packet "to" and the reply "from" which
> may be different paths since routing is not guaranteed to be symmetrical.
That's an understatement ;-)
consider this:
<-local-> <------internet-----> <local>
A --+--- B ---- C ---- D ---- E ---- F -+
| |
+-----------------------------------+
where 'F' has 2 ip addresses - the one it got by dialing up into the
interent through 'E', and the one it has by virtue of being on the
local network. (And B is the firewall/gateway for the local network)
So, if machine 'A' pings machine 'F's internet address, the packet
goes A B C D E F and then returns directly to A via the local network.
rc
Rusty Carruth Email: [EMAIL PROTECTED] or [EMAIL PROTECTED]
Voice: (480) 345-3621 SnailMail: Schlumberger ATE
FAX: (480) 345-8793 7855 S. River Parkway, Suite 116
Ham: N7IKQ @ 146.82+,pl 162.2 Tempe, AZ 85284-1825
ICBM: 33 20' 44"N 111 53' 47"W
