Project

General

Profile

Actions
Copy link

Bug #1771

closed

OpenVPN and PPPoE Wan Interface

Added by Oliver Loch almost 14 years ago. Updated almost 14 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
OpenVPN
Target version:
-
Start date:
08/15/2011
Due date:
% Done:

0%

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

Description

Hi,

if a pppoe interface is used as wan interface and OpenVPN is attached to the wan interface on port 443/tcp (which happens quite often), then the WebUI for configration can't come up after a reboot.

The moment the machine boots, the PPPoE interface doesn't have an ip address which leads to an empty string in the OpenVPN configration file ("local " instead of "local 1.2.3.4") and the daemon binds to all interfaces.

The then started WebUI can't use the socket 443/tcp on the LAN interface and you can't access the firewall anymore.

Only workaround is to kill the OpenVPN daemons in the shell and to restart the WebUI. In the WebUI you can then start the OpenVPN daemons again.

KR,

Grimeton

Actions
Copy link
 #1

Updated by Jim Pingle almost 14 years ago

  • Status changed from New to Rejected
  • Target version deleted (2.0)

The GUI always binds to 443 on all interfaces. The fact that it works at all in that configuration is surprising. As always, if you want to use 443 for an external service, either move the GUI to another port, or use a port forward to redirect it. (That is, run OpenVPN on 444, then port forward 443->444 on another interface.)

Actions
Copy link

Also available in: Atom PDF