From owner-freebsd-questions Fri Nov 24 12:45:16 2000 Delivered-To: freebsd-questions@freebsd.org Received: from comnet.ca (comnet.ca [207.107.47.2]) by hub.freebsd.org (Postfix) with ESMTP id 4EE9C37B4CF; Fri, 24 Nov 2000 12:45:08 -0800 (PST) Received: from spruce (d-25.comnet.ca [207.107.44.25]) by comnet.ca (8.10.0/8.10.0) with SMTP id eAOKj2R24729; Fri, 24 Nov 2000 15:45:06 -0500 (EST) Message-Id: <3.0.5.32.20001124154621.008a4180@205.206.213.2> X-Sender: mkuchta@205.206.213.2 X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 24 Nov 2000 15:46:21 -0500 To: freebsd-questions@FreeBSD.ORG From: Milan Kuchta Subject: Re: www.freebsd.org website Cc: wosch@FreeBSD.ORG In-Reply-To: References: <3.0.5.32.20001124100813.008abc80@205.206.213.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for your excellent suggestion (which I should have thought of). The traceroutes follow. The problem appears to be after T1-CDROM-00-EX.US.CRL.COM [165.113.118.2]. This is clearly not mine to fix but hopefully whoever is responsible for the freebsd.org domain can get it fixed. BTW. I did realize the site was up since a local friend does not have a problem reaching it (presumably since his ISP goes through some other set of routes totally). Thanks again. Milan Kuchta ---------------> Tracing route to www.freebsd.org [204.216.27.21] over a maximum of 30 hops: 1 141 ms 144 ms 143 ms pm16.comnet.ca [207.107.47.104] 2 145 ms 144 ms 152 ms spr-gateway.comnet.ca [207.107.47.1] 3 151 ms 146 ms 153 ms spc-mon-1-Serial-9-4.Sprint-Canada.Net [207.107. 247.121] 4 169 ms 158 ms 165 ms spc-isp-nitro-01-66.sprint.ca [207.107.254.66] 5 196 ms 158 ms 163 ms sl-gw9-nyc-2-0.sprintlink.net [144.232.173.17] 6 168 ms 184 ms 154 ms sl-bb20-nyc-3-0.sprintlink.net [144.232.7.93] 7 180 ms 168 ms 179 ms sl-bb22-rly-13-0.sprintlink.net [144.232.9.226] 8 175 ms 165 ms 170 ms 144.232.25.214 9 427 ms 191 ms 171 ms sl-e2-mae-0-1-0.sprintlink.net [144.228.10.42] 10 170 ms 163 ms 174 ms mae-e-1.e0.crl.com [192.41.177.104] 11 288 ms 260 ms 273 ms vva1-sfo2.ATM.us.crl.com [165.113.0.253] 12 270 ms 282 ms 263 ms E0-CRL-SFO-03-E0X0.US.CRL.COM [165.113.55.3] 13 294 ms 274 ms 267 ms T1-CDROM-00-EX.US.CRL.COM [165.113.118.2] 14 * * * Request timed out. 15 * Tracing route to www.freebsd.org [204.216.27.21] over a maximum of 30 hops: 1 140 ms 136 ms 135 ms tnt5.ottawa.on.da.uu.net [142.77.230.79] 2 131 ms 138 ms 138 ms dr.t1.tnt5.ottawa.on.da.uu.net [142.77.230.193] 3 137 ms 136 ms 140 ms 121.ATM5-0-0.HR1.TOR2.ALTER.NET [152.63.131.94] 4 1391 ms 1822 ms 1820 ms 101.ATM2-0.XR1.TOR2.ALTER.NET [152.63.128.130] 5 248 ms 144 ms 143 ms 195.ATM3-0.TR1.TOR2.ALTER.NET [152.63.128.38] 6 160 ms 163 ms 160 ms 137.at-7-3-0.TR1.DCA8.ALTER.NET [146.188.141.209 ] 7 169 ms 166 ms 166 ms 197.at-5-0-0.XR1.TCO1.ALTER.NET [152.63.32.189] 8 165 ms 166 ms 166 ms 193.ATM11-0-0.BR2.TCO1.ALTER.NET [146.188.160.89 ] 9 170 ms 164 ms 166 ms mae-e-1.e0.crl.com [192.41.177.104] 10 250 ms 251 ms 250 ms vva1-sfo2.ATM.us.crl.com [165.113.0.253] 11 250 ms 252 ms 247 ms E0-CRL-SFO-03-E0X0.US.CRL.COM [165.113.55.3] 12 253 ms 258 ms 256 ms T1-CDROM-00-EX.US.CRL.COM [165.113.118.2] 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. At 12:29 PM 11/24/00 -0500, Francisco Reyes wrote: >On Fri, 24 Nov 2000, Milan Kuchta wrote: > >> Can you please explain why I can not get to www.freebsd.org > >Chances are that is is a problem on your upstream ISP or somewhere along >the line to that site or some misconfiguration somewhere. I access that >site in one way or another almost every day.. also ftp.freebsd.org. > >I even just tried it a second ago with no problems. > >Try a traceroute (or tracert if on NT) and see where the packets are >getting stuck. > >>If there is a "rational" explanation for these, please have the mirror sites >> include a "please read this" link. > >Unless you see MANY other people complaining about the same problem more >often than not these connectivity problems are on the user's computer or >ISP. On the rare cases when Freebsd.org has problems you usually see >several messages to that regard from different people. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message