From owner-freebsd-net@FreeBSD.ORG Mon Apr 4 12:07:56 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 865F01065674 for ; Mon, 4 Apr 2011 12:07:56 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by mx1.freebsd.org (Postfix) with ESMTP id 44BDB8FC17 for ; Mon, 4 Apr 2011 12:07:55 +0000 (UTC) Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta05.westchester.pa.mail.comcast.net with comcast id TQ7r1g0060mv7h055Q7wmi; Mon, 04 Apr 2011 12:07:56 +0000 Received: from [10.0.0.79] ([71.199.122.142]) by omta11.westchester.pa.mail.comcast.net with comcast id TQ7v1g02B34Sj4f3XQ7vRb; Mon, 04 Apr 2011 12:07:56 +0000 Message-ID: <4D99B4A2.8090502@comcast.net> Date: Mon, 04 Apr 2011 08:08:02 -0400 From: Steve Polyack User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: Frederique Rijsdijk References: <20110401141655.GA5350@deta.isafeelin.org> <4D95E62A.5000109@comcast.net> <4D987B1B.4000608@isafeelin.org> In-Reply-To: <4D987B1B.4000608@isafeelin.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Network stack unstable after arp flapping 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: Mon, 04 Apr 2011 12:07:56 -0000 On 4/3/2011 9:50 AM, Frederique Rijsdijk wrote: > Steve, > > On 01-04-11 16:50, Steve Polyack wrote: >> On 04/01/11 10:16, Frederique Rijsdijk wrote: > [ .. ] >>> Mar 31 18:36:12 srv01 kernel: arp: x.x.x.1 moved from >>> 00:00:0c:9f:f0:3d to 00:00:0c:07:ac:3d on bge0 > [ .. ] >>> The result of that, is that loads of FreeBSD machines (6.x, 7.x and >>> 8.x) developed serious network issues, mainly being no or slow traffic > [ .. ] >>> Any ideas anyone? >> We experienced a similar issue here, but IIRC only on our 8.x systems >> (we don't have any 7.x). Disabling flowtable cleared everything up >> immediately. You can try that and see if it helps. > AFAIK this feature was introduced in 8.x? Btw you are here referring to > UDP, we had issues with TCP. It could still be related, perhaps I'll get > around emulating the situation and see if I can reproduce it. > > Sorry, I tried to clarify that in the last piece of my post - the title on the PR is misleading and should be corrected. We found out quickly after submitting it that all types of traffic (UDP, TCP, ICMP, etc.) are independently affected.