https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260
--- Comment #10 from Marek Zarychta ---
The workaround mentioned in comment 8 can be applied only on I354, I350
requires permanent bumping of MTU for the parent by 4 bytes, so the issue still
looks the same as it looked 1.5 years ago.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260
--- Comment #9 from Marek Zarychta ---
It's also worth mentioning, that large UDP datagrams are received fine without
any workaround, though the frames are shorter, at least in the case of testing
with iperf3.
UDP:
15:00:45.609781 ac:1f:6b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260
--- Comment #8 from Marek Zarychta ---
The bug seems to be not related to lagg(4). Moreover, I found out that it can
be also worked around by only temporarily oversizing MTU by one byte.
So to reproduce the problem issue this sequence of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260
--- Comment #7 from Marek Zarychta ---
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,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260
Kevin Bowling changed:
What|Removed |Added
CC||kbowl...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260
Marek Zarychta changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260
--- Comment #5 from Zhenlei Huang ---
Since the VLAN(4) works as expected when disabling VLAN hardware offloading
features, it should be a bug in the driver of igb(4).
--
You are receiving this mail because:
You are the assignee for the b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260
--- Comment #4 from Marek Zarychta ---
I was told to update the PR with some em vs igb details, so TL;DR:
1. em(4) works like before with the same MTU 9000 on parent em(4), lagg(4) and
vlan(4) with the options: VLAN_MTU,VLAN_HWTAGGING,VLAN_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260
--- Comment #3 from Marek Zarychta ---
(In reply to Zhenlei Huang from comment #2)
1. Indeed, bringing up intrefaces this way:
ifconfig_igb0="mtu 9000 -vlanmtu -vlanhwtag -vlanhwfilter -vlanhwtso
-vlanhwcsum up"
ifconfig_igb1="mtu 9000 -vla
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260
--- Comment #2 from Zhenlei Huang ---
So it is weird.
If VLANMTU is disabled on parent interface, MTU of VLAN interface will be
limited off by 4 automatically. The MTU of vlans should be 8996 in your case.
Try the following steps:
1. Dis
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260
--- Comment #1 from Marek Zarychta ---
Last time tested on 13.0-STABLE stable/13-n248421-3b936a8c889 where the issue
persists. It is also worth mentioning that turning off vlanmtu vlanhwtag
vlanhwfilter vlanhwtso vlanhwcsum on parents doesn
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260
Marek Zarychta changed:
What|Removed |Added
CC||n...@freebsd.org
Keywor
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260260
Bug ID: 260260
Summary: igb(4) I35{0,4} parrent <--> vlan jumbo frame mtu
mismatch
Product: Base System
Version: 13.0-STABLE
Hardware: amd64
OS: Any
13 matches
Mail list logo
