IP Alias // HA Cluster // Failover not working

[henrik_meyer]

Hi,

I have 2 pfSense version 2.3.2 in a simple HA/Cluster setup.

LAN:
pfSense-01: 192.168.1.2/24 // Primary
pfSense-02: 192.168.1.3/24 // Secondary
LAN-CARP: 192.168.1.1/24

I have added VIP "IP Alias" 100.64.1.1/32 to interface "localhost"on the primary, and that has replicated to the secondary.

With both pfSense-01 and pfSense-02 running:
From a PC Client I can ping 100.64.1.1
With a packet capture, I can see that pfSense-01 is replying.

With pfsense-01 shutdown and pfSense-02 running:
From a PC client I can no longer ping 100.64.1.1
With a packet capture, I can see the echo-request on pfSense-02 but it is not replying.

With pfsense-01 running and pfSense-02 shutdown:
From a PC Client I can ping 100.64.1.1
With a packet capture, I can see that pfSense-01 is replying.

In all three (3) tests LAN-CARP 192.168.1.1 is replying just fine.

Have I run into a bug regarding IP Alias on localhost and failover?

Thanks in advance

regards
Henrik Meyer, Denmark

[henrik_meyer]

New discovery

When it does not work on pfSense-02, that should answer the request, but is not doing so.
pfSense-02 is actually forwarding the packet to pfSense-01 - who is offline..

What the f***

Is "IP Alias" on localhost interface not suppose to failover?

[viragomann]

@henrik_meyer:

I have added VIP "IP Alias" 100.64.1.1/32 to interface "localhost"on the primary, and that has replicated to the secondary.

Why to localhost??? What's your intention?

[jimp]

They should failover fine, assuming your routing and other aspects of the config are OK.

What exactly do you mean by "pfSense-02 is actually forwarding the packet to pfSense-01"?

[Nrador007]

Failover Groups I can not work like this allows me to answer.