<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: Last stupid question: traceroute
From: Keith Smith <keith,AT,ksmith,DOT,com>
Date: Wed, 23 Jan 2002 05:18:05 +0100

RE: cp ... Path is hard coded in pkcipe.  In fact pkcipe will move with
configure, but the process won't move ciped-cb.  At some point someone
will have configure fix up a paths.h file and I'm certain it will work.

I looked at the FAQ.  I'm about blue on the .info file which won't install
btw, and disappears if you run make distclean, but of course info -f cipe.info
works just fine.  Just don't back up too far.  or get off my duff and hand
install the bloody thing into /usr/info.

Okay the CIPE tunnels are up, everything is peachy, except you cannot
traceroute through the CIPE connection:

[keith@b0201]/etc/cipe/peers<421>ifconfig cipcb2
cipcb2    Link encap:IPIP Tunnel  HWaddr
           inet addr:192.168.25.128  P-t-P:192.168.64.128  
Mask:255.255.255.255
           UP POINTOPOINT RUNNING NOARP  MTU:1442  Metric:1
           RX packets:26 errors:0 dropped:0 overruns:0 frame:0
           TX packets:202 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:100

[keith@b0201]/etc/cipe/peers<422>ping -c2 192.168.64.128
PING 192.168.64.128 (192.168.64.128): 56 data bytes
64 bytes from 192.168.64.128: icmp_seq=0 ttl=255 time=26.2 ms
64 bytes from 192.168.64.128: icmp_seq=1 ttl=255 time=26.2 ms

--- 192.168.64.128 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 26.2/26.2/26.2 ms
[keith@b0201]/etc/cipe/peers<423>traceroute !!:2
traceroute 192.168.64.128
traceroute to 192.168.64.128 (192.168.64.128), 30 hops max, 40 byte packets
  1  * * *
  2  * * *
  3  * * *

Why can we ping (ICMP) but not trace (also ICMP)?  Something not implemented
in the kernel layer?

-- 
Keith Smith                 keith,AT,ksmith,DOT,com
655 W Fremont Dr
Tempe AZ 85282              it's hot





<< | Thread Index | >> ]    [ << | Date Index | >> ]