Bug #963: CARP Virtual IPs bind to actual interface, not interface description - pfSense - pfSense bugtracker

Actions

Copy link

Bug #963

closed

CARP Virtual IPs bind to actual interface, not interface description

Added by Tom Pepper over 14 years ago. Updated over 14 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

CARP

Target version:

Start date:

10/20/2010

Due date:

% Done:

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

2.0

Affected Architecture:

Description

I have the following setup on Oct 2 snapshot:

Firewall A:
WAN (wan) -> em1 -> 2xx.xxx.xxx.156/27
LAN (lan) -> em0 -> 10.0.22.254/24
OPT1 (opt1) -> em2 -> 10.239.10.1/24
MGMT (opt3) -> em4 -> 10.0.99.254/22

Firewall B:
WAN (wan) -> em1 -> 2xx.xxx.xxx.157/27
LAN (lan) -> em0 -> 10.0.22.253/24
OPT1 (opt1) -> em2 -> 10.239.10.4/24
MGMT (opt2) -> em3 -> 10.0.99.253/22

CARP VIPs supply IPs for the following:
LAN default router (10.0.22.1)
WAN default router (2xx.xxx.xxx.158)
MGMT default router (10.0.96.1)

The problem is that Carp Sync breaks the VIP for MGMT on Firewall B because the config binds it to the actual interface name (opt3) as opposed to the interface description (MGMT).

Is this by design?

Thanks,
-t