From owner-freebsd-net@freebsd.org Thu Jun 23 13:15:06 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 E5A9DA7AAC7 for ; Thu, 23 Jun 2016 13:15:06 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 55F1C218C for ; Thu, 23 Jun 2016 13:15:05 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 97380 invoked by uid 89); 23 Jun 2016 13:15:04 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@194.97.158.70) by mail.grem.de with ESMTPA; 23 Jun 2016 13:15:04 -0000 Date: Thu, 23 Jun 2016 15:15:03 +0200 From: Michael Gmelin To: Karl Pielorz Cc: 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: <20160623151503.1630324b@bsd64.grem.de> In-Reply-To: References: <2ED5D9FEB55641BF734C14F3@[10.12.30.106]> <2033B3FC769B74294656A089@[10.12.30.106]> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.2) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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:15:07 -0000 On Thu, 23 Jun 2016 14:04:13 +0100 Karl Pielorz wrote: > --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 > Could you post the output of ifconfig after boot and while/after running tcpdump? -- Michael Gmelin