Date: Mon, 04 Apr 2011 08:08:02 -0400 From: Steve Polyack <korvus@comcast.net> To: Frederique Rijsdijk <frederique@isafeelin.org> Cc: freebsd-net@freebsd.org Subject: Re: Network stack unstable after arp flapping Message-ID: <4D99B4A2.8090502@comcast.net> In-Reply-To: <4D987B1B.4000608@isafeelin.org> References: <20110401141655.GA5350@deta.isafeelin.org> <4D95E62A.5000109@comcast.net> <4D987B1B.4000608@isafeelin.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D99B4A2.8090502>