Date: Mon, 1 Jan 2007 17:00:16 +0300 (MSK) From: .@babolo.ru To: Matthew Hudson <fbsd@synoptic.org> Cc: Stephan Wehner <stephanwehner@gmail.com>, freebsd-net@freebsd.org Subject: Re: Diagnose co-location networking problem Message-ID: <1167660016.168305.67043.nullmailer@cicuta.babolo.ru> In-Reply-To: <20061228203100.GA1165@gort.synoptic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Wed, Dec 27, 2006 at 10:08:25PM -0800, Stephan Wehner wrote: ... > Oh, also, going back to the 198.168 address seen in the client dumps, > it's clear that you're going through a NAT firewall or VPN or something > on the way to your server. Thus are you able to reproduce this problem > from a different external network? > > Actually, I just realized that you've provided enough information for me > to run this test myself which I've now done. I ran the following test; > > i=0; while true; do ((i++)); echo $i; curl http://stbgo.org > /dev/null; done > > I was able to make over 64 consecutive connections without a single failure > before I stopped the test (didn't want to spam your site). How sure > are you that this isn't a client-side problem? /usr/ports/net/scand/ designed for such a problem on client side when overactive.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1167660016.168305.67043.nullmailer>