Project

General

Profile

Actions

Feature #2834

closed

carp+pfsync: add ability to prefer one node as master

Added by Alexander Swen about 11 years ago. Updated about 9 years ago.

Status:
Needs Patch
Priority:
Normal
Assignee:
-
Category:
CARP
Target version:
-
Start date:
02/22/2013
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

This request is done because we have the situation of a lot (3x /27) ip-addresses with most of them guarded by carp. As we have three blocks available on two (geographicly separated) datacenters we want to split the masters across those two dc's to have some kind of loadbalancing.
Without pfsync this can be easily achieved by just configuring the skew a bit higher on the side that we want to keep standby.

While using pfsync though, currently we can only add a carp address to the pfsync master and then that address will be synced to the pfsync-slave and that machine will be slave for that carp address. That is done by pfsync by increasing the chosen Skew with 100 when it goes through the sync.
If we want to configure the pfsync slave machine master for some of the carp addresses we need to disable the virtual addresses sync and then set the skew manually on both pfsense machines. While this is a working solution it would be very nice to have an option in the carp config (I would suggest a checkbox near the base/skew setting) which tells the pfsync config whether he should be master or slave. Alternatively a checkbox could be made that says "ignore/override pfsync" so that you can just set a lower skew on the box prefer to be master.


Files

skew.patch (4.7 KB) skew.patch Robert Middleswarth, 01/24/2015 07:59 PM
Actions #1

Updated by Robert Middleswarth about 10 years ago

I just came to request the same thing. Although I was thinking of a simple check box that said subtrack instead of add 100 during sync. I would think that would be a simple change without having a major impact.

Thanks
Robert

Actions #2

Updated by Chris Buechler over 9 years ago

  • Status changed from New to Needs Patch
Actions #3

Updated by Robert Middleswarth about 9 years ago

Attached is a simple fix based on the initial request of giving people the option to disable the syncing of the skew value.

Actions #4

Updated by Robert Middleswarth about 9 years ago

https://github.com/pfsense/pfsense/pull/1449

My patch was rejected. Looking to see what will be accepted.

Actions

Also available in: Atom PDF