From owner-freebsd-amd64@freebsd.org  Wed Jun 15 15:01:27 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@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 B361FA44E44
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Wed, 15 Jun 2016 15:01:27 +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 9FF7C16DF
 for <freebsd-amd64@FreeBSD.org>; Wed, 15 Jun 2016 15:01:27 +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 u5FF1Qtd023180
 for <freebsd-amd64@FreeBSD.org>; Wed, 15 Jun 2016 15:01:27 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 207701] vlan interface over failover lagg has
 empty/00:00:00:00:00:00 mac/ether address
Date: Wed, 15 Jun 2016 15:01:27 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.3-BETA2
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: matthew@FreeBSD.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: araujo@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-207701-6-a5Y4TafQDj@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-207701-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-207701-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 15 Jun 2016 15:43:28 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2016 15:01:27 -0000

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

Matthew Seaman <matthew@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |matthew@FreeBSD.org

--- Comment #8 from Matthew Seaman <matthew@FreeBSD.org> ---
Hi,

We're seeing exactly this on upgrading from 10.2-RELEASE to 10.3-RELEASE-p5=
 --
only one machine out of about 10 that have been upgraded.=20=20

Workaround is to set the ether address via rc.conf by adding:

```
ifconfig_vlan110=3D"ether 90:b1:1c:41:93:50 up"
```

Config settings:
```
ifconfig_bge0=3D"up"
ifconfig_bge1=3D"up"

ifconfig_lagg0=3D"laggproto lacp laggport bge0 laggport bge1 up"

cloned_interfaces=3D"lagg0 vlan110"
vlans_lagg0=3D"vlan110"
create_args_vlan110=3D"vlandev lagg0 vlan 110"
ifconfig_vlan110=3D"ether 90:b1:1c:41:93:50 up"
ipv4_addrs_vlan110=3D"10.2.1.9/24"
defaultrouter=3D"10.2.1.1"
```

Machine is a Dell R420 -- we're seeing the same effect with both the on-boa=
rd
bge(4) NICs and with an add-on igb(4) card.

This setup has been working flawlessly for us on numerous machines since ar=
ound
9.0-RELEASE

--=20
You are receiving this mail because:
You are on the CC list for the bug.=