Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move key-direction infront of tls-auth for old network-manager-openvp… #529

Closed
wants to merge 1 commit into from

Conversation

RolfWojtech
Copy link
Contributor

OpenVPN configs generated by pfsense currently do not work in network-manager-openvpn of Ubuntu 16.04 because of a bug: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1643282
One could argue that pfsense generates a perfectly valid config thus no change is needed but Ubuntu 16.04 is still very widespread and supported until 2021 and it does seem to affect many users (the error message is really unclear).

…n versions

OpenVPN configs generated by pfsense currently do not work in network-manager-openvpn of Ubuntu 16.04 because of a bug: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1643282
One could argue that pfsense generates a perfectly valid config thus no change is needed but Ubuntu 16.04 is still very widespread and supported until 2021 and it does seem to affect many users (the error message is really unclear).
@jim-p
Copy link
Contributor

jim-p commented Jun 15, 2018

Has this been tested and proven to work with other clients? I get wanting to fix Ubuntu but we need to be certain that it doesn't break any others.

@RolfWojtech
Copy link
Contributor Author

I have tested it with the Windows OpenVPN GUI and it works fine there as well. In general these directions are not supposed to have an order so yes, this Pull Request would just be working around a bug in network manager, very likely not affecting any other clients. (https://forums.openvpn.net/viewtopic.php?t=7964 )

@jim-p
Copy link
Contributor

jim-p commented Jul 5, 2018

In an effort to improve the tracking of changes and bug/feature requests, we have decided to require an entry on the pfSense Redmine issue tracker associated with every pull request, and likewise the Redmine entry should also have a link back to the pull request.

If you could, please associate this PR to a Redmine issue either by locating an existing issue at https://redmine.pfsense.org or by creating a new issue. Add a link to the Redmine issue that points to this PR, and also add a link on the PR to the Redmine issue.

For more information, see https://doc.pfsense.org/index.php/Submitting_a_Pull_Request_via_Github

Thanks!

@jim-p
Copy link
Contributor

jim-p commented Jul 20, 2018

I committed a slightly different version of this, it will be in snapshots for testing soon!

@jim-p jim-p closed this Jul 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants