Project

General

Profile

Actions

Bug #6607

closed

OpenVPN server won't start after reboot, when set to a Gateway Group specifing CARP VIPs

Added by r00 00m almost 9 years ago. Updated almost 9 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
OpenVPN
Target version:
-
Start date:
07/13/2016
Due date:
% Done:

0%

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

Description

No problem for OpenVPN clients.

When OpenVPN server is set to a simple CARP VIP, it will start after reboot.

When CARP failover occurs, the OpenVPN server won't start on the new master / old backup node neither (when set to a Gateway Group specifing CARP VIPs).

Actions #1

Updated by r00 00m almost 9 years ago

Affected version is 2.3.1-RELEASE-p1. I am using SG-4860 hardware.

Actions #2

Updated by Chris Buechler almost 9 years ago

  • Status changed from New to Not a Bug

subject isn't true. That was all fully verified in 2.3.1, and just checked again to verify on 2.3.1_5 and 2.3.2, and it works fine during boot and failover/fail back.

Guessing maybe you upgraded to 2.3.0, where a config upgrade bug would have caused issues with not setting the uniqid properly, in which case the config might need fixing (though that doesn't exactly match the description).

Please get in touch via support and we can help track down what's going on there. There could well be a bug of some sort there, but it's not as simple as described.

Actions #3

Updated by Steve Wheeler almost 9 years ago

See: VPA-15570

Actions

Also available in: Atom PDF