Bug #644: Changing CARP VHID results in multiple interfaces with the same IP - pfSense - pfSense bugtracker

Actions

Copy link

Bug #644

closed

Changing CARP VHID results in multiple interfaces with the same IP

Added by Jim Pingle over 14 years ago. Updated over 14 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

CARP

Target version:

2.0

Start date:

06/10/2010

Due date:

% Done:

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

2.0

Affected Architecture:

Description

If you change the VHID of a CARP VIP, the old interface is not deactivated/destroyed, or reused.

I know at one point that was dangerous due to panic risk, but could the interface be renamed or reused instead of destroyed if that is no longer possible? Or at least strip the IP address off the old VIP interface?

As expected, after a reboot only the correct VHID interface is present.

Actions

Copy link

Updated by Jim Pingle over 14 years ago

This may be related to #643 in some way, upon further testing. I can only reproduce it if I change the VHID on the master, let it sync to the slave, and then edit/save the VIP on the slave, which results in this:

vip70: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
    inet 192.168.7.1 netmask 0xffffff00 
    carp: MASTER vhid 70 advbase 1 advskew 100
vip72: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
    inet 192.168.7.1 netmask 0xffffff00 
    carp: BACKUP vhid 72 advbase 1 advskew 100

Actions

Copy link

Updated by Jim Pingle over 14 years ago

Some more info on how to reproduce this. On a pair of systems already setup for config sync, do the following:

On the Master:

Go to Firewall > Virtual IPs
Create a new CARP VIP, give it a VHID, password, etc.
Save/apply

On the Backup:

Go to Status > CARP (Failover)
* There is a line for the new IP, but no interface listed
Look at ifconfig -a
* There is no VIP interface for this new CARP IP
Go to Firewall > Virtual IPs
Edit the new CARP IP
Change nothing, just Save/Apply
Look at Status > CARP and ifconfig -a
* VIP interface is present with a proper name and working as expected.

On the Master again:

Go to Firewall > Virtual IPs
Edit the CARP VIP created above, change its VHID.
Save/apply

On the Backup again:

Go to Firewall > Virtual IPs
Edit the new CARP IP
Change nothing, just Save/Apply
Look at Status > CARP
VIP interface is present with a proper name
Look at ifconfig -a
* There are multiple VIP interfaces as shown above, with different VHIDs but the same IP address assigned.