On Mon, 02 Aug 2004 23:30:05 +1200, Brendan Greer <[EMAIL PROTECTED]> wrote: > Thanks Chris > > And I just realised that I could have found out my self by trying to > ping a website I knew that was up. Remeber Alot of sites drop icmp ping requests. > Pinging google.com [216.239.39.99] with 32 bytes of data: Sometimes google drops icmp ping requests.
> Reply from 216.239.39.99: bytes=32 time=387ms TTL=236 > Reply from 216.239.39.99: bytes=32 time=393ms TTL=236 > Reply from 216.239.39.99: bytes=32 time=382ms TTL=236 > Reply from 216.239.39.99: bytes=32 time=380ms TTL=236 > > > > > > Yes. > > > >[EMAIL PROTECTED] ~ $ ping -c 2 202.0.37.152 > >PING 202.0.37.152 (202.0.37.152) 56(84) bytes of data. > >64 bytes from 202.0.37.152: icmp_seq=1 ttl=64 time=2.75 ms > >64 bytes from 202.0.37.152: icmp_seq=2 ttl=64 time=2.75 ms > > > >--- 202.0.37.152 ping statistics --- > >2 packets transmitted, 2 received, 0% packet loss, time 1000ms > >rtt min/avg/max/mdev = 2.752/2.754/2.756/0.002 ms > > > > > > -- --Ben Devine yeahhost.net
