Date: Thu, 23 Jun 2016 14:30:15 +0200 From: Michael Gmelin <freebsd@grem.de> To: Karl Pielorz <kpielorz_lst@tdx.co.uk> Cc: freebsd-net@FreeBSD.org Subject: Re: Problem with VLAN config and traffic after 10.1-R -> 10.3-R-p5 Upgrade? Message-ID: <5DA0293A-B07A-4975-A347-3DE91C5A6116@grem.de> In-Reply-To: <2033B3FC769B74294656A089@[10.12.30.106]> References: <2ED5D9FEB55641BF734C14F3@[10.12.30.106]> <2033B3FC769B74294656A089@[10.12.30.106]>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 23 Jun 2016, at 14:14, Karl Pielorz <kpielorz_lst@tdx.co.uk> wrote: >=20 >=20 > --On 23 June 2016 11:53 +0100 Karl Pielorz <kpielorz_lst@tdx.co.uk> wrote:= >=20 >> This gets increasingly weird if I run tcpdump on the 10.3 box. The act of= >> running 'tcpdump -i lagg1.30 -n' actually fixes the problem: >=20 > As a follow up - running 'ifconfig lagg1 promisc' fixes the issue as well (= as you'd kind of expect if tcpdump does while it's running). >=20 > I don't know if that's a good idea / workaround for now? I don't think having an IP address on an interface that also has vlan interf= aces is a good idea. What kind of traffic are you expecting on lagg1? - Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5DA0293A-B07A-4975-A347-3DE91C5A6116>