Project

General

Profile

Actions

Regression #13274

closed

OpenVPN override IPv4 tunnel network field changing value improperly

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

Status:
Resolved
Priority:
High
Assignee:
Category:
OpenVPN
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
22.05
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

For an override on a subnet topology VPN, the mask on the tunnel network in the override has to reflect the subnet mask of the VPN tunnel network. However, when saving the override the entered address is being changed to the network address of the given subnet/mask, losing the actual address the user wants.

e.g. Enter 10.40.104.100/24 and it ends up 10.40.104.0/24.

Using /32 does not work as OpenVPN will not properly use the address+mask and it sets it up with the wrong values.

If you ignore the remote network field and add a proper advanced config entry of ifconfig-push 10.40.104.100 255.255.255.0 then it works properly.

This was changed on #11416 but it probably should have only been changed on the server and client pages not on the override page.


Related issues

Related to Bug #11416: OpenVPN IPv4 Tunnel Network incorrectly allows hostnamesResolvedViktor Gurov02/13/2021

Actions
Actions #1

Updated by Jim Pingle over 2 years ago

  • Related to Bug #11416: OpenVPN IPv4 Tunnel Network incorrectly allows hostnames added
Actions #2

Updated by Jim Pingle over 2 years ago

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

Updated by Jim Pingle over 2 years ago

  • Plus Target Version changed from 22.09 to 22.05
Actions #4

Updated by Jim Pingle over 2 years ago

  • Status changed from Feedback to Resolved

Working as expected on the latest build. The exact tunnel network address and mask remain, and the resulting ifconfig-push directive is correct.

Actions

Also available in: Atom PDF