Date: Mon, 1 Jun 2020 00:39:41 +0300 From: Lev Serebryakov <lev@FreeBSD.org> To: current@freebsd.org Subject: Re: r360902 breaks VLAN interface on if_em (82579LM) Message-ID: <711876429.20200601003941@serebryakov.spb.ru> In-Reply-To: <997c1389-5e18-b07e-d342-c787c841a4c4@gmail.com> References: <88004d48-4434-875a-5a36-0627b00c2f38@gmail.com> <1906251966.36777.1590562439792.JavaMail.open-xchange@opme11oxm03aub.bagnolet.francetelecom.fr> <997c1389-5e18-b07e-d342-c787c841a4c4@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Ian, Thursday, May 28, 2020, 2:45:48 AM, you wrote: > I noticed that my VLAN interfaces stopped working after a recent build. > tcpdump showed traffic leaving leaving and entering the interface but no > host on the network actually received any packets from this host. A > binary search led me to r360902 and indeed the following change fixed > the issue for me: Problem is, this change will return terrible situation when adding new VLAN will flap connection status. It all worked before iflib: hardware VLAN filtering worked, and adding/removing new VLAN didn't cause link to flap. Now, with iflib, looks like we can not have all good things at once :( -- Best regards, Lev mailto:lev@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?711876429.20200601003941>