Project

General

Profile

Bug #7074

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

Added by Jim Pingle 4 months ago. Updated 4 months ago.

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

100%

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"

Associated revisions

Revision f69e098f
Added by Renato Botelho 4 months ago

Fix #7074: Fix automatic port number guessing

Rework openvpn_port_used() to take care of following conflicts after
ticket #7062 was committed:

  • "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 interface is set to "any"
  • "TCP4" and "TCP6" do not conflict unless interface is set to "any"

History

#1 Updated by Renato Botelho 4 months ago

  • Assignee set to Renato Botelho

I'll work on it

#2 Updated by Renato Botelho 4 months ago

  • Status changed from Confirmed to Feedback
  • % Done changed from 0 to 100

#3 Updated by Jim Pingle 4 months 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.

Also available in: Atom PDF