Date: Thu, 23 Jun 2016 14:04:13 +0100 From: Karl Pielorz <kpielorz_lst@tdx.co.uk> To: Matthew Seaman <matthew@FreeBSD.org>, freebsd-net@freebsd.org Subject: Re: Problem with VLAN config and traffic after 10.1-R -> 10.3-R-p5 Upgrade? Message-ID: <C79C5854063C035F33429973@[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>
next in thread | previous in thread | raw e-mail | index | archive | help
--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. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C79C5854063C035F33429973>