,--[ On Fri, Dec 28, 2007 at 04:33:48PM +0530, Siju George wrote: | Hi, | | I have been noticing this for many days. | | When I ping google.com from my OpenBSD firewall I always get packet | loss where as other sites don't give any packet loss. | | Is there anybody experiencing the same problem?
I also tried this on one of my remote GNU/Linux box, and found the similar results: [EMAIL PROTECTED]:~$ ping -c20 google.com PING google.com (64.233.187.99) 56(84) bytes of data. 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=4 ttl=249 time=58.5 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=5 ttl=249 time=59.2 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=7 ttl=249 time=58.6 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=8 ttl=249 time=57.7 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=9 ttl=249 time=59.1 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=10 ttl=249 time=58.7 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=11 ttl=249 time=65.5 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=12 ttl=249 time=58.4 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=13 ttl=249 time=59.7 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=14 ttl=249 time=57.7 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=15 ttl=249 time=58.7 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=16 ttl=249 time=58.5 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=17 ttl=249 time=58.6 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=18 ttl=249 time=58.5 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=19 ttl=249 time=59.0 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=20 ttl=249 time=58.4 ms --- google.com ping statistics --- 20 packets transmitted, 16 received, 20% packet loss, time 19149ms rtt min/avg/max/mdev = 57.723/59.110/65.527/1.733 ms [EMAIL PROTECTED]:~$ ping -c20 yahoo.com PING yahoo.com (216.109.112.135) 56(84) bytes of data. 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=1 ttl=56 time=73.0 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=2 ttl=56 time=73.1 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=3 ttl=56 time=73.2 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=4 ttl=56 time=73.0 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=5 ttl=56 time=72.9 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=6 ttl=56 time=72.8 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=7 ttl=56 time=72.9 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=8 ttl=56 time=72.9 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=9 ttl=56 time=73.0 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=10 ttl=56 time=73.5 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=11 ttl=56 time=73.0 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=12 ttl=56 time=73.1 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=13 ttl=56 time=72.8 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=14 ttl=56 time=73.2 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=15 ttl=56 time=72.8 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=16 ttl=56 time=73.2 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=17 ttl=56 time=73.0 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=18 ttl=56 time=72.7 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=19 ttl=56 time=73.0 ms 64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=20 ttl=56 time=72.8 ms --- yahoo.com ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19190ms rtt min/avg/max/mdev = 72.788/73.057/73.574/0.311 ms [EMAIL PROTECTED]:~$ ping -c20 openbsd.org PING openbsd.org (199.185.137.3) 56(84) bytes of data. 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=1 ttl=241 time=89.0 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=2 ttl=241 time=88.6 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=3 ttl=241 time=91.5 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=4 ttl=241 time=93.5 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=5 ttl=241 time=92.1 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=6 ttl=241 time=113 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=7 ttl=241 time=103 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=8 ttl=241 time=89.2 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=9 ttl=241 time=89.0 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=10 ttl=241 time=89.2 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=11 ttl=241 time=88.5 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=12 ttl=241 time=105 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=13 ttl=241 time=88.5 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=14 ttl=241 time=95.9 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=15 ttl=241 time=97.5 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=16 ttl=241 time=96.2 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=17 ttl=241 time=95.7 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=18 ttl=241 time=94.5 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=19 ttl=241 time=89.5 ms 64 bytes from cvs.openbsd.org (199.185.137.3): icmp_seq=20 ttl=241 time=91.8 ms --- openbsd.org ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 19187ms rtt min/avg/max/mdev = 88.575/94.168/113.197/6.464 ms Looks like Google is taking preventive measure against Ping flood[1] . References: [1] - http://en.wikipedia.org/wiki/Ping_flood HTH -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ···· ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- --
signature.asc
Description: Digital signature
_______________________________________________ bsd-india mailing list [email protected] http://www.bsd-india.org/mailman/listinfo/bsd-india
