Project

General

Profile

Actions
Copy link

Bug #3573

closed

tun/tap interfaces not available for assignment in 2.2

Added by Gilmar Cabral about 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ermal Luçi
Category:
Interfaces
Target version:
2.2
Start date:
04/05/2014
Due date:
% Done:

0%

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

Description

Version 2.2 Alpha options not create virtual interface.
Pfsense Version 2.1.1 is possible create virtual interface using openvpn interface.

Files

58.png (206 KB) 58.png Gilmar Cabral, 04/05/2014 07:43 AM
Actions
Copy link
 #1

Updated by Chris Buechler about 10 years ago

  • Subject changed from Create Interface Virtual Pfsense 2.2 Alpha not available to tun/tap interfaces not available for assignment in 2.2
  • Category set to Interfaces
  • Target version set to 2.2
  • Affected Version set to 2.2

tun and tap interfaces should be available for assignment, whether tunX/tapX or ovpnsX/ovpncX.

Actions
Copy link
 #2

Updated by Jim Pingle about 10 years ago

The OpenVPN interfaces do appear for assignment in current code.

For interfaces made outside of OpenVPN:
tunX interfaces do not appear for assignment
tapX interfaces DO appear for assignment

So it appears to be partially fixed.

Actions
Copy link
 #3

Updated by Jim Thompson almost 10 years ago

  • Assignee set to Ermal Luçi
Actions
Copy link
 #4

Updated by Ermal Luçi over 9 years ago

I do not think this is a good option to allow.

Since whoever creates the tun needs to provide a sticky interface name and tunX its not a stable one.

I do not consider a thing to be allowed.

Actions
Copy link
 #5

Updated by Chris Buechler over 9 years ago

  • Status changed from New to Closed

the original issue here was that OpenVPN's tun interfaces weren't being added at all at the time. the remainder is a non-issue

Actions
Copy link

Also available in: Atom PDF