Date: Mon, 04 Jan 1999 10:04:51 +0100 From: sthaug@nethelp.no To: mike@smith.net.au Cc: dcs@newsguy.com, jkh@zippy.cdrom.com, freebsd-current@FreeBSD.ORG, freebsd-admin@FreeBSD.ORG Subject: Re: 3.0-19981226-SNAP/src/ssys.ac is corrupt Message-ID: <24748.915440691@verdi.nethelp.no> In-Reply-To: Your message of "Mon, 04 Jan 1999 00:32:06 -0800" References: <199901040832.AAA11061@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > There's nothing wrong with this file - the problem is somewhere on > > > your end, or between our two sites. There's absolutely nothing we > > > can do about it here. > > > > Err... I happen to have seen the exact same problem. I tried four > > times to install the sys sources, and each time the connection would > > stop at the precise same point. ... > This is usually a "magic byte sequence" which blows the brains out of > something in the transit path. We've seen a few of these. Maybe it should be investigated more closely. I see the same problem from three different hosts here in Norway, connected via two different ISPs and using very different paths: 1. From hegre.uninett.no: traceroute to usw2.freebsd.org (209.180.6.226), 30 hops max, 40 byte packets 1 unit-gw.unit.no (129.241.1.2) 2.010 ms 3.109 ms 1.165 ms 2 trdS-gw (129.241.181.15) 1.670 ms 5.680 ms 1.326 ms 3 osloS-gw (128.39.46.1) 8.051 ms 8.014 ms 9.111 ms 4 no-gw2.nordu.net (128.39.2.1) 9.539 ms 8.289 ms 8.386 ms 5 sw-gw.nordu.net (193.10.252.149) 19.024 ms 18.836 ms 19.853 ms 6 us-gw.nordu.net (193.10.252.138) 116.364 ms 118.197 ms 117.190 ms 7 gin-nyy-core1.Teleglobe.net (207.45.202.17) 117.310 ms 118.283 ms 117.313 ms 8 gin-nyy-bb1.Teleglobe.net (207.45.223.170) 117.740 ms 119.055 ms 120.379 ms 9 Serial1-0-1.GW2.NYC2.ALTER.NET (157.130.5.217) 120.275 ms Serial0-1-0.GW2.NYC2.ALTER.NET (157.130.4.165) 119.525 ms Serial1-0-1.GW2.NYC2.ALTER.NET (157.130.5.217) 118.513 ms 10 144.ATM2-0.XR2.NYC1.ALTER.NET (146.188.178.150) 122.257 ms 118.006 ms 119.339 ms 11 194.ATM3-0.TR2.NYC1.ALTER.NET (146.188.178.198) 119.394 ms 118.765 ms 121.182 ms 12 104.ATM7-0.TR2.CHI4.ALTER.NET (146.188.136.153) 141.189 ms 141.879 ms 140.252 ms 13 198.ATM6-0.XR2.CHI6.ALTER.NET (146.188.209.1) 141.568 ms 141.105 ms 140.681 ms 14 190.ATM8-0-0.GW2.MSP1.ALTER.NET (146.188.209.125) 154.812 ms 154.971 ms 155.309 ms 15 uswmsp-gw.customer.ALTER.NET (157.130.96.166) 149.941 ms 149.431 ms 150.794 ms 16 207.225.159.220 (207.225.159.220) 150.013 ms 149.056 ms 148.990 ms 17 usw2.freebsd.org (209.180.6.226) 150.841 ms 149.249 ms 151.275 ms 2. From newsfeed1.telia.no: traceroute to usw2.freebsd.org (209.180.6.226), 30 hops max, 40 byte packets 1 194.19.1.49 (194.19.1.49) 0.963 ms 0.854 ms 0.834 ms 2 194.19.1.94 (194.19.1.94) 1.441 ms 1.665 ms 1.308 ms 3 194.19.1.146 (194.19.1.146) 19.590 ms 20.661 ms 19.916 ms 4 apv-c2-fddi5-0-core.stockholm.telia.net (194.22.194.253) 15.771 ms 14.808 ms 14.310 ms 5 apv-i1-feth4-0-0-ix.stockholm.telia.net (195.67.232.8) 14.443 ms 16.892 ms 15.514 ms 6 ny-i1-pos4-0-0-int-newyork.telia.net (194.17.0.250) 111.639 ms 110.964 ms 110.338 ms 7 209.95.130.138 (209.95.130.138) 112.581 ms 113.056 ms 111.801 ms 8 MAE-East-hssi2-0-int.vienna.telia.net (209.95.128.37) 119.952 ms 118.003 ms 117.990 ms 9 maeeast2.bbnplanet.net (198.32.186.2) 131.367 ms 123.608 ms 127.574 ms 10 p2-2.vienna1-nbr2.bbnplanet.net (4.0.1.93) 123.232 ms 117.797 ms 120.134 ms 11 p3-1.nyc4-nbr2.bbnplanet.net (4.0.3.130) 120.709 ms 127.382 ms 121.752 ms 12 p1-0.nyc4-nbr3.bbnplanet.net (4.0.5.26) 123.863 ms 124.764 ms 123.996 ms 13 p2-1.chicago1-nbr1.bbnplanet.net (4.0.3.121) 146.194 ms 144.213 ms 140.665 ms 14 p10-0-0.chicago1-br1.bbnplanet.net (4.0.5.89) 150.874 ms 139.794 ms 138.179 ms 15 h1-0.minneapol1-cr1.bbnplanet.net (4.0.2.18) 151.672 ms 150.914 ms 151.956 ms 16 h1-0.uswest-mn.bbnplanet.net (4.0.246.254) 154.703 ms 148.461 ms 148.034 ms 17 207.225.159.220 (207.225.159.220) 149.299 ms 154.605 ms 151.377 ms 18 usw2.freebsd.org (209.180.6.226) 167.212 ms 156.491 ms * The only points in common for these two traceroutes are usw2.freebsd.org, and the router at 207.225.159.220. That should narrow the field sufficiently that it's possible to investigate. It's the same file I'm trying to fetch (3.0-19981226-SNAP/src/ssys.ac). Also, I've tried it from both FreeBSD and SunOS 4.1.4 clients. Same problem. A tcpdump shows no packets from usw2.freebsd.org after a certain point, which is consistent with the FTP session hanging: ... 10:01:22.655241 209.180.6.226.59113 > 129.241.1.42.1169: . 156985:158433(1448) ack 1 win 17376 <nop,nop,timestamp 919238 8540842> (DF) [tos 0x8] 10:01:22.655569 209.180.6.226.59113 > 129.241.1.42.1169: . 158433:159881(1448) ack 1 win 17376 <nop,nop,timestamp 919238 8540842> (DF) [tos 0x8] 10:01:22.658650 209.180.6.226.59113 > 129.241.1.42.1169: . 159881:161329(1448) ack 1 win 17376 <nop,nop,timestamp 919238 8540842> (DF) [tos 0x8] 10:01:22.659172 209.180.6.226.59113 > 129.241.1.42.1169: . 161329:162777(1448) ack 1 win 17376 <nop,nop,timestamp 919238 8540842> (DF) [tos 0x8] 10:01:22.665906 129.241.1.42.1169 > 209.180.6.226.59113: . ack 159881 win 17376 <nop,nop,timestamp 8540842 919238> (DF) [tos 0x8] 10:01:22.669349 129.241.1.42.1169 > 209.180.6.226.59113: . ack 162777 win 17376 <nop,nop,timestamp 8540842 919238> (DF) [tos 0x8] 10:01:22.679161 209.180.6.226.59113 > 129.241.1.42.1169: . 162777:164225(1448) ack 1 win 17376 <nop,nop,timestamp 919238 8540842> (DF) [tos 0x8] 10:01:22.680143 209.180.6.226.59113 > 129.241.1.42.1169: . 164225:165673(1448) ack 1 win 17376 <nop,nop,timestamp 919238 8540842> (DF) [tos 0x8] 10:01:22.695234 129.241.1.42.1169 > 209.180.6.226.59113: . ack 165673 win 17376 <nop,nop,timestamp 8540842 919238> (DF) [tos 0x8] 10:01:22.789428 209.180.6.226.59113 > 129.241.1.42.1169: P 165673:167121(1448) ack 1 win 17376 <nop,nop,timestamp 919238 8540842> (DF) [tos 0x8] 10:01:22.914620 129.241.1.42.1169 > 209.180.6.226.59113: . ack 167121 win 17376 <nop,nop,timestamp 8540842 919238> (DF) [tos 0x8] (no more from the remote end. Always at the same point.) Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24748.915440691>