From owner-freebsd-net@freebsd.org  Mon Oct  5 13:23:49 2015
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F0FE99A98C
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Mon,  5 Oct 2015 13:23:49 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6B8D1F96
 for <freebsd-net@FreeBSD.org>; Mon,  5 Oct 2015 13:23:49 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t95DNndC063196
 for <freebsd-net@FreeBSD.org>; Mon, 5 Oct 2015 13:23:49 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 156226] [lagg]: failover does not announce the failover to switch
Date: Mon, 05 Oct 2015 13:23:49 +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: unspecified
X-Bugzilla-Keywords: feature, needs-qa, patch
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: pvz@itassistans.se
X-Bugzilla-Status: Open
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: mfc-stable9? mfc-stable10?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-156226-2472-0ogKbdUGIr@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-156226-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-156226-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.20
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Oct 2015 13:23:49 -0000

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

--- Comment #16 from pvz@itassistans.se ---
In this case it's not even a case of a protocol though, it's rather just some
functionality to prod even the dumbest stack of switches that are smart enough
to know about MAC learning to do the right thing.

I think though that this could well be made into a really simple user-space
daemon with a few hundred lines of code and no configuration file, though it
would be "cleaner" (for a regular end user) for it to just be built into lagg.

The code would be something like: every now and then, iterate over all laggs.
If the master has changed, send out an ethernet frame on the interface, and on
any VLAN interfaces on top of the lagg. Would that be something that could be
included in the base system as a feature rather than just adding the
functionality to lagg?

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