Project

General

Profile

Actions
Copy link

Bug #449

closed

OpenVPN died when PPPOE link came up with a different IP.

Added by Deon George over 14 years ago. Updated over 14 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
OpenVPN
Target version:
2.0
Start date:
03/24/2010
Due date:
% Done:

0%

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

Description

I have both a OpenVPN client configuration (connecting to a server on the net with a static IP), and an OpenVPN server configuration.

When my PPPOE link dropped and came back up with a different IP, both the openvpn processes stopped. IE: my client connection to the remote server stopped, as well as my openvpn server stopped and didnt restart automatically (I waited about 10 mins). The logs showed this:

Mar 25 11:44:10 openvpn51140: TCP/UDP: Socket bind failed on local address 124.168.x.x:11196: Can't assign requested address
Mar 25 11:44:10 openvpn51140: Exiting
Mar 25 11:44:10 openvpn39460: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Mar 25 11:44:11 openvpn39460: TCP/UDP: Socket bind failed on local address 124.168.x.x:1194: Can't assign requested address
Mar 25 11:44:11 openvpn39460: Exiting

In this case 124.168 was the old address...

Two issues:
  • Shouldnt the openvpn service restart automatically?
  • There is no way to manually restart it. Be nice if it was on the dashboard like ntpd, dhcpd are.)

(A resave of each configuration resulted in the openvpn process restarting. Obviously a reboot would do the same thing - but a little drastic where pfsense is being used on dynamic ip based links.)

Actions
Copy link

Also available in: Atom PDF