From owner-freebsd-net@FreeBSD.ORG Thu Feb 22 20:40:32 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5F73A16A405 for ; Thu, 22 Feb 2007 20:40:32 +0000 (UTC) (envelope-from toasty@dragondata.com) Received: from tokyo01.jp.mail.your.org (tokyo01.jp.mail.your.org [204.9.54.5]) by mx1.freebsd.org (Postfix) with ESMTP id 3168713C4B9 for ; Thu, 22 Feb 2007 20:40:32 +0000 (UTC) (envelope-from toasty@dragondata.com) Received: from mail.your.org (server3-a.your.org [64.202.112.67]) by tokyo01.jp.mail.your.org (Postfix) with ESMTP id 199602AD5540; Thu, 22 Feb 2007 20:20:52 +0000 (UTC) Received: from [69.31.99.11] (pool011.dhcp.your.org [69.31.99.11]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.your.org (Postfix) with ESMTP id 6EBC6A0A44F; Thu, 22 Feb 2007 20:20:51 +0000 (UTC) In-Reply-To: <784231.40396.qm@web52305.mail.yahoo.com> References: <784231.40396.qm@web52305.mail.yahoo.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Kevin Day Date: Thu, 22 Feb 2007 14:20:58 -0600 To: Jeremy Nelson X-Mailer: Apple Mail (2.752.3) Cc: freebsd-net@freebsd.org Subject: Re: 5.4-RELEASE and 5.5-RELEASE Slow routing table response X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Feb 2007 20:40:32 -0000 On Feb 22, 2007, at 1:45 PM, Jeremy Nelson wrote: > I have an Internet proxy that is running FreeBSD 5.4-RELEASE. This > server has been up and running beautifully for about a year and a > half with no issues. > > Just the other day I had a user try to connect to a host on the > Internet and her connection was failing. At first I thought that > it was the receiving host's issue because we were having no other > Internet connection issues through the proxy. However, I ran a > test connection from my home and found that everything worked fine. > > After investigating the issue I found that if I ran a "route get > xxx.xxx.xxx.xxx" on my proxy server it would take 1.25 minutes for > the route to come back. This same delay was also experienced if I > tried to use telnet to open a connection to the remote host. After > about 1.25 minutes the session would open successfully. > > So I ran "route monitor" and found that when I execute the "route > get" command the RTM_GET returns the appropriate route almost > immediately but there is still a substantial delay in the "route > get" command displaying the response. > > I ran this test on three other 5.4 and one 5.5 servers and found > that they all had the same issue. However, if I ran the same > "route get" command on a 5.3 server it works just fine. > > After all of my testing I wanted to know exactly what IP address > range was affected and found that it is limited to just 60 address > within a specific range (I can provide the range). > > Any help you could provide would be greatly appreciated. > > This is almost definitely a DNS issue. Try "route -n get" or "telnet -N" and see if it still happens. -- Kevin