[Bug 249050] if_qlxgb mtu not initialized bug causing wrong pkt 0x62 dump start

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050 Mark Johnston changed: What|Removed |Added Assignee|n...@freebsd.org |ma...@freebsd.org Sta

[Bug 249050] if_qlxgb mtu not initialized bug causing wrong pkt 0x62 dump start

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050 Mark Johnston changed: What|Removed |Added CC||p...@pogotopia.net --- Comment #4

[Bug 249050] if_qlxgb mtu not initialized bug causing wrong pkt 0x62 dump start

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050 --- Comment #3 from commit-h...@freebsd.org --- A commit references this bug: Author: markj Date: Tue Sep 1 20:13:51 UTC 2020 New revision: 365060 URL: https://svnweb.freebsd.org/changeset/base/365060 Log: qlxgb: Initialize if_mtu befor

[Bug 249050] if_qlxgb mtu not initialized bug causing wrong pkt 0x62 dump start

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050 --- Comment #2 from Christian Vallières --- The interface didn't respond when in bridge, but I realized that moving ifp->if_capabilities = IFCAP_LINKSTATE; didn't solve, forget that part. -- You are receiving this mail because: You are th

[Bug 249050] if_qlxgb mtu not initialized bug causing wrong pkt 0x62 dump start

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org Stat

[Bug 249050] if_qlxgb mtu not initialized bug causing wrong pkt 0x62 dump start

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050 Mark Linimon changed: What|Removed |Added Attachment #217690|0 |1 is patch|

[Bug 249050] if_qlxgb mtu not initialized bug causing wrong pkt 0x62 dump start

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org -- You are receiv