Project

General

Profile

Bug #769

OpenVPN interface assignment on upgrade

Added by Jim Pingle almost 9 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Backup/restore
Target version:
Start date:
07/29/2010
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0
Affected Architecture:

Description

If you restore a 1.2.3 config to 2.0, and that config has assigned OpenVPN interfaces, and the restore triggers the interface reassignment process, the OpenVPN interfaces from the restored configuration are not available for assignment.

Associated revisions

Revision 4f1ebacb (diff)
Added by Ermal Luçi over 8 years ago

Ticket #769. Convert assigned openvpn interfaces by using custom options to 2.0 style assigned openvpn interfaces. This upgrade removes the 'dev tun#' from cutom options and upgrades the assigned interface name to new style.

History

#1 Updated by Chris Buechler almost 9 years ago

There's another somewhat related ticket open - the conversion process will break OpenVPN completely where interfaces are assigned, as it'll end up with two dev tunX lines, plus the actual assignment breaking. May be able to consolidate this into that as they're ultimately the same issue.

#2 Updated by Ermal Luçi almost 9 years ago

i think it is easier to handle openvpn as all other cloned interfaces, build the list of assignment manually rather than expecting a list from ifconfig.

Though i am not sure if only interfaces_assign needs modification or other places rely on this!

#3 Updated by Ermal Luçi over 8 years ago

  • Status changed from New to Feedback

#4 Updated by Ermal Luçi over 8 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF