Project

General

Profile

Bug #3948

Changing OpenVPN from tun to tap or vice-versa breaks that instance

Added by Chris Buechler almost 5 years ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
OpenVPN
Target version:
-
Start date:
10/20/2014
Due date:
% Done:

0%

Estimated time:
Affected Version:
All
Affected Architecture:

Description

Where you have an OpenVPN client or server instance defined on tun and switch to tap, or vice-versa, the ovpnc*/ovpns* interface is retained from the previous configuration. ifconfig will error out with:

Oct 20 19:14:02    openvpn[39784]: FreeBSD ifconfig failed: external program exited with error status: 1
Oct 20 19:14:02    openvpn[39784]: Exiting due to fatal error

because the ifconfig it uses on a tap isn't valid on tun, or vice versa.

To work around, "ifconfig ovpncX destroy" (or ovpnsX), then edit and save the OpenVPN instance, which will re-create the tun/tap. Or reboot.

Also available in: Atom PDF