Project

General

Profile

Actions

Regression #14026

closed

HA node with CARP VIP in backup state is unable to ping the active node using that CARP VIP address

Added by Christopher Cope over 1 year ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
CARP
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
24.11
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

This was brought up by a customer and I am able to reproduce it.

Master 10.41.1.252
Backup 10.40.1.253
CARP 10.40.1.254

10.40.1.253 is unable to ping 10.40.1.254 on 23.01, but is able to on a 22.05 install.

When pinging 10.40.1.253 > 10.40.1.254 and using packet capture it shows packets reaching 10.41.1.252 and replies making it back to 10.41.1.253, but ping never sees the response. There are no blocked entries in the firewall logs.


Related issues

Related to Feature #11369: add Enabling IPv6 Source Address Validation supportResolved02/04/2021

Actions
Has duplicate Bug #14798: can't ping VIP addresses from the secondary nodeDuplicate

Actions
Actions

Also available in: Atom PDF