Re: Can this possibly be right

James W. Laferriere (babydr@nwrain.net)
Tue, 21 Jan 1997 23:01:40 -0800 (PST)


Jim,

Came across this exact same thing the other day.

It's behind a fire-wall that doesn't allow the
ICMP TIME_EXCEEDED's to get thru.

www.analogic.com didn't seem to exist in the DNS
this evening....

On Tue, 21 Jan 1997, Jim Nance wrote:
> Hello all,
> I think I may have found a bug, but it may just be a problem with
> my understanding of how networking works. I have a machine running
> 2.0.27 and I can ping the machine www.analogic.com. However, if I
> try to telnet to the same machine I get an error message about
> there being no route to the host:
>
> sailboat> ping www.analogic.com
> PING www.analogic.com (204.178.41.218): 56 data bytes
> 64 bytes from 204.178.41.218: icmp_seq=0 ttl=244 time=590.3 ms
> 64 bytes from 204.178.41.218: icmp_seq=1 ttl=244 time=34.3 ms
> --- www.analogic.com ping statistics ---
> 2 packets transmitted, 2 packets received, 0% packet loss
> round-trip min/avg/max = 34.3/312.3/590.3 ms
> sailboat> telnet www.analogic.com 80
> Trying 204.178.41.218...
> telnet: Unable to connect to remote host: No route to host
>
> I am assuming that there must be a route to the host in order for
> ping to work.
>
> Here is the output of strace:
>
> socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 4
> getuid() = 502
> setuid(502) = 0
> connect(4, {sin_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("204.178.
> 41.218")}, 16) = -1 EHOSTUNREACH (No route to host)
>
> and the output of route:
> Kernel routing table
> Destination Gateway Genmask Flags MSS Window Use Iface
> localnet * 255.255.0.0 U 1500 0 19891 eth0
> loopback * 255.0.0.0 U 3584 0 541 lo
> default uncw-gw.gate.un * UG 1500 0 25797 eth0
>

Hth, JimL
_________________________________________
| James W. Laferriere | Network Engineer |
| babydr@nwrain.net | System Techniques |
| 25416 - 22nd S. | Kent, WA 98032 |
| Give me VMS -or- Give me Linux |
| but only on AXP |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
My libraries & programs status ( most are here now )

Linux-2.0.24 , eepro100.c/v0.12b/as module (the only one)
Gcc v. 2.7.2 ; binutils-2.6.0.14 ; sysvinit-2.62
ld.so.1.7.14 ; libc.so.5.3.12 ; libc.so.4.7.6
libg++.so.27.1.4 ;
proc-ps 0.99 ; net-tools 1.2.0 ; mount-2.5j
Modules 2.0.0 ; loadkeys 0.89 ;

--- Linux-Vax Port, Still in Progress . IE: No Progress To Report. ;-) ---