From owner-freebsd-hubs Thu Apr 19 14:47:37 2001 Delivered-To: freebsd-hubs@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id BE90C37B424; Thu, 19 Apr 2001 14:47:33 -0700 (PDT) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id C74205D60; Thu, 19 Apr 2001 23:48:13 +0200 (CEST) Date: Thu, 19 Apr 2001 23:48:13 +0200 From: Jesper Skriver To: noc@lightning.net Cc: dg@FreeBSD.org, hubs@FreeBSD.org Subject: Packet loss between fa0-0.br1.nycmny.us and a1-0-1.cr2.nycmny1.us towards ftp.freesoftware.com Message-ID: <20010419234813.A61420@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 6B88 9CE8 66E9 E631 C9C5 5EB4 22AB F0EC F956 1C31 X-PGP-Public-Key: http://freesbee.wheel.dk/~jesper/gpgkey.pub Sender: owner-freebsd-hubs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I see massive packet loss towards ftp.freesoftware.com from hosts in AS3292 (this test was performed from 195.249.6.93, a interface on ftp.dk.FreeBSD.org), it seems that it appear in your network between 12 fa0-0.br1.nycmny.us.lightning.net (209.244.186.10) 94.871 ms 95.351 ms 94.692 ms and 13 a1-0-1.cr2.nycmny1.us.lightning.net (216.66.3.2) 129.998 ms 134.664 ms * Do the return path to 195.249.6.93 change between these ? or is there a congestion problem between these hops ? Traceroute and ping's below. PS: This severy affect the ability to mirror ftp.FreeBSD.org on ftp.dk.FreeBSD.org, do other of you mirror admin's have the same problem ? /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. jesper@boulder% traceroute ftp.freebsd.org traceroute to ftp.freesoftware.com (216.66.64.162), 30 hops max, 40 byte packets 1 fe8-1-0-6.100M.sltnxt2.ip.tele.dk (195.249.6.90) 0.497 ms 0.379 ms 0.403 ms 2 pos0-3.155M.arcnxg2.ip.tele.dk (195.249.12.245) 0.528 ms 0.476 ms 0.446 ms 3 pos6-0.2488M.arcnxg1.ip.tele.dk (195.249.6.101) 0.650 ms 0.546 ms 0.570 ms 4 pos7-0.2488M.albnxg1.ip.tele.dk (195.249.6.125) 2.656 ms 2.503 ms 2.531 ms 5 pos2-1.155M.linxnxg1.ip.tele.dk (195.249.2.170) 21.336 ms 21.197 ms 22.143 ms 6 GigabitEthernet5-0.linx1.lon1.level3.net (195.66.224.77) 21.475 ms 21.874 ms 21.403 ms 7 so-4-2-0-0.mp1.lon1.level3.net (212.113.0.114) 22.134 ms 21.894 ms 21.727 ms 8 so-3-0-0-0.mp1.lon2.level3.net (212.187.128.46) 21.987 ms 21.867 ms 22.178 ms 9 212.187.128.162 (212.187.128.162) 97.400 ms 94.093 ms 99.840 ms 10 pos8-0.core1.NewYork1.level3.net (209.247.10.34) 96.162 ms 93.884 ms 102.018 ms 11 gigaethernet6-0.ipcolo1.NewYork1.Level3.net (209.244.12.42) 96.653 ms 94.800 ms 95.425 ms 12 fa0-0.br1.nycmny.us.lightning.net (209.244.186.10) 94.871 ms 95.351 ms 94.692 ms 13 a1-0-1.cr2.nycmny1.us.lightning.net (216.66.3.2) 129.998 ms 134.664 ms * 14 s7-1.br1.nycmny1.us.lightning.net (216.66.3.29) 142.591 ms 121.387 ms 114.920 ms 15 ftp.freesoftware.com (216.66.64.162) 129.444 ms^C jesper@boulder% ping -c 100 209.244.186.10 PING 209.244.186.10 (209.244.186.10): 56 data bytes --- 209.244.186.10 ping statistics --- 100 packets transmitted, 100 packets received, 0% packet loss round-trip min/avg/max/stddev = 93.324/103.648/196.783/13.205 ms jesper@boulder% ping -c 100 216.66.3.2 PING 216.66.3.2 (216.66.3.2): 56 data bytes --- 216.66.3.2 ping statistics --- 100 packets transmitted, 85 packets received, 15% packet loss round-trip min/avg/max/stddev = 100.401/141.587/434.243/56.072 ms jesper@boulder% ping -c 100 ftp.freebsd.org PING ftp.freesoftware.com (216.66.64.162): 56 data bytes --- ftp.freesoftware.com ping statistics --- 100 packets transmitted, 75 packets received, 25% packet loss round-trip min/avg/max/stddev = 100.376/138.354/168.176/14.340 ms To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message