From owner-freebsd-net@FreeBSD.ORG  Sat Sep 13 21:16:22 2014
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id CDA0175C
 for <freebsd-net@FreeBSD.org>; Sat, 13 Sep 2014 21:16:22 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B3D9EADF
 for <freebsd-net@FreeBSD.org>; Sat, 13 Sep 2014 21:16:22 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8DLGMrl077742
 for <freebsd-net@FreeBSD.org>; Sat, 13 Sep 2014 21:16:22 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working
 in 10.0
Date: Sat, 13 Sep 2014 21:16:22 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: olivier@cochard.me
X-Bugzilla-Status: In Discussion
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-185967-2472-dK5hxDDDe5@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-185967-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-185967-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Sep 2014 21:16:22 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967

--- Comment #11 from olivier@cochard.me ---
(In reply to kvedulv from comment #10)
> Hi Oliver,
> 
> (In reply to olivier from comment #8)
> > The patch didn't solve Lagg regression between 9.2 and 10-stable (r267244).
> > 
> > My configuration only use one lagg member (the second will be added later):
> 
> _Maybe_ #179926 is your Bug and you could try the patch over there...
> (Although that problem seems to have existed at least in 9.1)

I believe it's not a regression in my case:
On FreeBSD 9.2, the lagg-lacp mode by not implementing a 'strict' mode was
equivalent to a 'static+optionnal LACP' mode.
The behavior of lagg-lacp on 9.2 seems:
- If no LACP detected, allow a minimum of 1 lagg member to transmit.
The behavior on 10 seems:
- If no LACP detected, don't allow any of the lagg member to transmit (even
with strict_mode disabled)
And in my case: I didn't have a LACP device in front of my FreeBSD.
Then I simply need to use a 'static' mode (like loadbalanced or roundrobin).

-- 
You are receiving this mail because:
You are the assignee for the bug.