Project

General

Profile

Actions

Bug #12232

closed

OpenVPN status incorrect for TAP servers without a defined tunnel network

Added by Max Leighton about 3 years ago. Updated almost 3 years ago.

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

100%

Estimated time:
Plus Target Version:
22.01
Release Notes:
Default
Affected Version:
2.5.2
Affected Architecture:

Description

Creating an OpenVPN server TAP mode without specifying the IPv4 Tunnel Network will result in the Status>OpenVPN page not showing Client Connections. pfSense as a client on the other end of this tunnel will show that it is connected and traffic will pass successfully, but the server Status page doesn't see the connected client.

The settings I'm using to recreate it are:

UDP4 (1196)
Mode: Peer to Peer ( SSL/TLS )
Data Ciphers: AES-256-GCM, AES-128-GCM, CHACHA20-POLY1305, AES-256-CBC
Digest: SHA256
D-H Params: 2048 bits

2.5.2-RELEASE (amd64)
built on Fri Jul 02 15:33:00 EDT 2021
FreeBSD 12.2-STABLE


Files

openvpn-config-tap-server-test.xml (2.23 KB) openvpn-config-tap-server-test.xml Max Leighton, 08/07/2021 02:28 PM
tap-server-status.png (16.8 KB) tap-server-status.png Max Leighton, 08/07/2021 02:28 PM
tap-client-status.png (20.9 KB) tap-client-status.png Max Leighton, 08/07/2021 02:28 PM

Related issues

Related to Regression #12884: OpenVPN status display for TAP mode services shows peer-to-peer instead of client list in certain casesResolvedViktor Gurov

Actions
Actions

Also available in: Atom PDF