From owner-freebsd-questions@FreeBSD.ORG  Fri Nov 15 14:49:52 2013
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 91816BEC
 for <questions@freebsd.org>; Fri, 15 Nov 2013 14:49:52 +0000 (UTC)
Received: from mail.lariat.net (mail.lariat.net [66.62.230.51])
 by mx1.freebsd.org (Postfix) with ESMTP id 37AF92DA4
 for <questions@freebsd.org>; Fri, 15 Nov 2013 14:49:51 +0000 (UTC)
Received: from Toshi.lariat.net (IDENT:ppp1000.lariat.net@localhost
 [127.0.0.1]) by mail.lariat.net (8.9.3/8.9.3) with ESMTP id HAA04566
 for <questions@freebsd.org>; Fri, 15 Nov 2013 07:49:44 -0700 (MST)
Message-Id: <201311151449.HAA04566@mail.lariat.net>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 15 Nov 2013 07:49:38 -0700
To: questions@freebsd.org
From: Brett Glass <brett@lariat.net>
Subject: lagg(4) question
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Nov 2013 14:49:52 -0000

I'm interested in using lagg(4) to provide failover from a main 
wireless link to a backup link. Unfortunately, one of the common 
failure modes, when a link fails, is for the Ethernet port on the 
radio to stay up but not pass any traffic. Does lagg(4) test the 
link, by actually trying to send packets, to determine if the link 
has failed? Or does it rely upon the Ethernet link losing "carrier"?

--Brett Glass