It resolves: $ ping 209.61.157.176 PING 209.61.157.176 (209.61.157.176) from 10.0.0.4 : 56(84) bytes of data. 64 bytes from ping.net (209.61.157.176): icmp_seq=0 ttl=234 time=200.5 ms 64 bytes from ping.net (209.61.157.176): icmp_seq=1 ttl=234 time=185.9 ms 64 bytes from ping.net (209.61.157.176): icmp_seq=2 ttl=234 time=201.3 ms 64 bytes from ping.net (209.61.157.176): icmp_seq=3 ttl=234 time=185.1 ms --- 209.61.157.176 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 185.1/193.2/201.3 ms Ketil On Wed, 11 Apr 2001, Isabelle, Francois wrote: > would the resolver be invoked even with the IP supplied, I though it was > invoked when host is reached via a name, i'll tri that anyway thanx > > > -----Original Message----- > > From: Ketil Froyn [SMTP:linux-net+ketil@froyn.com] > > Sent: 11 avril, 2001 16:25 > > To: Isabelle, Francois > > Cc: linux-net@vger.kernel.org > > Subject: Re: RedHat 6.2 - ICMP Echo request works one way only or > > works only w ith "-f" option > > > > On Wed, 11 Apr 2001, Isabelle, Francois wrote: > > > > > on the client: > > > ping -f 192.168.1.1 # works well > > > ftp 192.168.1.1 #works well > > > .... > > > > > > ping 192.168.1.1 #does not work , or works 1 packet / each > > > 70000 ms why ? > > > > Maybe the client tries to look up the IP address 192.168.1.1. Try > > "ping -n 192.168.1.1" also. > > > > Network timeouts like that are usually DNS timeouts, in my experience. If > > something takes X seconds longer each time, check if resolving works > > first. > > > > Ketil > > > > - > > : send the line "unsubscribe linux-net" in > > the body of a message to majordomo@vger.kernel.org > - > : send the line "unsubscribe linux-net" in > the body of a message to majordomo@vger.kernel.org > - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org
