Project

General

Profile

Actions
Copy link

Bug #4026

closed

Virtual IP on a PPPoE interface - OpenVPN fails

Added by Walt McDonald about 10 years ago. Updated about 10 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11/18/2014
Due date:
% Done:

0%

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

Description

WAN interface is PPPoE(em1)
Virtual IP (1.2.3.4) on WAN interface
OpenVPN server on the Virtual IP 1.2.3.4

openvpn44829: Exiting due to fatal error
Nov 19 01:57:00 openvpn44829: TCP/UDP: Socket bind failed on local address [AF_INET]1.2.3.4:1194: Can't assign requested address

OpenVPN works ok when it is a Virtual IP not on a PPPoE interface.

Workaround is instead of using Virtual IP - create a new Interface OPT1 (with an IP of 1.2.3.4) on same physical network port em1, choose this interface for OpenVPN server.

I don't know if this would effect other scenarios - using a Virtual IP on a PPPoE interface type.

Actions
Copy link
 #1

Updated by Chris Buechler about 10 years ago

  • Project changed from pfSense Packages to pfSense
  • Status changed from New to Rejected

VIP should be bound to localhost with PPPoE, not WAN.

Actions
Copy link

Also available in: Atom PDF