From owner-freebsd-net@FreeBSD.ORG Sun Apr 3 14:06:19 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 348CC1065674 for ; Sun, 3 Apr 2011 14:06:19 +0000 (UTC) (envelope-from frederique@isafeelin.org) Received: from progress.isafeelin.org (progress.isafeelin.org [80.69.81.6]) by mx1.freebsd.org (Postfix) with ESMTP id EE5CA8FC18 for ; Sun, 3 Apr 2011 14:06:18 +0000 (UTC) Received: from progress.isafeelin.org (localhost [127.0.0.1]) by progress.isafeelin.org (Postfix) with ESMTP id 722BE131198 for ; Sun, 3 Apr 2011 15:50:21 +0200 (CEST) Received: from [192.168.1.15] (s5375723c.adsl.wanadoo.nl [83.117.114.60]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by progress.isafeelin.org (Postfix) with ESMTPSA id 3E2A3131194 for ; Sun, 3 Apr 2011 15:50:21 +0200 (CEST) Message-ID: <4D987B1B.4000608@isafeelin.org> Date: Sun, 03 Apr 2011 15:50:19 +0200 From: Frederique Rijsdijk 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: freebsd-net@freebsd.org References: <20110401141655.GA5350@deta.isafeelin.org> <4D95E62A.5000109@comcast.net> In-Reply-To: <4D95E62A.5000109@comcast.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP 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: Sun, 03 Apr 2011 14:06:19 -0000 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. -- Frederique