Bug #3910
closed
Cannot set advskew back to 0
100%
Description
When leaving persistent CARP maintenance mode, the advskew is left at 254 on the running system, so it retains backup status when it shouldn't. advskew should be set back to its config-defined value after leaving persistent maintenance mode.
Updated by Pi Ba about 10 years ago
This seems to me to be a FreeBSD bug, setting advskew to 0 never works.. Setting it to 1 is possible though. Perhaps pfSense carp interfaces should use a minimum advskew value of 1 ?
Updated by Chris Buechler about 10 years ago
- Subject changed from advskew not set back to 0 after leaving persistent maintenance mode to Cannot set advskew back to 0
- Category changed from High Availability to Operating System
- Status changed from New to Confirmed
- Target version deleted (
2.2)
That is correct, we're running the commands correctly to set it back to 0. The source of the issue is FreeBSD 10.1 won't set it back to 0, though any other value works.
I committed a work around to resolve this issue for the time being.
FreeBSD bug opened:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194672
will leave this here to hopefully remove the workaround at some point once that upstream bug is fixed.
Updated by Jim Pingle about 10 years ago
There still seems to be an issue here. On a current snapshot when I try to leave maintenance mode the skew is stuck at 254 on the LAN side, but it may be related to having IP Alias VIPs using the CARP VIP as their parent.
We probably should automatically set the skew to 1 when the user has it set to 0. 0 is supposed to be for emergency use, we should probably prevent that from being selected directly in the GUI. carp(4) and ifconfig(8) list 0 as being special and default, and 1 is the lowest user-configurable value.
Updated by Renato Botelho almost 10 years ago
- Status changed from Confirmed to Assigned
- Assignee set to Renato Botelho
- Target version set to 2.2
After the fix is pushed, revert eea2ad5d
Updated by Renato Botelho almost 10 years ago
- Status changed from Assigned to Feedback
- % Done changed from 0 to 100
Should be ok on next snapshots