Bug #11091
open
Interfaces set as disabled in the configuration have an UP status in the operating system at boot
0%
Description
If you disable interface on interfaces.php page it's disabled
there is no UP in ifconfig output and `get_interface_info()` returns 'status' = 'down', 'enable' = 'false'
but after system reboot interface status is UP in ifconfig output and `get_interface_info()` returns 'status' = 'up', 'enable' = 'false', which is incorrect
it seems `interfaces_configure()` doesn't disable interfaces on boot
Updated by Viktor Gurov over 1 year ago
Updated by Jim Pingle over 1 year ago
- Status changed from New to Pull Request Review
- Target version set to CE-Next
Updated by Renato Botelho over 1 year ago
- Status changed from Pull Request Review to Feedback
- Assignee set to Viktor Gurov
PR has been merged. Thanks!
Updated by Viktor Gurov over 1 year ago
- % Done changed from 0 to 100
Applied in changeset 9115501d6ab5197d9caf499e90779c020d711dca.
Updated by Jim Pingle about 1 year ago
- Status changed from Feedback to Waiting on Merge
- Target version changed from CE-Next to 2.5.1
Updated by Renato Botelho about 1 year ago
- Status changed from Waiting on Merge to Feedback
Cherry-picked to RELENG_2_5_1
Updated by Alhusein Zawi about 1 year ago
After reboot the interface is not UP in ipconfig
[2.5.1-RC][admin@pfSense.home.arpa]/root: ifconfig em2
em2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=81009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,VLAN_HW
2.5.1-RC (amd64)
built on Thu Mar 11 09:11:02 EST 2021
Updated by Jim Pingle about 1 year ago
- Subject changed from Disabled interface is UP on boot to Interfaces set as disabled in the configuration have an UP status in the operating system at boot
Updating subject for release notes.
Updated by Jim Pingle about 1 year ago
- Status changed from Resolved to In Progress
I think this may need some refinement as it could interfere with other things. If you have an interface assigned but disabled and use that interface as a parent for other things, the children will be affected.
For example if lagg0 is assigned and enabled, and you have VLAN children on lagg0, this takes out the VLAN children.
I think we should back this out of 2.5.1/21.02.2 and work on it more in master for the next release.
Updated by Jim Pingle about 1 year ago
- Target version changed from 2.5.1 to 2.6.0
I backed the change out of RELENG_2_5_1, moving target forward.
Updated by Steve Wheeler about 1 year ago
Confirmed; this breaks sub-interfaces on anything that is assigned but disabled by removing the parent entirely.
Updated by Viktor Gurov about 1 year ago
Steve Wheeler wrote:
Confirmed; this breaks sub-interfaces on anything that is assigned but disabled by removing the parent entirely.
fix:
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/250
Updated by Jim Pingle about 1 year ago
We can bring in that fix for the next release, I backed out the original change from plus-RELENG_21_05 to make sure it doesn't impact the pending release to be safe.
Updated by Jim Pingle about 1 year ago
- Status changed from In Progress to New
- % Done changed from 50 to 0
Per discussion on the PR, all the changes have been reverted.
Can try alternate approaches for the next release.
Updated by Jim Pingle 9 months ago
- Plus Target Version changed from 21.09 to 22.01
Moving ahead, too close to release to make another attempt at this and have enough time to validate the change in behavior.
Updated by Jim Pingle 7 months ago
- Target version changed from 2.6.0 to CE-Next
- Plus Target Version changed from 22.01 to 22.05
Updated by Jim Pingle 12 days ago
- Plus Target Version changed from 22.05 to 22.09