From owner-freebsd-net@FreeBSD.ORG Mon Oct 17 17:50:11 2011 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E059106566C for ; Mon, 17 Oct 2011 17:50:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1D3C88FC0C for ; Mon, 17 Oct 2011 17:50:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9HHoAjv074845 for ; Mon, 17 Oct 2011 17:50:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9HHoAoX074844; Mon, 17 Oct 2011 17:50:10 GMT (envelope-from gnats) Date: Mon, 17 Oct 2011 17:50:10 GMT Message-Id: <201110171750.p9HHoAoX074844@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Gleb Smirnoff Cc: Subject: Re: kern/155604: [flowtable] Flowtable excessively caches dest MAC addresses for outgoing traffic X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Gleb Smirnoff List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2011 17:50:11 -0000 The following reply was made to PR kern/155604; it has been noted by GNATS. From: Gleb Smirnoff To: Steve Polyack Cc: bug-followup@FreeBSD.org Subject: Re: kern/155604: [flowtable] Flowtable excessively caches dest MAC addresses for outgoing traffic Date: Mon, 17 Oct 2011 21:45:56 +0400 On Mon, Oct 17, 2011 at 12:04:35PM -0400, Steve Polyack wrote: S> > looks like this bug is fixed in 8.2 and later versions of FreeBSD. S> > Can I close the PR? S> > S> IMHO, the fix is merely a workaround (disabling FLOWTABLE by default in S> the kernel configuration). If a user turns flowtable on, they will S> still encounter the same problem as I described. S> S> We don't have a reason to turn the flowtable feature back on, so it S> doesn't really affect us either way. I'll leave it up to you as to S> whether you want to close it or have someone take a deeper look. You misunderstood me. I meant that the problem is no longer present with flowtable turned on. I have just tried to reproduce your problem on 8.2 and on head, and failed. I've found some reports in my private emails that claim that problem is only present only in 8.0 and 8.1. However, I haven't find the actual fix in commitlogs. -- Totus tuus, Glebius.