Bug #6677
closed
CARP VIPs are configured on disabled interfaces at boot time
100%
Description
When a CARP VIP is configured for a disabled interface, it is still configured by pfSense during the boot process even though the main interface address is not present. This leads to the interface being active when it should not be.
CARP VIPs for disabled interfaces should be skipped.
Updated by Jim Pingle over 8 years ago
- Status changed from New to Feedback
An interface can show as "up" as long as it has a link. A VLAN will exist at the OS level if a tag is defined. The difference between enabled and disabled would be whether or not it has an IP address configured and if it's being put to use, more or less. Can you provide more detail about what, specifically, it is that you're seeing?
Updated by Patrik Andersin over 8 years ago
Did little more testing.
It seems that if there is an carp address assigned to interface the interface will come up after reboot even if it is not enabled.
With carp address disable does not survive reboot.
1. staring condition: lagg1_vlan9 with carp address
2. disable interface -> lagg1_vlan9 is deleted from system (ifconfig: interface lagg9_vlan9 does not exist)
3. reboot -> interface setting on web gui shows interface not enabled. ifconfig shows interface up with ip addresses.
Without carp address things are fine.
1. starting condition: lagg_vlan9
2. disable interface -> lagg1_vlan9 is deleted from system (ifconfig: interface lagg9_vlan9 does not exist)
3. reboot -> interface settin on web bui shows interface not enabled. ifconfig show interface up with no ip addresses.
Updated by Jim Pingle over 8 years ago
- Subject changed from Non enabled interface active after boot (vlan on lagg) to CARP VIPs are configured on disabled interfaces at boot time
- Description updated (diff)
- Category set to CARP
- Status changed from Feedback to New
- Target version set to 2.3.2-p1
- Affected Version changed from 2.3.2 to 2.3.x
OK, that I can reproduce. I have adjusted the subject and description to be a more clear/accurate representation of the issue.
Updated by Jim Pingle about 8 years ago
- Target version changed from 2.3.2-p1 to 2.4.0
Updated by
Updated by Luiz Souza over 7 years ago
- Target version changed from 2.4.0 to 2.4.1
Updated by Jim Pingle about 7 years ago
- Target version changed from 2.4.1 to 2.4.2
Updated by Jim Pingle about 7 years ago
- Target version changed from 2.4.2 to 2.4.3
Updated by Luiz Souza almost 7 years ago
- Status changed from Assigned to Feedback
- % Done changed from 0 to 100
Fixed.
Please check with the next snapshot.
Updated by Luiz Souza almost 7 years ago
- Status changed from Feedback to Resolved