Project

General

Profile

Actions

Bug #7568

closed

unused openvpn client_mgmt_port ?

Added by Jeremy C. Reed over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
OpenVPN
Target version:
Start date:
05/20/2017
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4
Affected Architecture:
All

Description

vpn_openvpn_server.php
configures client_mgmt_port
but as far as I can tell this number is not used
and the management is using a Unix domain socket and not a TCP port.

(I noticed this while working on my book.
My list of bugs is at http://reedmedia.net/books/pfsense/bugs.html )

Actions #1

Updated by Jim Pingle over 4 years ago

  • Category changed from VPN (Multiple Types) to OpenVPN
  • Status changed from New to Assigned
  • Assignee set to Jim Pingle
  • Target version set to 2.4.0
  • Affected Version set to 2.4
  • Affected Architecture All added
  • Affected Architecture deleted ()

It was a part of the OpenVPN Client Export package that was used with the OpenVPNManager add-on. That add-on has been removed, since it was no longer necessary. Any references to it can be removed.

Actions #2

Updated by Phillip Davis over 4 years ago

Indeed, in "the olden days" we had to run OpenVPN Manager on a Windows client so that unpriv users could use it to start/stop their OpenVPN connections. If users had multiple configs installed on their client Windows system (e.g. for links up to different offices), then each one had to have a unique port number that OpenVPN Manager would talk to in order to start/stop/control the particular client.

Actions #3

Updated by Jim Pingle over 4 years ago

  • Status changed from Assigned to Feedback
  • % Done changed from 0 to 100
Actions #4

Updated by Jim Pingle over 4 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF