https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162017-02-12T08:37:03ZpfSense bugtrackerpfSense - Bug #7252: OpenVPN widget, connect time of roadwariors shows a numberhttps://redmine.pfsense.org/issues/7252?journal_id=314772017-02-12T08:37:03ZPhillip Davisphil@jankaritech.com
<ul></ul><p>Pull Request <a class="external" href="https://github.com/pfsense/pfsense/pull/3537">https://github.com/pfsense/pfsense/pull/3537</a></p>
<p>Actually I think it could be done just by cherry-picking <a class="external" href="https://github.com/pfsense/pfsense/commit/6f17547aaa073ca460c8bbd8dc1dc5c12922b76d">https://github.com/pfsense/pfsense/commit/6f17547aaa073ca460c8bbd8dc1dc5c12922b76d</a> which updated the code that parses this stuff, so it knows the field order that comes from the new OpenVPN output.</p> pfSense - Bug #7252: OpenVPN widget, connect time of roadwariors shows a numberhttps://redmine.pfsense.org/issues/7252?journal_id=314782017-02-12T08:40:53ZPhillip Davisphil@jankaritech.com
<ul></ul><p>At the moment the field is displaying one of the byte counts, so it will be completely misleading to leave it like that. I think this should have higher priority than "low" and should be fixed between RC1 and RC2 or RELEASE.</p> pfSense - Bug #7252: OpenVPN widget, connect time of roadwariors shows a numberhttps://redmine.pfsense.org/issues/7252?journal_id=314792017-02-12T09:58:41ZJim Thompsonjim@netgate.com
<ul><li><strong>Assignee</strong> set to <i>Renato Botelho</i></li></ul><p>Shouldn't this be architecture All?</p> pfSense - Bug #7252: OpenVPN widget, connect time of roadwariors shows a numberhttps://redmine.pfsense.org/issues/7252?journal_id=314802017-02-12T10:07:10ZPi Ba
<ul></ul><p>I didn't test architecture 'all' but likely yes.. As for priority, its a display issue, actual functionality of the openvpn works okay so i chose 'low' there. It really doesn't matter much but would be nice to have fixed which is why i did set 2.3.3 as a target. Feel free to modify fields as deemed appropriate.</p> pfSense - Bug #7252: OpenVPN widget, connect time of roadwariors shows a numberhttps://redmine.pfsense.org/issues/7252?journal_id=314832017-02-12T12:44:47ZJim Pingle
<ul></ul><p>I didn't notice that OpenVPN 2.4 was on pfSense 2.3.3. That means there are probably more OpenVPN 2.4-isms to account for than just this, like the fact that NCP will be on by default and syntax changes like <a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: OpenVPN 2.4: client-cert-not-required is deprecated, replace with "verify-client-cert none" (Resolved)" href="https://redmine.pfsense.org/issues/7073">#7073</a> and <a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: OpenVPN 2.4 treats "udp" and "tcp" as dual stack now, move old preference to udp4/tcp4 (Resolved)" href="https://redmine.pfsense.org/issues/7062">#7062</a></p>
<p>I'd say step it down to OpenVPN 2.3 but in the FreeBSD ports tree they have the OpenVPN 2.3 port marked as deprecated and scheduled for expiration next month so that's probably not a good long-term plan.</p> pfSense - Bug #7252: OpenVPN widget, connect time of roadwariors shows a numberhttps://redmine.pfsense.org/issues/7252?journal_id=314992017-02-13T09:16:48ZJim Pingle
<ul></ul><p>We're moving 2.3.3 back to OpenVPN 2.3 since it appears to be the path of least disruption.</p> pfSense - Bug #7252: OpenVPN widget, connect time of roadwariors shows a numberhttps://redmine.pfsense.org/issues/7252?journal_id=315012017-02-13T09:34:49ZMichael Kellogggrandrivers@gmail.com
<ul></ul><p>so if someones on 2.3.3 with opnvpn 2.4 will change back to 2.3 have ramifications ??</p> pfSense - Bug #7252: OpenVPN widget, connect time of roadwariors shows a numberhttps://redmine.pfsense.org/issues/7252?journal_id=315022017-02-13T09:38:04ZJim Pingle
<ul></ul><p>No, it will work fine for everyone (Well, 99.999%). OpenVPN won't have any compatibility issues between the two. It will actually be better since pfSense 2.3.3 snapshots do not have any code to handle changes in OpenVPN 2.4 like deprecated syntax, status output changes (like this), NCP would make your connecting cipher selection unpredictable, etc, etc.</p>
<p>It's a good move in this case to back it down.</p>
<p>Only someone who manually put OpenVPN 2.4-specific directives in the advanced options on a 2.3.3 snapshot would have a problem.</p> pfSense - Bug #7252: OpenVPN widget, connect time of roadwariors shows a numberhttps://redmine.pfsense.org/issues/7252?journal_id=315032017-02-13T09:51:43ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>OpenVPN port was downgraded to 2.3.x</p> pfSense - Bug #7252: OpenVPN widget, connect time of roadwariors shows a numberhttps://redmine.pfsense.org/issues/7252?journal_id=315352017-02-15T05:10:39ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>Looks good with OpenVPN 2.3 being back</p>