Project

General

Profile

Actions
Copy link

Bug #16322

closed

Gateway monitoring daemon can unexpectedly use a CARP VIP as the source IP address

Added by Christopher Cope 5 months ago. Updated 20 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Marcos M
Category:
Gateway Monitoring
Target version:
2.9.0
Start date:
Due date:
% Done:

100%

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

Description

find_interface_ip() in /etc/inc/interfaces.inc has a flush parameter, but that only seems to ignore the $interface_ip_arr_cache.

If the CARP VIP is in /var/db/{$interface}_ip when calling find_interface_ip() with flush the VIP will still be used.

I think it would make sense to add another parameter such as $ignore_cache_file to force the function to reload the current preferred address directly from the interface. This could then be set when calling the function as needed.

This issue was noticed as dpinger was monitoring on the CARP VIP instead of the interface address.

Actions
Copy link

Also available in: Atom PDF