Project

General

Profile

Actions
Copy link

Bug #2775

closed

OpenVPN Server binds on CARP IP on slave instead on master

Added by Reiner Keller almost 12 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
OpenVPN
Target version:
2.1
Start date:
01/23/2013
Due date:
% Done:

0%

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

Description

Hello,

I am running

2.1-BETA1 (amd64) 
     built on Mon Jan 14 11:26:04 EST 2013 
     FreeBSD 8.3-RELEASE-p5

and think that the fix of Bug #2686 is wrongly applied for the server part because my slave firewall start openvpn server instead of my master firewall.
The client part is running fine on master.

Actions
Copy link
 #1

Updated by Reiner Keller almost 12 years ago

forgotten... the firewall slave binds on the right CARP IP:

wan_vip201: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet x.x.x.122 netmask 0xfffffff8
carp: BACKUP vhid 201 advbase 1 advskew 100

and master has:

wan_vip201: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet x.x.x.122 netmask 0xfffffff8
carp: MASTER vhid 201 advbase 1 advskew 0

Actions
Copy link
 #2

Updated by Jim Pingle almost 12 years ago

OpenVPN Servers are not bound by the same CARP restrictions as OpenVPN clients. It's normal for OpenVPN servers to be running on both.

Actions
Copy link
 #3

Updated by Jim Pingle almost 12 years ago

Tested this on a cluster I had handy and servers bound to a CARP VIP run on both. I'm not seeing a problem.

We used to stop servers as well as clients but that changed in 260f267e way back in July.

Actions
Copy link
 #4

Updated by Jim Pingle almost 12 years ago

  • Status changed from New to Closed
Actions
Copy link

Also available in: Atom PDF