From owner-freebsd-questions@FreeBSD.ORG Tue Jul 31 22:15:13 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 89FCB106566B for ; Tue, 31 Jul 2012 22:15:13 +0000 (UTC) (envelope-from mailnull@mips.inka.de) Received: from mail-in-03.arcor-online.net (mail-in-03.arcor-online.net [151.189.21.43]) by mx1.freebsd.org (Postfix) with ESMTP id 36AC98FC1A for ; Tue, 31 Jul 2012 22:15:13 +0000 (UTC) Received: from mail-in-11-z2.arcor-online.net (mail-in-11-z2.arcor-online.net [151.189.8.28]) by mx.arcor.de (Postfix) with ESMTP id DFFDED82D4 for ; Tue, 31 Jul 2012 23:44:12 +0200 (CEST) Received: from mail-in-11.arcor-online.net (mail-in-11.arcor-online.net [151.189.21.51]) by mail-in-11-z2.arcor-online.net (Postfix) with ESMTP id DC83E31A011 for ; Tue, 31 Jul 2012 23:44:12 +0200 (CEST) Received: from lorvorc.mips.inka.de (dslb-092-075-215-144.pools.arcor-ip.net [92.75.215.144]) by mail-in-11.arcor-online.net (Postfix) with ESMTPS id BB81835A492 for ; Tue, 31 Jul 2012 23:44:12 +0200 (CEST) X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-11.arcor-online.net BB81835A492 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.14.5/8.14.3) with ESMTP id q6VLiC6q004490 for ; Tue, 31 Jul 2012 23:44:12 +0200 (CEST) (envelope-from mailnull@lorvorc.mips.inka.de) Received: (from mailnull@localhost) by lorvorc.mips.inka.de (8.14.5/8.14.5/Submit) id q6VLiC4e004489 for freebsd-questions@freebsd.org; Tue, 31 Jul 2012 23:44:12 +0200 (CEST) (envelope-from mailnull) From: naddy@mips.inka.de (Christian Weisgerber) Date: Tue, 31 Jul 2012 21:44:12 +0000 (UTC) Message-ID: References: <5017EE35.2040509@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-questions@freebsd.org Subject: Re: lagg(4) and LACP setup X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jul 2012 22:15:13 -0000 Tilman Keskinöz wrote: > FreeBSD -if0---------flaky link1 ----Switch----FreeBSD Router > | | > if1 --------------flaky link2 --- > > I think the best configuration would be to use lagg(4) with LACP to > catch the failing links. > > I have found several examples to do this with two completely seperate > links both computers using lagg interfaces, but in my setup the router > has only one interface. LACP manages physical links. In your setup above, you would configure LACP on the FreeBSD host (not the router) and on the switch. If the switch doesn't support it, you can't use LACP. > AFAI understood the Router needs to answer the LACP packets send by the > lagg interface. how do i activate this on a normal ethernet card? I think it's possible to create a lagg(4) interface on top of a single physical interface, but that's of no use here. You could use lagg(4) in _failover_ mode on the FreeBSD host. This (like LACP, actually) assumes that the availability of the link is correctly signaled by the interface link state. If by "flaky" you mean that packets are simply blackholed, none of this will work. -- Christian "naddy" Weisgerber naddy@mips.inka.de