Bug #13218
closedGIF-based interface MTU is assigned to parent interface on boot when parent interface is a LAGG
100%
Description
Minimal reproducible configuration:
round-robin LAGG pair assigned as the WAN interface with either an MTU of 1500 or no MTU set.
a GIF interface (he.net tunnel used for testing) assigned as OPT1 with an MTU of 1480 set.
System:
Intel i3 8100,
16GB RAM,
Chelsio T422-CR 2x10Gb/2x1Gb NIC,
2x Intel I210AT 1Gb NIC
(Also tested on an older i5 2500-based system with 4x Intel Pro/1000 PT NICs)
Issue:
In the stated configuration, the MTU assigned to OPT1 is applied to the WAN interface on each reboot according to Status > Interfaces and ifconfig.
This occurs with both Intel and Chelsio NICs. I have not tested with other brands.
This occurs whether the MTU of the parent interface is specifically set to 1500 or left at the default value.
Once the issue manifests, any MTU setting for the WAN interface is ignored.
Clearing the problem involves removing the MTU setting from the GIF interface before setting the WAN interface's MTU to a temporary value.
The WAN interface's MTU can then be returned to 1500 (or the default setting) and the MTU limit on the GIF interface restored.
The correct MTU remains on the WAN interface until the next reboot.
The problem does not occur when the NIC is set to a single, non-aggregated interface.
Files
Updated by Viktor Gurov about 2 years ago
- Assignee set to Viktor Gurov
Updated by Jim Pingle about 2 years ago
- Status changed from New to Pull Request Review
- Target version set to 2.7.0
- Plus Target Version set to 22.09
Updated by Graeme Bragg about 2 years ago
Thanks for looking at this so quickly. Please let me know if you need/want me to test anything.
Updated by Viktor Gurov about 2 years ago
Graeme Bragg wrote in #note-3:
Thanks for looking at this so quickly. Please let me know if you need/want me to test anything.
You can try to test the attached patch.
See https://docs.netgate.com/pfsense/en/latest/development/system-patches.html
Updated by Graeme Bragg about 2 years ago
I've applied it and it looks to do the job. I will keep an eye on it and throw in a couple of reboots over the weekend - I'll report back if I have any issues.
Updated by Jim Pingle about 2 years ago
- Plus Target Version changed from 22.09 to 22.11
Updated by Jim Pingle almost 2 years ago
- Plus Target Version changed from 22.11 to 23.01
Updated by Jim Pingle almost 2 years ago
- Plus Target Version changed from 23.01 to 23.05
Updated by Jim Pingle over 1 year ago
- Plus Target Version changed from 23.05 to 23.09
Updated by Jim Pingle about 1 year ago
- Target version changed from 2.7.0 to CE-Next
Updated by Jim Pingle 12 months ago
- Status changed from Pull Request Review to In Progress
- Assignee set to Jim Pingle
- Target version changed from CE-Next to 2.8.0
PR has conflicts (and some logic issues, and outdated code usage). I'm working on an updated version of the changes.
Updated by Jim Pingle 12 months ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
Applied in changeset 14beb636e4ca286c011398a30fd818f15c83eb7e.
Updated by Danilo Zrenjanin 12 months ago
I reproduced the issue on the following version:
23.05.1-RELEASE (amd64) built on Wed Jun 28 03:57:27 UTC 2023 FreeBSD 14.0-CURRENT
Updated by Danilo Zrenjanin 12 months ago
- Status changed from Feedback to Resolved
The patch fixes it.
I am marking this ticket resovled.