Project

General

Profile

Actions

Bug #13344

open

Vlan loses parent interface when changing LAGG mtu to jumbo frames

Added by Matthew Whittaker-Williams over 1 year ago. Updated 4 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
LAGG Interfaces
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
22.01
Affected Architecture:

Description

Hi,

Psense+ version: 22.01

When I try to add jumbo frames to lagg interface ( 9000 ) - main
When I change the main interface enabled with no ip address the vlans configured under the lagg instantly lose their parent device.

lagg1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
description: LAGG1

ifconfig lagg1.115|grep vlan
groups: vlan
vlan: 0 vlanpcp: 0 parent interface: <none>

How am I suppose to enable jumbo frames on a aggregated link without losing vlan device links?
Also how to keep it persistent from the gui without doing hacks during bootup.


Files

lagg1-mtu-9000.png (278 KB) lagg1-mtu-9000.png Matthew Whittaker-Williams, 07/07/2022 08:47 AM
Actions #1

Updated by Alhusein Zawi over 1 year ago

it appears with 22.05 too.

to workaround :

re-save the Lagg interface Interfaces>LAGGs

after resaving:
lagg0.100: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
options=3<RXCSUM,TXCSUM>

ifconfig lagg0.100|grep vlan
groups: vlan
vlan: 100 vlanpcp: 0 parent interface: lagg0

22.05-RELEASE (amd64)
built on Wed Jun 22 18:56:13 UTC 2022
FreeBSD 12.3-STABLE

Actions #2

Updated by Jordan G 10 months ago

Matthew Whittaker-Williams wrote:

When I try to add jumbo frames to lagg interface ( 9000 ) - main
When I change the main interface enabled with no ip address the vlans configured under the lagg instantly lose their parent device.

Same behavior in 22.05, saving the (parent) interface with with IPv4/6 set to none and MTU 9000 kills connectivity on any VLANs on the LAGG. Reverting config and reboot/reroot restores connectivity. Config corrected, saving/applying interfaces and resetting states did not restore connectivity to sub-interfaces.

Actions #3

Updated by Jordan G 4 months ago

Actions

Also available in: Atom PDF