Bug #3744: CARP IPs stuck in INIT on 2.2 - pfSense - pfSense bugtracker

Actions

Copy link

Bug #3744

closed

CARP IPs stuck in INIT on 2.2

Added by Chris Buechler almost 10 years ago. Updated over 8 years ago.

Status:

Rejected

Priority:

Normal

Assignee:

Category:

High Availability

Target version:

Start date:

07/06/2014

Due date:

% Done:

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

2.2

Affected Architecture:

Description

On at least 32 bit.

lan_vip10: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
    inet 10.0.4.1 netmask 0xffffff00 vhid 10 
    nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
    carp: INIT vhid 10 advbase 2003398497 advskew 1
    carp: INIT vhid 0 advbase 0 advskew 0
opt1_vip11: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
    inet 10.0.5.1 netmask 0xffffff00 vhid 10 
    nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
    carp: INIT vhid 11 advbase 1870099809 advskew 1
    carp: INIT vhid 0 advbase 0 advskew 0
opt2_vip12: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
    inet 10.0.6.1 netmask 0xffffff00 vhid 9 
    nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
    carp: INIT vhid 12 advbase 1768909409 advskew 1
    carp: INIT vhid 0 advbase 0 advskew 0
wan_vip13: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
    inet 1.22.3.4 netmask 0xfffffff8 vhid 9 
    nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
    carp: INIT vhid 13 advbase 1768911713 advskew 1
    carp: INIT vhid 0 advbase 0 advskew 0
wan_vip14: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
    inet 1.22.3.5 netmask 0xfffffff8 vhid 6 
    nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
    carp: INIT vhid 14 advbase 1869177203 advskew 1
    carp: INIT vhid 0 advbase 0 advskew 0

No reason they shouldn't be in master status. That's from the primary system (backup looks identical). It does reply to ARP with the CARP MAC and more or less works minus failover.