<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[[solved] OpenVPN with Linux-NetworkmanagerClient]]></title><description><![CDATA[<p dir="auto">I need hours to solve this problem. In the end it was simple. My Linux Clients was unable to connect OpenVPN-Server on pfsense. In pfsence i always got error Messages like this:<br />
Jun 18 10:55:41 	openvpn 	27145 	TLS Error: cannot locate HMAC in incoming packet from [AF_INET]77.XXX.XXX.XX7:44398<br />
To import the client connection i used the nmcli import option on my Linux Clients. one of the Problems, but an easy to solve one, was nmcli import don't accept p12 files for the keys. So i used the keys of the Viscosity Client-Export of the pfsense export addon together with the Bundled Configurations Config file.<br />
But, and that was the mayor problem leading to the errors metioned above, the Viscosity tls-key (ta.key) and all other files not in p12 container, have a header like this:</p>
<h1><a class="anchor-offset"></a></h1>
<h1><a class="anchor-offset" name="2048-bit-openvpn-static-key"></a>2048 bit OpenVPN static key</h1>
<h1><a class="anchor-offset"></a></h1>
<p dir="auto">This header needs to be removed for network manager. If its removed everthing works fine. And i got stable OpenVPN-Connections to pfsense.<br />
So maybe a further version of the pfsense OpenVPN Export addon can deliver a version of the tls-key without this header to prevent others to have similar problems like me, wasting 3 or 4 hours to solve it.</p>
<p dir="auto">Thanks</p>
]]></description><link>https://forum.netgate.com/topic/188784/solved-openvpn-with-linux-networkmanagerclient</link><generator>RSS for Node</generator><lastBuildDate>Sat, 10 Oct 2026 23:53:34 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/188784.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 18 Jun 2024 09:33:05 GMT</pubDate><ttl>60</ttl></channel></rss>