Date: Fri, 6 Nov 2020 14:32:41 -0800 From: Eric Joyner <erj@freebsd.org> To: mike tancsa <mike@sentex.net> Cc: lev@freebsd.org, current <current@freebsd.org> Subject: Re: Link flap when adding / removing a vlan (was Re: r360902 breaks VLAN interface on if_em (82579LM)) Message-ID: <CA%2Bb0zg_PVBnaOBK=Mg9923ciV0gUTZHdhiQ-oVxjJWU_dN8ANQ@mail.gmail.com> In-Reply-To: <a7d4eb82-29d1-34f7-85df-c6f7ffb83032@sentex.net> 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> <711876429.20200601003941@serebryakov.spb.ru> <d67b7835-f7de-e230-08df-9d35b75b5b91@sentex.net> <a7d4eb82-29d1-34f7-85df-c6f7ffb83032@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Could you reply to that issue with what you've found? Though, as far as I can recall, igb(4) devices are not supposed to do the iflib reset talked about in the bug, so I wouldn't expect to see a link flap on those. - Eric On Fri, Nov 6, 2020 at 12:48 PM mike tancsa <mike@sentex.net> wrote: > On 11/6/2020 2:17 PM, mike tancsa wrote: > > On 5/31/2020 5:39 PM, Lev Serebryakov wrote: > >> 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 :( > > > Looks like this is captured in > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240818 > > > > Hi All, > > > > Just came across this thread as I am running into this behaviour on > > RELENG_12. Adding a new vlan causes all vlans on the parent interface > > to flap. Not the greatest thing as it bounces a LOT of traffic > > potentially, flaps routing etc. Is there a way around this ? > > > > This is on r367411 releng12 > > > > igb0@pci0:2:0:0: class=0x020000 card=0x153315d9 chip=0x15338086 > > rev=0x03 hdr=0x00 > > vendor = 'Intel Corporation' > > device = 'I210 Gigabit Network Connection' > > class = network > > subclass = ethernet > > > > eg. just something simple like > > > > ifconfig vlan16 create 10.1.2.3/29 vlandev igb1 vlan 16 > > > > # dmesg | tail -8 > > igb1: link state changed to DOWN > > vlan16: link state changed to DOWN > > vlan2049: link state changed to DOWN > > vlan15: link state changed to DOWN > > igb1: link state changed to UP > > vlan16: link state changed to UP > > vlan2049: link state changed to UP > > vlan15: link state changed to UP > > > > > > ---Mike > > > > > > > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2Bb0zg_PVBnaOBK=Mg9923ciV0gUTZHdhiQ-oVxjJWU_dN8ANQ>