From owner-freebsd-net@FreeBSD.ORG Thu Feb 22 20:12:03 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 CFDF416A400 for ; Thu, 22 Feb 2007 20:12:03 +0000 (UTC) (envelope-from chekorn@yahoo.com) Received: from web52305.mail.yahoo.com (web52305.mail.yahoo.com [206.190.48.148]) by mx1.freebsd.org (Postfix) with SMTP id 8039613C48D for ; Thu, 22 Feb 2007 20:12:03 +0000 (UTC) (envelope-from chekorn@yahoo.com) Received: (qmail 41201 invoked by uid 60001); 22 Feb 2007 19:45:22 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=ebgIsnbt+noduPeg1v/bL1ewVKV/plVAXnSu4uI+8Iax9nRZW2jSqRKEHqgkkrfjngxMuowRzFexERs1Yt4kGj9Mk+MluWX54kFoN9oUzLYk8RaPSJP1K5K525RF1tRCiLfGiR2a3FzS4AjklXQNyhyKIx8ZQwtXyg3KTEG7uyM=; X-YMail-OSG: kOd_6SoVM1lW11OGh3wWPW_2gix7pk8pnDaRuaBiz85t4ZUNeauKMUsmDJpsufBqqMrS6ZEm1na31y542XBJ4vSZVCW7yYE_wIKYzPIuHU40RXrXAYHEaNjgcZx3EiT068.480ogNGVZKUsi.M4ID1MC Received: from [208.251.106.83] by web52305.mail.yahoo.com via HTTP; Thu, 22 Feb 2007 11:45:22 PST Date: Thu, 22 Feb 2007 11:45:22 -0800 (PST) From: Jeremy Nelson To: freebsd-net@freebsd.org MIME-Version: 1.0 Message-ID: <784231.40396.qm@web52305.mail.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 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:12:04 -0000 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. --------------------------------- Don't get soaked. Take a quick peak at the forecast with theYahoo! Search weather shortcut.