From owner-freebsd-questions@FreeBSD.ORG Wed Mar 18 03:34:13 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CC2810656D0 for ; Wed, 18 Mar 2009 03:34:13 +0000 (UTC) (envelope-from chowse@charter.net) Received: from mta31.charter.net (mta31.charter.net [216.33.127.82]) by mx1.freebsd.org (Postfix) with ESMTP id D1BCD8FC16 for ; Wed, 18 Mar 2009 03:34:12 +0000 (UTC) (envelope-from chowse@charter.net) Received: from imp11 ([10.20.200.11]) by mta31.charter.net (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090318033400.VNUH2647.mta31.charter.net@imp11> for ; Tue, 17 Mar 2009 23:34:00 -0400 Received: from [192.168.100.3] ([24.176.102.105]) by imp11 with charter.net id UTZz1b00S2GSkqY05Ta058; Tue, 17 Mar 2009 23:34:00 -0400 Message-Id: <49442761-BB46-4C07-B4D5-419F7F49EFF7@charter.net> From: Charles Howse To: FreeBSD Questions In-Reply-To: <49C05D02.80703@ibctech.ca> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 17 Mar 2009 22:33:59 -0500 References: <25F15A6A-6A95-4500-9831-9021A5102450@charter.net> <20090317191354.4c98b2de@sbcglobal.net> <49C040C9.3090107@ibctech.ca> <89C4FE48-2536-44A9-B777-F82F03A92FC9@charter.net> <49C05103.2000709@ibctech.ca> <49C05D02.80703@ibctech.ca> X-Mailer: Apple Mail (2.930.3) Subject: Re: Physical location of cvsup servers X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Mar 2009 03:34:13 -0000 On Mar 17, 2009, at 9:31 PM, Steve Bertrand wrote: > Charles Howse wrote: >> >> On Mar 17, 2009, at 8:40 PM, Steve Bertrand wrote: > >>> What do you want to achieve? fastest_cvsup will tell you >>> addressing of >>> the servers. You will have to contact those responsible for the >>> IPs to >>> see where they are located to ensure any form of accuracy regarding >>> geo-location. >> >> Mainly, it's curiosity. I know-fer-a-fact I saw a list of physical >> locations back when 4.x was the latest release. Probably been >> deleted. >> >> fastest_cvsup usually tells me #17 is fastest, but it times out a >> lot, I >> mean A LOT, from here. > > Fastest, (in this case) != most reliable. > > Can you produce the output of fastest_cvsup, include the top two > results > (add #17 if it isn't included), and then provide the output of a > traceroute to #17? root@curly /root# fastest_cvsup -c us >> Querying servers in countries: us --> Connecting to cvsup.us.freebsd.org [198.104.69.57]... * error: connect: timeout --> Connecting to cvsup2.us.freebsd.org [130.94.149.166]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 62.86 ms --> Connecting to cvsup3.us.freebsd.org [128.31.0.28]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 55.50 ms --> Connecting to cvsup4.us.freebsd.org [204.152.184.73]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 90.92 ms --> Connecting to cvsup5.us.freebsd.org [208.83.20.166]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 81.31 ms --> Connecting to cvsup6.us.freebsd.org [216.14.98.190]... * error: connect: timeout --> Connecting to cvsup7.us.freebsd.org [128.205.32.60]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 67.65 ms --> Connecting to cvsup8.us.freebsd.org [216.165.129.134]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 68.22 ms --> Connecting to cvsup9.us.freebsd.org [128.205.32.21]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 66.51 ms --> Connecting to cvsup10.us.freebsd.org [69.147.83.48]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 97.16 ms --> Connecting to cvsup11.us.freebsd.org [63.87.62.77]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 50.68 ms --> Connecting to cvsup12.us.freebsd.org [128.46.156.46]... * error: connect: timeout --> Connecting to cvsup13.us.freebsd.org [216.32.84.70]... * error: connect: Invalid argument --> Connecting to cvsup14.us.freebsd.org [216.87.87.128]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 119.39 ms --> Connecting to cvsup15.us.freebsd.org [35.9.37.225]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 57.43 ms --> Connecting to cvsup16.us.freebsd.org [128.143.108.35]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 63.13 ms --> Connecting to cvsup17.us.freebsd.org [65.212.71.21]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 34.74 ms --> Connecting to cvsup18.us.freebsd.org [128.205.32.60]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 61.17 ms >> Speed Daemons: - 1st: cvsup17.us.freebsd.org 34.74 ms - 2st: cvsup11.us.freebsd.org 50.68 ms - 3st: cvsup3.us.freebsd.org 55.50 ms For some reason, traceroute has never worked on any of my *nix boxes. There are soooo many reasons that might cause that. Too many to go into, but mostly the way I set up my lan, the router settings and options, etc. I have 2 FreeBSD, a Mac, and an XP machine. On the XP machine, tracert times out after 12 hops, however the ip did resolve to..... "THE WEATHER CHANNEL" - ncvsup.twc.waether.com That in itself may be reason enough for the timeouts...? > > > Perhaps you have a faulty asymmetric path to 17... > > It is important to know that just because a server may be literally > located at the building across the street, it doesn't mean that you > are > guaranteed a path that may not cross the country (and in some > situations, across an ocean) and back. > > I don't know where you are located, but generally, I've found cvsup8 > to > be extremely quick (in terms of latency) and very reliable for a > number > of years. I'm in Central West Tennessee. > > > Steve