Bug #3910: Cannot set advskew back to 0 - pfSense - pfSense bugtracker

Custom queries

2.4.5-p1 - Resolved/Closed
2.5.0 - Resolved/Closed
2.5.1 - Resolved/Closed
2.5.2 - Resolved/Closed
2.6.0 - Resolved/Closed
2.7.0 - Resolved/Closed
2.7.1 - All Open Issues
2.7.1 - Resolved/Closed
2.7.2 - Resolved/Closed
2.8.0 - All Open Bugs
2.8.0 - All Open Features
2.8.0 - All Open Issues
2.8.0 - All Open Regressions
2.8.0 - Feedback
2.8.0 - Needs Attention
2.8.0 - New/Confirmed
2.8.0 - Pull Requests
2.8.0 - Regressions affecting 2.7.0
2.8.0 - Resolved/Closed
21.02.2/2.5.1 - Resolved/Closed
21.05 Plus - All Closed Issues
21.05.1 Plus Target - All Closed Issues
21.05.1 Target - All Closed Issues
22.01 Plus - All Closed Issues
22.01 Target - All Closed Issues
22.05 Plus - All Closed Issues
22.05 Target - All Closed Issues
23.01 Plus - All Closed Issues
23.01 Target - All Closed Issues
23.05 Plus - All Closed Issues
23.05 Target - All Closed Issues
23.05.1 Plus - All Closed Issues
23.05.1 Target - All Closed Issues
23.09 Plus - All Closed Issues
23.09 Target - All Closed Issues
23.09.1 Plus - All Closed Issues
23.09.1 Target - All Closed Issues
24.03 Plus - All Closed Issues
24.03 Target - All Closed Issues
24.11 Plus - All Closed Issues
24.11 Plus - All Open Issues
24.11 Plus - Feedback Issues
24.11 Plus - Needs Attention/Work
24.11 Plus - New/Confirmed/In Progress Issues
24.11 Target - All Closed Issues
24.11 Target - All Open Issues
25.01 Plus - All Closed Issues
25.01 Plus - All Open Issues
25.01 Plus - Feedback Issues
25.01 Plus - Needs Attention/Work
25.01 Plus - New/Confirmed/In Progress Issues
25.01 Plus - Pull Request Review
25.01 Plus - Waiting on Merge
25.01 Target - All Closed Issues
25.01 Target - All Open Issues
All Open Issues assigned to Me
All Open Pull Requests
Any Target - All Open Regressions
Any Target - Feedback Issues
CE-Next - All Closed Issues (Move to specific target)
CE-Next - All Open Issues
CE-Next - Feedback (Likely needs target changed)
New Issues by Category - Future Target
New Issues by Category - No Target
New Issues by Category - No Target+Future
No Target - All Open Issues (Base Only)
No Target - New Issues (Base Only)
No Target - New Issues (Base and Packages)
Release Notes - Plus Target Version (DO NOT EDIT)
Release Notes - Target Version (DO NOT EDIT)

Actions

Copy link

Bug #3910

closed

Cannot set advskew back to 0

Added by Chris Buechler about 10 years ago. Updated almost 10 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Renato Botelho

Category:

Operating System

Target version:

2.2

Start date:

10/02/2014

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

2.2

Affected Architecture:

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.

History
Notes
Property changes
Associated revisions

Actions

Copy link

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 ?

Actions

Copy link

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.

Actions

Copy link

Updated by Jim Pingle almost 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.

Actions

Copy link