From owner-freebsd-net@freebsd.org  Thu Jun 23 13:41:14 2016
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 2B515AC532E
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Thu, 23 Jun 2016 13:41:14 +0000 (UTC)
 (envelope-from kpielorz_lst@tdx.co.uk)
Received: from smtp.krpservers.com (smtp.krpservers.com [62.13.128.145])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.krpservers.com", Issuer "RapidSSL SHA256 CA - G3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id C49EE2E96;
 Thu, 23 Jun 2016 13:41:13 +0000 (UTC)
 (envelope-from kpielorz_lst@tdx.co.uk)
Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213] (may be
 forged)) (authenticated bits=0)
 by smtp.krpservers.com (8.15.2/8.15.2) with ESMTPSA id u5NDfAj8067079
 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Thu, 23 Jun 2016 14:41:11 +0100 (BST)
 (envelope-from kpielorz_lst@tdx.co.uk)
Date: Thu, 23 Jun 2016 14:41:02 +0100
From: Karl Pielorz <kpielorz_lst@tdx.co.uk>
To: Matthew Seaman <matthew@FreeBSD.org>, freebsd-net@freebsd.org
cc: Michael Gmelin <freebsd@grem.de>
Subject: Re: Problem with VLAN config and traffic after 10.1-R -> 10.3-R-p5
 Upgrade?
Message-ID: <87C4B070AC631E5175831B3A@[10.12.30.106]>
In-Reply-To: <e219551b-b5fe-8fba-f705-492634b7ecf1@freebsd.org>
References: <2ED5D9FEB55641BF734C14F3@[10.12.30.106]>
 <2033B3FC769B74294656A089@[10.12.30.106]>
 <e219551b-b5fe-8fba-f705-492634b7ecf1@freebsd.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.22
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: Thu, 23 Jun 2016 13:41:14 -0000


Ok...

--On 23 June 2016 13:32 +0100 Matthew Seaman <matthew@FreeBSD.org> wrote:

> I use a similar config with vlans over lagg.  While I haven't seen
> exactly your problem, I did see one instance of the vlan interface
> coming up with an all-zero MAC address (out of about 10 systems upgraded
> to 10.3-RELEASE so far).  See PR207701 -- my workaround was to
> explicitly set a MAC address for the vlan i/f.

Having just spent twenty minutes staring at MAC's on the machine - it *does 
appear* we are also seeing the same as PR207701.

The machine has two lagg interfaces on it - I checked the wrong one 
initially (em based) - hence twenty minutes of head scratching and 
oh-so-long reboots (on HP kit) after I glimpsed one of them was indeed a 
MAC of 00:00:00:00:00:00 (which is on the bge based lagg vlans).

I'll go read up on the PR, add myself to it, and implement the workaround.

Sorry for the noise...

Regards,

-Karl