Project

General

Profile

Actions

Feature #814

closed

GUI should allow to bind openvpn on different ip same port

Added by Ermal Luçi over 11 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Low
Category:
OpenVPN
Target version:
Start date:
08/09/2010
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:

Actions #1

Updated by Chris Buechler over 11 years ago

  • Category set to OpenVPN
  • Target version set to 2.0
  • Affected Version set to 2.0
Actions #2

Updated by Chris Buechler over 11 years ago

  • Target version changed from 2.0 to Future

This is because the management interface relies on the same port as the server is listening on, which changing would have a number of complications. If someone wants to knock this out for 2.0 that's fine but it's not a critical issue for release given the complications it introduces.

Actions #3

Updated by Jim Pingle about 11 years ago

This can be done now because Ermal converted the management interface over to UNIX sockets, so the port from the GUI should no longer matter to the management interface.

We just need to make sure the input validation is smart enough to reject only if there isn't an interface-specific conflict (or if one has chosen 'any' interface on a certain port)

Actions #4

Updated by Jim Pingle about 11 years ago

The wizard also needs adjusted to accept this scenario (Reported in #1002, but that was closed in favor of using this ticket).

Actions #5

Updated by Chris Buechler over 9 years ago

  • Tracker changed from Bug to Feature
Actions #6

Updated by Carlos Cesario over 9 years ago

Hello, already is possible run 2 openvpn instances in same port using diferent Wan Interfaces?

Actions #7

Updated by ahshang ang over 9 years ago

Vote for this feature.

Actions #8

Updated by Jim Pingle almost 9 years ago

This should be possible now but there is a new issue holding it back. Now that we can assign a gateway group as the "interface" for an OpenVPN instance, the IP would not only have to be checked against the other IPs used directly, but also against any potential IP/interface inside a gateway group.

Actions #9

Updated by Renato Botelho almost 9 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #10

Updated by Renato Botelho almost 9 years ago

  • Assignee set to Renato Botelho
  • Target version changed from Future to 2.1
  • Affected Architecture All added
  • Affected Architecture deleted ()
Actions #11

Updated by Chris Buechler almost 9 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF