Project

General

Profile

Actions

Regression #15768

closed

OpenVPN Windows Client fails to connect

Added by dylan mendez about 2 months ago. Updated about 1 month ago.

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

100%

Estimated time:
Plus Target Version:
24.11
Release Notes:
Force Exclusion
Affected Version:
2.8.0
Affected Architecture:

Description

Version 24.08.a.20240925.0600

1) OpenVPN server in Subnet Mode

            <tunnel_network>192.168.25.0/24</tunnel_network>
            <gwredir>yes</gwredir>
            <local_network>192.168.0.0/24, 192.168.12.45/32</local_network>
            <topology>subnet</topology>

2) User with the following override ifconfig-push 192.168.25.5 255.255.255.0;
3) pfSense shows client connected under Status - OpenVPN Screenshot

4) OpenVPN GUI Client fails with the following log

2024-10-06 19:19:29 There is a problem in your selection of --ifconfig endpoints [local=192.168.25.5, remote=255.255.255.0]. The local and remote VPN endpoints must exist within the same 255.255.255.252 subnet. This is a limitation of --dev tun when used with the TAP-WIN32 driver. Try 'openvpn --show-valid-subnets' option for more info.
2024-10-06 19:19:29 Exiting due to fatal error

5) Trying to connect again will show up duplicates under Status - OpenVPN connected at the same time.

This works as expected on the previous development snapshot as well as release 24.03


Files

clipboard-202410061919-nauzx.png (11.7 KB) clipboard-202410061919-nauzx.png dylan mendez, 10/07/2024 01:19 AM
Actions #1

Updated by Marcos M about 1 month ago

  • Description updated (diff)
Actions #2

Updated by Marcos M about 1 month ago

  • Status changed from New to Resolved
  • Assignee set to Marcos M
  • Target version set to 2.8.0
  • % Done changed from 0 to 100
  • Plus Target Version set to 24.11
  • Release Notes changed from Default to Force Exclusion
  • Affected Version set to 2.8.0
Actions

Also available in: Atom PDF