Project

General

Profile

Actions

Bug #9154

closed

Editing a VLAN parent interface causes all VLANs to be reconfigured, which can lead to problems

Added by Jim Pingle almost 3 years ago. Updated 10 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Interfaces
Target version:
Start date:
11/27/2018
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.4_1
Affected Architecture:

Description

See #9115 for details/logs. After fixing #9115, editing other VLAN interfaces works well, but editing the VLAN parent interface is still a problem as it hits every VLAN child and reconfigures it after. This can be necessary in certain cases, such as when changing MTU or other interface attribute, but it is very disruptive.

Also causes problems with PPPoE interfaces failing to (re)connect ( #9148 ) and IPv6 tracked interface addresses not being reapplied to the interfaces ( #9136 )

Actions #1

Updated by Jim Pingle over 2 years ago

  • Target version changed from 48 to 2.5.0
Actions #3

Updated by Renato Botelho about 1 year ago

  • Status changed from New to Feedback

PR has been merged. Thanks!

Actions #5

Updated by Renato Botelho about 1 year ago

Viktor Gurov wrote:

extra improvement:
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/13

Merged. Thanks!

Actions #6

Updated by Viktor Gurov 10 months ago

  • Status changed from Feedback to Resolved

works as expected on 2.5.0.a.20201209.0250 -
changes MTU of child VLAN interfaces without restarting
and keeping the manually configured child VLAN MTU

Actions

Also available in: Atom PDF