From owner-freebsd-net@FreeBSD.ORG Tue Oct 23 01:20:01 2012 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 97C8F5C7 for ; Tue, 23 Oct 2012 01:20:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.FreeBSD.org [8.8.178.135]) by mx1.freebsd.org (Postfix) with ESMTP id 807F38FC0A for ; Tue, 23 Oct 2012 01:20:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q9N1K1fW021966 for ; Tue, 23 Oct 2012 01:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q9N1K1vL021965; Tue, 23 Oct 2012 01:20:01 GMT (envelope-from gnats) Date: Tue, 23 Oct 2012 01:20:01 GMT Message-Id: <201210230120.q9N1K1vL021965@freefall.freebsd.org> To: freebsd-net@FreeBSD.org Cc: From: Ryan Steinmetz Subject: Re: kern/156226: Lagg failover does not announce the failover to switch X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Ryan Steinmetz List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2012 01:20:01 -0000 The following reply was made to PR kern/156226; it has been noted by GNATS. From: Ryan Steinmetz To: Per von Zweigbergk Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/156226: Lagg failover does not announce the failover to switch Date: Mon, 22 Oct 2012 21:12:40 -0400 This isn't a solution, but is a workaround that I've been using for a bit: http://people.freebsd.org/~zi/ping You can drop the file in /usr/local/etc/rc.d and then add ping_enable="YES" to /etc/rc.conf Basically, it sends an icmp echo request to your default gateway every 5 seconds by default, which forces the switch to update its FIB. This means that after a maximum of 5 seconds after lagg completes an interface failover, you should regain network connectivity. -r