Project

General

Profile

Actions
Copy link

Feature #2472

closed

Option to tie OpenVPN client instance to CARP status

Added by Rudy Attias over 13 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
OpenVPN
Target version:
-
Start date:
06/04/2012
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

Currently OpenVPN clients on backup CARP status hosts will still send out packets on that CARP IP, breaking that OpenVPN instance. It's currently worked around with devd scripts but done manually. Should have a checkbox at some point to tie client instances to the CARP status, or if it can be worked around at the OS level by forbidding sending packets sourced from a CARP IP with backup status, that would be best as it would eliminate any kind of problem along these lines.

Actions
Copy link

Also available in: Atom PDF