From owner-freebsd-questions@FreeBSD.ORG Mon Jun 9 12:12:27 2008 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 CCAA9106568D for ; Mon, 9 Jun 2008 12:12:27 +0000 (UTC) (envelope-from fbsd06+WX=50118bc6@mlists.homeunix.com) Received: from turtle-out.mxes.net (turtle-out.mxes.net [216.86.168.191]) by mx1.freebsd.org (Postfix) with ESMTP id 8F71B8FC22 for ; Mon, 9 Jun 2008 12:12:27 +0000 (UTC) (envelope-from fbsd06+WX=50118bc6@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by turtle-in.mxes.net (Postfix) with ESMTP id B89D3163DFB for ; Mon, 9 Jun 2008 07:56:17 -0400 (EDT) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 0E13223E4C3 for ; Mon, 9 Jun 2008 07:56:15 -0400 (EDT) Date: Mon, 9 Jun 2008 12:56:13 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20080609125613.247b15bb@gumby.homeunix.com.> In-Reply-To: <200806082019.04350.af300wsm@gmail.com> References: <200806082019.04350.af300wsm@gmail.com> X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.10; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Networking issues 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: Mon, 09 Jun 2008 12:12:27 -0000 On Sun, 8 Jun 2008 20:19:04 -0600 Andrew Falanga wrote: > Hello, > > I have, for some time, been able to ssh into my father's FreeBSD > machine in the Road Runner network in Central New York. Last night, > I tried so that I could fix a problem for him and ssh timed out. No > problem I thought, his modem has a different IP than the one I have > in my /etc/hosts file, but this turned to not be the case. > > Well, after some digging, I did a traceroute to his IP address. The > packets went all over the place, from San Jose, to Colorado, back to > San Jose, to Colorado then to Ohio, then to Denver, then to San Jose, > then to Ohio, etc. (you get the idea). This is not necessarily wrong, I used to have a dialup account where connections within the UK would go often go to London, then go round a tour of Western Europe, and then come back through London. Although there probably is a fault in your case since you can't connect. > First, my DSL modems IP is 71.221.172.38, however, the default route > appears to be 67.41.38.201. I think Point-to-Point links just work like that, with arbitrary addresses on either end of the link. My address and gateway have only the first byte in common. > [/usr/home/andy] > -> traceroute -n 67.41.38.201 > traceroute to 67.41.38.201 (67.41.38.201), 64 hops max, 52 byte > packets 1 * * * > 2 67.41.38.201 40.303 ms * 39.421 ms > > Why on earth would there be delays on the first hop when not using > name resolution? I don't see what name resolution has to do with the delay, the 39ms is the round-trip time to the gateway at the ISP.