From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 16 20:50:11 2011 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A9021065673 for ; Wed, 16 Mar 2011 20: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 272668FC20 for ; Wed, 16 Mar 2011 20: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 p2GKoAx8045535 for ; Wed, 16 Mar 2011 20: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 p2GKoAcb045534; Wed, 16 Mar 2011 20:50:10 GMT (envelope-from gnats) Date: Wed, 16 Mar 2011 20:50:10 GMT Message-Id: <201103162050.p2GKoAcb045534@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Steve Polyack X-Mailman-Approved-At: Wed, 16 Mar 2011 21:21:11 +0000 Cc: Subject: Re: amd64/155604: Flowtable excessively caches dest MAC addresses for outgoing UDP traffic X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Steve Polyack List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Mar 2011 20:50:11 -0000 The following reply was made to PR amd64/155604; it has been noted by GNATS. From: Steve Polyack To: bug-followup@FreeBSD.org, spolyack@collaborativefusion.com Cc: Subject: Re: amd64/155604: Flowtable excessively caches dest MAC addresses for outgoing UDP traffic Date: Wed, 16 Mar 2011 16:32:54 -0400 I've just confirmed that this can also happen with TCP. As long as something on the freebsd system is constantly trying to form a connection to the same destination address & port, the old MAC address of the router is used as the destination MAC address for new connection attempts. Since the connection attempts continue to match the old flows, they are never expired. Disabling the flowtable again causes things to immediately return to normal and send traffic to the correct destination MAC address.