From owner-freebsd-net@FreeBSD.ORG Mon Apr 4 10:22:51 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 90FD1106566B for ; Mon, 4 Apr 2011 10:22:51 +0000 (UTC) (envelope-from free@isafeelin.org) Received: from progress.isafeelin.org (progress.isafeelin.org [80.69.81.6]) by mx1.freebsd.org (Postfix) with ESMTP id 2424A8FC19 for ; Mon, 4 Apr 2011 10:22:50 +0000 (UTC) Received: from progress.isafeelin.org (localhost [127.0.0.1]) by progress.isafeelin.org (Postfix) with ESMTP id 37440131197; Mon, 4 Apr 2011 12:22:50 +0200 (CEST) Received: from s5375723c.adsl.wanadoo.nl (s5375723c.adsl.wanadoo.nl [83.117.114.60]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by progress.isafeelin.org (Postfix) with ESMTPS id F196F13118B; Mon, 4 Apr 2011 12:22:49 +0200 (CEST) Received: by s5375723c.adsl.wanadoo.nl (Postfix, from userid 1002) id 924772843A; Mon, 4 Apr 2011 12:22:49 +0200 (CEST) Date: Mon, 4 Apr 2011 12:22:49 +0200 From: Frederique Rijsdijk To: "K. Macy" Message-ID: <20110404102249.GB3421@deta.isafeelin.org> References: <20110401141655.GA5350@deta.isafeelin.org> <4D95E62A.5000109@comcast.net> <4D987B1B.4000608@isafeelin.org> <20110404095333.GA3421@deta.isafeelin.org> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV using ClamSMTP 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 10:22:51 -0000 Hi Kip, Thanks. Any idea btw why this would also effect hosts that run 6.x and 7.x RELEASE versions? These do not have the flowtable sysctl. -- Frederique On Mon, Apr 04, 2011 at 12:09:05PM +0200, K. Macy wrote: > Correct. Set it to zero and the flowtable will be bypassed. > > flowtable.c: > static uint32_t > ipv6_flow_lookup_hash_internal( > struct sockaddr_in6 *ssin6, struct sockaddr_in6 *dsin6, > uint32_t *key, uint16_t flags) > { > uint16_t sport, dport; > uint8_t proto; > int offset = 0; > > if ((V_flowtable_enable == 0) || (V_flowtable_ready == 0)) > return (0); > > > Ciao > > On Mon, Apr 4, 2011 at 11:53 AM, Frederique Rijsdijk > wrote: > > Kip, > > > > Which sysctl are we talking about exactly? Just to be sure.. > > > > net.inet.flowtable.enable ? > > > > > > -- Frederique > > > > > > > > On Sun, Apr 03, 2011 at 08:11:33PM +0200, K. Macy wrote: > >> I don't think it was properly tested when it was enabled for IPv6. > >> Given that I have been absentee it really should not be in the default > >> kernel or at least the sysctl should be off. Sorry for the > >> inconvenience. Additionally, you don't need to rebuild you can just > >> disable the sysctl. > >> > >> > >>  -Kip > >> On Sunday, April 3, 2011, 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. > >> > > >> > > >> > -- Frederique > >> > > >> > > >> > _______________________________________________ > >> > freebsd-net@freebsd.org mailing list > >> > http://lists.freebsd.org/mailman/listinfo/freebsd-net > >> > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > >> > > >> _______________________________________________ > >> freebsd-net@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-net > >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > >