From owner-freebsd-net@FreeBSD.ORG Tue Jun 12 17:13:22 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 95E8616A400 for ; Tue, 12 Jun 2007 17:13:22 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id 5CBA713C45B for ; Tue, 12 Jun 2007 17:13:22 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from vanquish.pgh.priv.collaborativefusion.com (vanquish.pgh.priv.collaborativefusion.com [192.168.2.61]) (SSL: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Tue, 12 Jun 2007 13:13:21 -0400 id 00056405.466ED431.0000C091 Date: Tue, 12 Jun 2007 13:13:20 -0400 From: Bill Moran To: Andre Oppermann Message-Id: <20070612131320.c120cd00.wmoran@collaborativefusion.com> In-Reply-To: <466EBE3E.3050105@freebsd.org> References: <20070612101949.646dcaa5.wmoran@collaborativefusion.com> <466EBE3E.3050105@freebsd.org> Organization: Collaborative Fusion X-Mailer: Sylpheed 2.3.1 (GTK+ 2.10.11; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Weird "ignoring syn" 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: Tue, 12 Jun 2007 17:13:22 -0000 In response to Andre Oppermann : > > Before we go into more detail: > > a) the em(4) driver is most likely totally unrelated to this Are you saying it's more likely to be a tcp stack problem? As an experiment, I tried to reproduce it over the loopback and was unable to, which points back toward the em driver ... > b) you may run out of socket on the client side and reuse them > too fast. Try to lower net.inet.ip.portrange.first to 30,000 > or so. I find that unlikely. The problem usually occurs reliably after less than 200 connections, and frequently after less than 50. > c) related to (b) you may have a lot of connections in TIME_WAIT > on the server catching not really stray packets. Try it with > net.inet.tcp.nolocaltimewait=1 That's the default. Also, I see no change in the behaviour of TIME_WAIT states (based on the output of netstat -f inet) no matter what I change that value to. And, just to finish out the debugging steps, the problem occurs with nolocaltimewait set to both 0 and 1. > d) if the above didn't help then it'd be very helpful to test > against a server with FreeBSD-current (the future 7.0) on > it. In -current we've got detailed logging of LISTEN socket > failures that allow rapid analysis of the problem. This will take some time. Also, I'm not seeing the problem on other, similar hardware. I'm considering swapping out that NIC to see if it might be buggy HW. -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ wmoran@collaborativefusion.com Phone: 412-422-3463x4023