https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162020-02-24T15:21:41ZpfSense bugtrackerpfSense - Bug #10287: OpenVPN TLS key direction value added to existing tunnels is 0.https://redmine.pfsense.org/issues/10287?journal_id=447702020-02-24T15:21:41ZJim Pingle
<ul><li><strong>Target version</strong> changed from <i>Future</i> to <i>2.4.5</i></li></ul> pfSense - Bug #10287: OpenVPN TLS key direction value added to existing tunnels is 0.https://redmine.pfsense.org/issues/10287?journal_id=447712020-02-24T15:22:04ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> pfSense - Bug #10287: OpenVPN TLS key direction value added to existing tunnels is 0.https://redmine.pfsense.org/issues/10287?journal_id=447722020-02-24T15:35:25ZJim Pingle
<ul></ul><p>In the selection list, when <code>tlsauth_keydir</code> is empty/unset, both the list entry for default and 0 are marked with <code>selected</code>.</p>
<p>Probably we need to prefill the empty value with something like "default" and then check for that on the backend rather than rely on it being empty.</p> pfSense - Bug #10287: OpenVPN TLS key direction value added to existing tunnels is 0.https://redmine.pfsense.org/issues/10287?journal_id=447762020-02-25T08:05:06ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Correct 'default' behavior of OpenVPN TLS key dir. Fixes #10287" href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/d2011b0addd27766e6b402270c79d06c6c485f04">d2011b0addd27766e6b402270c79d06c6c485f04</a>.</p> pfSense - Bug #10287: OpenVPN TLS key direction value added to existing tunnels is 0.https://redmine.pfsense.org/issues/10287?journal_id=448362020-02-28T04:30:41ZViktor Gurov
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>tested on 2.4.5.r.20200228.0300</p>
<p>works as expected on the Client/Server pages</p>