From owner-freebsd-net@FreeBSD.ORG Thu Jan 4 19:34:17 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 33E0D16A403 for ; Thu, 4 Jan 2007 19:34:17 +0000 (UTC) (envelope-from fbsd@synoptic.org) Received: from gort.synoptic.org (gort.synoptic.org [216.254.17.65]) by mx1.freebsd.org (Postfix) with ESMTP id 1790613C457 for ; Thu, 4 Jan 2007 19:34:17 +0000 (UTC) (envelope-from fbsd@synoptic.org) Received: by gort.synoptic.org (Postfix, from userid 1000) id D1FD26352885; Thu, 4 Jan 2007 11:34:16 -0800 (PST) Date: Thu, 4 Jan 2007 11:34:16 -0800 From: Matthew Hudson To: Stephan Wehner , freebsd-net@freebsd.org Message-ID: <20070104193416.GA47635@gort.synoptic.org> References: <20061228203100.GA1165@gort.synoptic.org> <1167660016.168305.67043.nullmailer@cicuta.babolo.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: Subject: Re: Diagnose co-location networking problem 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, 04 Jan 2007 19:34:17 -0000 On Mon, Jan 01, 2007 at 08:07:59PM -0800, Stephan Wehner wrote: > Hello again, > > to give a short summary; I contacted this list to ask for help with > diagnosing a problem with a co-located server (accessible at > http://stbgo.org) running FreeBSD 6.1. When I swamp it with requests > (simply, lynx -dump http://stbgo.org > /dev/null in a loop) > some responses take 90 seconds -- far too long. This is reproducible, > but seemingly not from other source addresses - only my own (home) > machine, 64.114.83.92 Stephan, I haven't yet looked at the new data you've reported because of the last point that you mention, the point that I brought up in my previous email, is of critical importance. There is currently evidence that suggests the possibility that this problem is not reproduceable from anywhere but your home network. If that is indeed the case then what you have is likely not a problem with the FreeBSD networking code on your colocated box but rather a problem with your home network. If so, then this is the wrong forum to seek assistance in troubleshooting a non-FreeBSD networking problem. Before we can meaningfully assist you with your issue here, we're going to need to see evidence that shifts the finger of blame back towards the FreeBSD networking code and away from your home network where it is currently pointing. cheers, -- Matthew Hudson