Project

General

Profile

Actions

Bug #12926

closed

Changing LAGG type on CARP interfaces makes VIPs go to an "init" State

Added by Kris Phillips about 2 years ago. Updated 3 months ago.

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

0%

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

Description

When changing a LAGG from any mode to another mode while it has child interfaces that are something like VLANs and CARP VIPs on them will cause CARP to go to an init status and never recover.

If you re-save the interface or reboot the firewall, they will go back to MASTER or BACKUP (depending on if it's primary or secondary). This can be worked around by failing over manually before making these changes and rebooting the firewall you're working on to avoid disruption, but this seems like a bug that should not present itself.

Bug was present in 2.6 of CE and 22.01 of pfSense Plus.


Files

first_error_after_changing_LAGG_type.png (214 KB) first_error_after_changing_LAGG_type.png Azamat Khakimyanov, 12/15/2022 02:16 AM
after_pressing_Reset_CARP_Demotion_Status.png (268 KB) after_pressing_Reset_CARP_Demotion_Status.png Azamat Khakimyanov, 12/15/2022 02:20 AM
after_about_10_minutes.png (240 KB) after_about_10_minutes.png Azamat Khakimyanov, 12/15/2022 02:23 AM
gateway_timeout.png (30.4 KB) gateway_timeout.png Azamat Khakimyanov, 12/15/2022 02:33 AM

Related issues

Is duplicate of Bug #9453: Reconfiguring a parent LAGG interface breaks its VLANsFeedbackMarcos M04/04/2019

Actions
Actions

Also available in: Atom PDF