From owner-freebsd-current@freebsd.org  Mon Aug 31 17:47:25 2015
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 1955B9C7077
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon, 31 Aug 2015 17:47:25 +0000 (UTC)
 (envelope-from deischen@freebsd.org)
Received: from mail.netplex.net (mail.netplex.net [204.213.176.9])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.netplex.net", Issuer "RapidSSL SHA256 CA - G3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id D0339190C
 for <freebsd-current@freebsd.org>; Mon, 31 Aug 2015 17:47:24 +0000 (UTC)
 (envelope-from deischen@freebsd.org)
Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11])
 by mail.netplex.net (8.15.1/8.15.1/NETPLEX) with ESMTP id t7VHlMeN006337;
 Mon, 31 Aug 2015 13:47:22 -0400
X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net)
X-Greylist: Message whitelisted by DRAC access database, not delayed by
 milter-greylist-4.4.3 (mail.netplex.net [204.213.176.9]);
 Mon, 31 Aug 2015 13:47:22 -0400 (EDT)
Date: Mon, 31 Aug 2015 13:47:22 -0400 (EDT)
From: Daniel Eischen <deischen@freebsd.org>
X-X-Sender: eischen@sea.ntplx.net
Reply-To: Daniel Eischen <deischen@freebsd.org>
To: Adrian Chadd <adrian.chadd@gmail.com>
cc: "Ranjan1018 ." <214748mv@gmail.com>,
 FreeBSD CURRENT <freebsd-current@freebsd.org>
Subject: Re: Upgrading to r297291 LAGG(4) stops working.
In-Reply-To: <CAJ-Vmo=A84QAOUK1qWt7Qg2Pm-DdC44z-ebnTK_=uMJJVcw+Pg@mail.gmail.com>
Message-ID: <Pine.GSO.4.64.1508311340410.5273@sea.ntplx.net>
References: <CACyC=qZm74oBjtsUPu4C2hB_C24eeRXUasNqSxzioAzNyjVGdA@mail.gmail.com>
 <CAJ-Vmo=_wd65Kgo0xqLOKX59Y_U1+C0M01AJpcfWYWNAxT0zrQ@mail.gmail.com>
 <CACyC=qYquXvthHqdifp_vMFKe_Ju05em2BMLx_ktvchQNQ=Vww@mail.gmail.com>
 <Pine.GSO.4.64.1508310810560.4192@sea.ntplx.net>
 <CAJ-Vmo=A84QAOUK1qWt7Qg2Pm-DdC44z-ebnTK_=uMJJVcw+Pg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Aug 2015 17:47:25 -0000

On Mon, 31 Aug 2015, Adrian Chadd wrote:

> Hi,
>
> Because it works by magic, not works by intent. There's no guarantee
> that a STA device will let you re-program its MAC address.

As long as an attempt to set the MAC address returns an error
that is meaningful (ENOTSUP?), that is fine.  I still believe
you should be able to tell the clone device to do this, and
have it call down through (all the way) to the actual device
driver.  Having to jump through hoops trying to configure
lagg on a cloned device is ugly.  But at least it is possible,
so I'm extremely happy for that :-)

> It also confuses people when they believe you can setup things like
> bridged VMs and they don't work across wifi but do across ethernet.

Ok, thanks for the info.

-- 
DE