Project

General

Profile

Actions

Bug #2995

closed

Unsetting the pfsync synchronize IP doesn't properly set it back to directed multicast

Added by Per von Zweigbergk over 8 years ago. Updated over 8 years ago.

Status:
Rejected
Priority:
Normal
Category:
CARP
Target version:
-
Start date:
05/16/2013
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0.x
Affected Architecture:

Description

Expected: Leaving the "pfsync Synchronize Peer IP" box empty should set up pfsync to use directed multicast.

Actual: If clearing the "pfsync Synchronize Peer IP" setting after it had been set already, it will still use the old value until a reboot.

Workaround 1: Manually enter 224.0.0.240 into the "pfsync Synchronize Peer IP" to enable directed multicast.
Workaround 2: Execute the command "ifconfig pfsync0 -syncpeer".
Workaround 3: Reboot and let the startup scripts configure it correctly.

Affected versions: I have only tested this on 2.0.3.

Patch:

--- /etc/inc/interfaces.inc.orig 2013-05-16 13:47:13.000000000 0200
++ /etc/inc/interfaces.inc 2013-05-16 13:48:02.000000000 0200
@ -1666,7 +1666,7 @
if (is_ipaddr($pfsyncpeerip))
mwexec("/sbin/ifconfig pfsync0 syncdev {$carp_sync_int} syncpeer {$pfsyncpeerip} up", false);
else
- mwexec("/sbin/ifconfig pfsync0 syncdev {$carp_sync_int} up", false);
mwexec("/sbin/ifconfig pfsync0 syncdev {$carp_sync_int} -syncpeer up", false);

sleep(1);

Files

pfsync-syncpeer-patch.txt (654 Bytes) pfsync-syncpeer-patch.txt Per von Zweigbergk, 05/16/2013 06:47 AM
Actions

Also available in: Atom PDF