Date: Sat, 13 Sep 2014 21:16:22 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-185967-2472-dK5hxDDDe5>