Date: Sat, 15 Apr 2023 08:47:59 +0000
From: bugzilla-noreply@freebsd.org
To: bugs@FreeBSD.org
Subject: [Bug 260260] igb(4) I35{0,4} parrent <--> vlan jumbo frame mtu mismatch
Message-ID: <bug-260260-227-pPgyZggxFl@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-260260-227@https.bugs.freebsd.org/bugzilla/>
References: <bug-260260-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260260 --- Comment #7 from Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> --- No idea. Perhaps I am wrong. Now I recall that transitioned to stable/13 on affected machines relatively late, and the bug was reported here even later= . I wonder if lagg(4) has anything to do with it, since in the report of bug 268490, using lagg(4) has also been noted. I am utilising lagg on all affec= ted setups, think I can check if it's lagg dependent this weekend. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260260-227-pPgyZggxFl>