Project

General

Profile

Actions
Copy link

Bug #7074

closed

Due to OpenVPN protocol selection changes, automatic port number guessing/adjustment is not working

Added by Jim Pingle over 7 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Renato Botelho
Category:
OpenVPN
Target version:
2.4.0
Start date:
01/03/2017
Due date:
% Done:

100%

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

Description

After the protocol selection changes needed for #7062, the OpenVPN server page is not adjusting the port numbers like it used to.

For example if there was a UDP server on 1194, it would automatically use 1195 for the next new server.

There may also be some input validation that isn't properly detecting collisions.

Note:
  • "UDP" is dual stack and conflicts with "UDP4" and "UDP6"
  • "TCP" is dual stack and conflicts with "TCP4" and "TCP6"
  • "UDP4" and "UDP6" do not conflict unless the interface is set to "any"
  • "TCP4" and "TCP6" do not conflict unless the interface is set to "any"
Actions
Copy link
 #1

Updated by Renato Botelho over 7 years ago

  • Assignee set to Renato Botelho

I'll work on it

Actions
Copy link
 #2

Updated by Renato Botelho over 7 years ago

  • Status changed from Confirmed to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #3

Updated by Jim Pingle over 7 years ago

  • Status changed from Feedback to Resolved

I tried a few combinations and it all worked. Creating a new instance or using the wizard properly guessed the next highest available port as well.

Actions
Copy link

Also available in: Atom PDF