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

Custom queries

2.8.1 - Resolved/Closed
2.9.0 - Resolved/Closed
26.03 Plus - All Closed Issues
26.03 Target - All Closed Issues
26.03.1 Plus - All Closed Issues
26.03.1 Target - All Closed Issues
26.07 Plus - All Closed Issues
26.07 Target - All Closed Issues
26.10 Plus - All Closed Issues
26.10 Plus - All Open Issues
26.10 Plus - Feedback Issues
26.10 Plus - Needs Attention/Work
26.10 Plus - New/Confirmed/In Progress Issues
26.10 Plus - Pull Request Review
26.10 Plus - Waiting on Merge
26.10 Target - All Closed Issues
26.10 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)
Plus-next Feedback/Closed (likely needs target changed)
Release Notes - CE Target Version (DO NOT EDIT)
Release Notes - Plus Target Version (DO NOT EDIT)
Release Notes - Target Version (DO NOT EDIT)

Actions

Copy link

Bug #3910

closed

CB RB

Cannot set advskew back to 0

Bug #3910: Cannot set advskew back to 0

Added by Chris Buechler almost 12 years ago. Updated over 11 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

PB Updated by Pi Ba almost 12 years ago Actions
Copy link
#1

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 ?

CB Updated by Chris Buechler almost 12 years ago Actions
Copy link
#2

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.

JP Updated by Jim Pingle over 11 years ago Actions
Copy link
#3

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.

RB Updated by Renato Botelho over 11 years ago Actions
Copy link
#4

Status changed from Confirmed to Assigned
Assignee set to Renato Botelho
Target version set to 2.2

After the fix is pushed, revert commit:eea2ad5d

RB Updated by Renato Botelho over 11 years ago Actions
Copy link
#5

Status changed from Assigned to Feedback
% Done changed from 0 to 100

Should be ok on next snapshots

CB Updated by Chris Buechler over 11 years ago Actions
Copy link
#6

Status changed from Feedback to Resolved

works

Actions

Copy link

Also available in: Atom

Project

General

Profile

pfSense

Custom queries

Bug #3910

Cannot set advskew back to 0

PB Updated by Pi Ba almost 12 years ago Actions
Copy link
#1

CB Updated by Chris Buechler almost 12 years ago Actions
Copy link
#2

JP Updated by Jim Pingle over 11 years ago Actions
Copy link
#3

RB Updated by Renato Botelho over 11 years ago Actions
Copy link
#4

RB Updated by Renato Botelho over 11 years ago Actions
Copy link
#5

CB Updated by Chris Buechler over 11 years ago Actions
Copy link
#6

Project

General

Profile

pfSense

Custom queries

Bug #3910

Cannot set advskew back to 0

PB Updated by Pi Ba almost 12 years ago ActionsCopy link #1

CB Updated by Chris Buechler almost 12 years ago ActionsCopy link #2

JP Updated by Jim Pingle over 11 years ago ActionsCopy link #3

RB Updated by Renato Botelho over 11 years ago ActionsCopy link #4

RB Updated by Renato Botelho over 11 years ago ActionsCopy link #5

CB Updated by Chris Buechler over 11 years ago ActionsCopy link #6

PB Updated by Pi Ba almost 12 years ago Actions
Copy link
#1

CB Updated by Chris Buechler almost 12 years ago Actions
Copy link
#2

JP Updated by Jim Pingle over 11 years ago Actions
Copy link
#3

RB Updated by Renato Botelho over 11 years ago Actions
Copy link
#4

RB Updated by Renato Botelho over 11 years ago Actions
Copy link
#5

CB Updated by Chris Buechler over 11 years ago Actions
Copy link
#6