Project

General

Profile

Actions

Bug #7053

closed

OpenVPN Client Specific Overrides - GUI Omissions and Errors

Added by Greg Siemon almost 5 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
OpenVPN
Target version:
Start date:
12/30/2016
Due date:
% Done:

100%

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

Description

The OpenVPN Client Specific Overrides page under OpenVPN settings only has a single Tunnel Network field. In fact this field seems to be for an IPv4 address. There is currently no way to set up an IPv6 Tunnel Network without resorting to the advanced config fields. There should be separate IPv4 and IPv6 Tunnel Network fields as per the OpenVPN Server and Client setup pages.

Additionally, the descriptions on each of the fields under Tunnel Settings - Remote Networks could be clearer.

IPv4 Remote Networks
These are the IPv4 networks that will be routed to this client specifically using iroute, so that a site-to-site VPN can be established. Expressed as a comma-separated list of one or more CIDR ranges. May be left blank if there are no client-side networks to be routed.
NOTE: Remember to add these subnets to the IPv4 Remote Networks list on the corresponding OpenVPN server settings.
This should say "the server" not "this client" as the Remote Networks specified here are local to the client. The Local and Remote networks are from the Server's perspective not the client. Maybe a short note to explain this would help to understand what to do here.

Similarly for IPv6 Remote Networks. The description also incorrectly refers to IPv4 and should be changed to IPv6.

Actions

Also available in: Atom PDF