Date: Thu, 22 Feb 2007 14:20:58 -0600 From: Kevin Day <toasty@dragondata.com> To: Jeremy Nelson <chekorn@yahoo.com> Cc: freebsd-net@freebsd.org Subject: Re: 5.4-RELEASE and 5.5-RELEASE Slow routing table response Message-ID: <FB112A05-28E4-46C0-B3D9-76420F516024@dragondata.com> In-Reply-To: <784231.40396.qm@web52305.mail.yahoo.com> References: <784231.40396.qm@web52305.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FB112A05-28E4-46C0-B3D9-76420F516024>