Traceroute but no Ping FAQ(wrong?)

Kelley Lingerfelt (pm2e@ns.cococo.net)
Fri, 29 Nov 1996 03:53:09 -0500 (EST)

Hey guys,
I posted a question a week or so ago about being able to do a
traceroute but not a ping. I was prowling through the livingston sight
and saw this question. I don't believe the answer, unless you have
changed it in the new ComOS. On the web sight at:

http://www.livingston.com/Tech/Appnotes/app.traceroute-vs-ping.shtml

you state that traceroute takes its source address from the interface it
is going through and ping takes its source address from the ether0
interface, as does TCP.

Below is a short version of my network and below it is a tcpdump after I
pinged from the Portmaster(pm3) and then I did a traceroute from the pm3
to a machine called penguin.

Is the website wrong, or am I totally misinterpreting what it says.

+--------------+
Internet | Cisco 2501 | 206.100.242.12
<------------+ cccroute1 +---------------------+--------------
Ser0 | | |
+------+-------+ +-------+------+
Ser1 |10.1.1.1 | penguin |
| | 206.100.242.7|
W1 |10.1.1.2 +--------------+
+------+----------+
| pm3 |(Portmaster PM2ER)
| 206.100.243.129 |
+-------+---------+
| +----------------+
+------------+206.100.243.130 |
+----------------+

Output of tcpdump at penguin

03:30:27.657244 10.1.1.2 > penguin.cococo.net: icmp: echo request
03:30:27.657404 arp who-has cccroute1.cococo.net tell penguin.cococo.net
03:30:27.658946 arp reply cccroute1.cococo.net is-at 0:0:c:76:2e:e4
03:30:27.659015 penguin.cococo.net > 10.1.1.2: icmp: echo reply
03:30:35.237658 10.1.1.2 > penguin.cococo.net: icmp: echo request
03:30:35.237782 penguin.cococo.net > 10.1.1.2: icmp: echo reply
03:30:35.456118 pm3.cococo.net.1072 > penguin.cococo.net.62015: udp 64 [ttl 1]
03:30:35.456284 penguin.cococo.net > pm3.cococo.net: icmp:
penguin.cococo.net udp port 62015 unreachable [tos 0xc0]

Later
Kelley