Project

General

Profile

Actions
Copy link

Bug #2411

closed

OpenVPN Automatic Rule Generation does not update TCP/UDP

Added by Phil Jaenke almost 12 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
Low
Assignee:
-
Category:
OpenVPN
Target version:
-
Start date:
05/04/2012
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0.1
Affected Architecture:
i386

Description

When changing the protocol type of an OpenVPN connection, the automatic firewall rule generation does not update the protocol correctly, which can result in false-fail as packets will not be passed normally.

To reproduce:
Create a new OpenVPN Server using UDP and any port (standard or non-standard.)
Save the new OpenVPN Server, then verify that the firewall rule has been automagically generated correctly (e.g. pass 1194/UDP for defaults) on the correct interface. This works fine.
Edit the OpenVPN Server that was just created, and change the protocol from UDP to TCP, without changing the port number. Save changes.
Examine firewall rules and find that the protocol for the associated rule has not had the protocol updated - it is still set to UDP.

Actions
Copy link
 #1

Updated by Jim Pingle almost 12 years ago

  • Status changed from New to Closed

The only place that makes a firewall rule for OpenVPN is in the wizard, and that's a one-time deal. There isn't an automatic/linked rule creation option for OpenVPN that works the way you're describing, not even on 2.1.

Actions
Copy link

Also available in: Atom PDF