Date: Mon, 4 Apr 2011 12:09:05 +0200 From: "K. Macy" <kmacy@freebsd.org> To: Frederique Rijsdijk <frederique@isafeelin.org> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: Network stack unstable after arp flapping Message-ID: <BANLkTi=dvHagdukgUgp2SbcB37vRXvFbTA@mail.gmail.com> In-Reply-To: <20110404095333.GA3421@deta.isafeelin.org> References: <20110401141655.GA5350@deta.isafeelin.org> <4D95E62A.5000109@comcast.net> <4D987B1B.4000608@isafeelin.org> <BANLkTin0RsisoLp-x9WinjvJuf3pmSz13w@mail.gmail.com> <20110404095333.GA3421@deta.isafeelin.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 =3D 0;
if ((V_flowtable_enable =3D=3D 0) || (V_flowtable_ready =3D=3D 0))
return (0);
Ciao
On Mon, Apr 4, 2011 at 11:53 AM, Frederique Rijsdijk
<frederique@isafeelin.org> 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.
>>
>>
>> =A0-Kip
>> On Sunday, April 3, 2011, Frederique Rijsdijk <frederique@isafeelin.org>=
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 traff=
ic
>> > [ .. ]
>> >>> Any ideas anyone?
>> >> We experienced a similar issue here, but IIRC only on our 8.x systems
>> >> (we don't have any 7.x). =A0Disabling flowtable cleared everything up
>> >> immediately. =A0You can try that and see if it helps.
>> >
>> > AFAIK this feature was introduced in 8.x? Btw you are here referring t=
o
>> > UDP, we had issues with TCP. It could still be related, perhaps I'll g=
et
>> > around emulating the situation and see if I can reproduce it.
>> >
>> >
>> > -- Frederique
>> >
>> >
>> > _______________________________________________
>> > freebsd-net@freebsd.org=A0mailing 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"
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTi=dvHagdukgUgp2SbcB37vRXvFbTA>