Project

General

Profile

Actions
Copy link

Bug #13218

closed

GIF-based interface MTU is assigned to parent interface on boot when parent interface is a LAGG

Added by Graeme Bragg almost 3 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
Interfaces
Target version:
2.7.1
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
23.09
Release Notes:
Default
Affected Version:
2.6.0
Affected Architecture:

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

806.diff (2.87 KB) 806.diff Viktor Gurov, 05/27/2022 02:59 AM
Actions
Copy link
 #1

Updated by Viktor Gurov almost 3 years ago

  • Assignee set to Viktor Gurov
Actions
Copy link
 #2

Updated by Jim Pingle almost 3 years ago

  • Status changed from New to Pull Request Review
  • Target version set to 2.7.0
  • Plus Target Version set to 22.09
Actions
Copy link
 #3

Updated by Graeme Bragg almost 3 years ago

Thanks for looking at this so quickly. Please let me know if you need/want me to test anything.

Actions
Copy link
 #4

Updated by Viktor Gurov almost 3 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

Actions
Copy link
 #5

Updated by Graeme Bragg almost 3 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.

Actions
Copy link
 #6

Updated by Jim Pingle almost 3 years ago

  • Plus Target Version changed from 22.09 to 22.11
Actions
Copy link
 #7

Updated by Jim Pingle over 2 years ago

  • Plus Target Version changed from 22.11 to 23.01
Actions
Copy link
 #8

Updated by Jim Pingle over 2 years ago

  • Assignee deleted (Viktor Gurov)
Actions
Copy link
 #9

Updated by Jim Pingle over 2 years ago

  • Plus Target Version changed from 23.01 to 23.05
Actions
Copy link
 #10

Updated by Jim Pingle almost 2 years ago

  • Plus Target Version changed from 23.05 to 23.09
Actions
Copy link
 #11

Updated by Jim Pingle almost 2 years ago

  • Target version changed from 2.7.0 to CE-Next
Actions
Copy link
 #12

Updated by Jim Pingle over 1 year 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.

Actions
Copy link
 #13

Updated by Jim Pingle over 1 year ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #14

Updated by Danilo Zrenjanin over 1 year 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

Actions
Copy link
 #15

Updated by Danilo Zrenjanin over 1 year ago

  • Status changed from Feedback to Resolved

The patch fixes it.

I am marking this ticket resovled.

Actions
Copy link
 #16

Updated by Jim Pingle over 1 year ago

  • Target version changed from 2.8.0 to 2.7.1
Actions
Copy link

Also available in: Atom PDF