From owner-freebsd-net@freebsd.org Thu Jun 23 12:32:30 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 63341A7A060 for ; Thu, 23 Jun 2016 12:32:30 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E965824BA for ; Thu, 23 Jun 2016 12:32:29 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from ox-dell39.ox.adestra.com (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 7432D24AF for ; Thu, 23 Jun 2016 12:32:24 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/7432D24AF; dkim=none; dkim-atps=neutral Subject: Re: Problem with VLAN config and traffic after 10.1-R -> 10.3-R-p5 Upgrade? To: freebsd-net@freebsd.org References: <2ED5D9FEB55641BF734C14F3@[10.12.30.106]> <2033B3FC769B74294656A089@[10.12.30.106]> From: Matthew Seaman Message-ID: Date: Thu, 23 Jun 2016 13:32:16 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <2033B3FC769B74294656A089@[10.12.30.106]> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="bHMoBvKKKshEQJIhVxvQQQaNHEV0I5i02" X-Virus-Scanned: clamav-milter 0.99.2 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_00,RDNS_NONE, SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk 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 12:32:30 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --bHMoBvKKKshEQJIhVxvQQQaNHEV0I5i02 Content-Type: multipart/mixed; boundary="NSjAGd75kt2mS6xGBGgCoQLiA5FeVL52X" From: Matthew Seaman To: freebsd-net@freebsd.org Message-ID: Subject: Re: Problem with VLAN config and traffic after 10.1-R -> 10.3-R-p5 Upgrade? References: <2ED5D9FEB55641BF734C14F3@[10.12.30.106]> <2033B3FC769B74294656A089@[10.12.30.106]> In-Reply-To: <2033B3FC769B74294656A089@[10.12.30.106]> --NSjAGd75kt2mS6xGBGgCoQLiA5FeVL52X Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 06/23/16 13:14, Karl Pielorz wrote: >=20 > --On 23 June 2016 11:53 +0100 Karl Pielorz wro= te: >=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 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. 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. Cheers, Matthew --NSjAGd75kt2mS6xGBGgCoQLiA5FeVL52X-- --bHMoBvKKKshEQJIhVxvQQQaNHEV0I5i02 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJXa9bQAAoJEABRPxDgqeTnVqsP+wWrcTctSxQ5xVMQsCTln664 tvHGgtQxnVGpN5WrxbrKCJQ49XaGoLx6v8HyKXQHE6My94huvW193M8VDYaYVVQx e51cr5i6+Z7wgkJVibBOi1/lOYxfz1lv9Nkt4+pe+laa31sntq7snVhlY7g8VNef LF98oKaYFiYrwzhmc75l68IqdMmzSfj03g3Pk967kza+6ChwmXgNfWNpWa5mJobV kJIl8xyQd9PqrHufaKvkD3jxHdP+wEcZnbQEMxXUYq6r1zd5neNn450Jg6jSGy9c 3x89E8XONtP2WXp9zM0VkZDU2E7NlT6Kjn9NWOnhQDEJ0V6vmxY9P4B0mTy/XmSz 2+dVefRY1K/GBXSsc9696ARmEbqrqyu+38GVLnMoHGFSz2iteZdxifqE0zUezMgg LJOwYR7TkP9SDG7xIGabFxWE27TxGOm7NJkvtQEstLg5NHITKgnNgJcVuZGot3d6 /wXNmQAoYZKH48zBYtP/qWzuo86DkTYF4VMkdF/ASL0BolwpXQTH4kgyoyxxYZZ6 xVtJBlY1Cb05Wtw3Ruh4h6AhGL7SYAX4advnIMQ6dXT8XKtOybZ1d6wV8hP3Az6q GNIyTZYvjmgbw++pjBaOAbqdbdG4esNuRBBG4u3t44fBzsXLxftHjgW1wkhyiil8 yVF0+EobYm3OCuepI1vI =3F4A -----END PGP SIGNATURE----- --bHMoBvKKKshEQJIhVxvQQQaNHEV0I5i02--