Date: Sat, 15 Apr 2023 12:39:44 +0000
From: bugzilla-noreply@freebsd.org
To: net@FreeBSD.org
Subject: [Bug 260260] igb(4) I35{0,4} parrent <--> vlan jumbo frame mtu mismatch
Message-ID: <bug-260260-7501-qFAJl1cfCC@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-260260-7501@https.bugs.freebsd.org/bugzilla/>
References: <bug-260260-7501@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 #8 from Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> --- The bug seems to be not related to lagg(4). Moreover, I found out that it c= an be also worked around by only temporarily oversizing MTU by one byte.=20 So to reproduce the problem issue this sequence of commands: ifconfig igb3 mtu 9000 ifconfig vlan1500 create vlandev igb3 vlan 1500 ifconfig vlan1500 192.168.40.5/24 Now MTU for both igb3 and vlan1500 is set to 9000 but vlan1500 can only send large TCP segments. Receiving is broken. But the real mystery is that after the sequence:=20 ifconfig igb3 mtu 9001 ifconfig igb3 mtu 9000 ifconfig vlan1500 create vlandev igb3 vlan 1500 ifconfig vlan1500 192.168.40.5/24 Receiving large TCP segments for vlan1500 is working fine (MTU for both igb3 and vlan1500 is still set to the same value of 9000).=20 I tried to investigate how can it be possible that when sibling setups are compared one of them is able to work without oversizing MTU of the parent b= ut another one does not. Neither TSO nor LRO seems to be involved. Here's how the segment looks at receiving side after applying a temporary M= TU oversizing fix from the above: 14:27:36.269125 ac:1f:6b:02:aa:bb > ac:1f:6b:02:aa:cc, ethertype IPv4 (0x0800), length 9014: (tos 0x2,ECT(0), ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 9000) 192.168.40.3.25218 > 192.168.40.5.5201: Flags [.], cksum 0x1a28 (correc= t), seq 835179525:835188473, ack 1, win 70, options [nop,nop,TS val 2309578650 = ecr 1068877401], length 8948 --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260260-7501-qFAJl1cfCC>