From owner-freebsd-net@freebsd.org Thu Jun 23 13:04:26 2016 Return-Path: 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 034D9A7A883 for ; Thu, 23 Jun 2016 13:04:26 +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 A23B0174A; Thu, 23 Jun 2016 13:04:25 +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 u5ND4LQx064681 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Jun 2016 14:04:23 +0100 (BST) (envelope-from kpielorz_lst@tdx.co.uk) Date: Thu, 23 Jun 2016 14:04:13 +0100 From: Karl Pielorz To: Matthew Seaman , freebsd-net@freebsd.org Subject: Re: Problem with VLAN config and traffic after 10.1-R -> 10.3-R-p5 Upgrade? Message-ID: In-Reply-To: References: <2ED5D9FEB55641BF734C14F3@[10.12.30.106]> <2033B3FC769B74294656A089@[10.12.30.106]> 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jun 2016 13:04:26 -0000 --On 23 June 2016 13:32 +0100 Matthew Seaman 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. Hi, We seem to always have a MAC address on the lagg - so I don't think we've hit that issue. > We're configuring the vlan interfaces slightly differently so that they > end up with a name like 'vlan123' rather than 'lagg0.123' -- if that > difference is significant then it maybe gives you an alternate > workaround to running your interfaces promiscuously. Any chance you can send us a snippet of how they're setup in '/etc/rc.conf' if it's different. When we originally set this up way-back-when we had a lot of fun with the various ways & syntax of getting it setup, just settling for the way we do 'because it works' - not ideal I guess, so I'd be interested to see if there's another way of spec'ing the config in rc.conf Cheers, -Karl