aboutsummaryrefslogtreecommitdiffstats
path: root/config/openvpn-client-export
Commit message (Collapse)AuthorAgeFilesLines
* Bump OpenVPN client export so it uses the latest installers.jim-p2015-04-022-2/+2
|
* OpenVPN export fix index typoPhil Davis2015-01-101-1/+1
| | | | | The $server array here has and "index" key, not an "sindex" key. Actually nothing was broken by this. When the user switches server selections, server_changed() is called. That uses JavaScript and selectedIndex to work out which entry the user selected. selectedIndex is a zero-based number. It matches the zero-based index of servers, which was built from the zero-based indexes of $ras_server array, which was built from data in the config. So by good luck or good management, this array index name typo is not actually a bug. I noticed it while investigating forum https://forum.pfsense.org/index.php?topic=86263.0
* Update OpenVPN Client Export with OpenVPN 2.3.6 installers.jim-p2014-12-012-4/+7
|
* Re-fix typojim-p2014-11-041-1/+1
|
* Update OpenVPN installers to 2.3.5-Ix01. Add -I6xx installers.jim-p2014-11-043-19/+47
|
* Text typosPhil Davis2014-10-051-2/+2
|
* Text typoPhil Davis2014-10-051-1/+1
|
* Text typosPhil Davis2014-10-051-2/+2
|
* Typos in OpenVPN Manager installer welcome screenPhil Davis2014-10-051-1/+1
|
* Typos in OpenVPN Manager installer welcome screenPhil Davis2014-10-051-1/+1
|
* Bump version of OpenVPN Client Export, windows installers have been updated ↵jim-p2014-10-011-1/+1
| | | | to -I003
* Do a basic validation on useaddr valueRenato Botelho2014-06-181-3/+7
|
* Bump version of OpenVPN Client Export to indicate that the Windows installer ↵jim-p2014-06-051-1/+1
| | | | was bumped (to 2.3.4-I002)
* Bump version of OpenVPN Client Export to indicate that the Windows installer ↵jim-p2014-05-301-1/+1
| | | | was bumped (to 2.3.4-I001)
* Don't add a second tls-auth line when exporting for Viscosity.jim-p2014-04-242-2/+2
|
* Bump here toojim-p2014-04-241-1/+1
|
* Fix various OpenVPN Client Export protocol issues that prevented the export ↵jim-p2014-04-241-5/+18
| | | | from generating a valid IPv6 endpoint client config; Also the Windows installer files have been bumped to 2.3.3-I002
* Avoid a PHP error in OpenVPN client export if the user chooses one of the ↵jim-p2014-04-242-1/+4
| | | | automatic port forward methods but has no port forwards defined.
* fix typoChris Buechler2014-04-231-1/+1
|
* fix Viscosity OpenVPN client export with advanced optionsChris Buechler2014-04-161-1/+1
|
* Fixup URLs:Renato Botelho2014-03-181-5/+5
| | | | | | - Replace http by https - *.pfsense.com -> *.pfsense.org - www.pfsense.org/packages/config -> packages.pfsense.org/packages/config
* Instruct the client to use a random local port for OpenVPN in the exported ↵jim-p2013-11-253-10/+46
| | | | configuration.
* Bump version againjim-p2013-11-141-1/+1
|
* Missed this file in the previous commit.jim-p2013-11-141-14/+20
|
* Bring back tls-remote as a non-default option for those stuck on older ↵jim-p2013-11-132-9/+21
| | | | clients. Also give the user the option to disable server cert CN verification. Implements #3318
* OpenVPN Client Export - Update OpenVPN installers to 2.3.2-I003. Fix 64-bit ↵jim-p2013-11-134-16/+226
| | | | postinstall script, enable 64-bit export. (Note: 64-bit export does not work with OpenVPNManager)
* Don't include a pkcs12 line in the Viscosity config, it uses individual ↵jim-p2013-11-122-2/+2
| | | | ca/cert/key lines and not pkcs12.
* Disable "verify-x509-name" in some cases. It can cause problems with ↵jim-p2013-11-112-2/+4
| | | | auth-only setups, and also with Yealink/Snom phones since they are stuck on an older OpenVPN version that does not support this feature.
* Allow the client export package to properly match the compression setting on 2.2jim-p2013-10-312-3/+9
|
* Version bump for OpenVPN Client Exportjim-p2013-10-311-1/+1
|
* tls-remote is deprecated, use verify-x509-name, which also works on the iOS ↵jim-p2013-10-311-2/+2
| | | | client so no need to exclude it from getting the line either.
* Add auth line to client config if configured on the server (drop-down is ↵jim-p2013-10-311-0/+4
| | | | there to set it in master/2.2)
* Add an "Automatic" multi-wan option to the client export package that will ↵jim-p2013-10-233-21/+116
| | | | look for and use port forwards targeting this instance rather than the IP directly. This way you can bind to LAN or localhost, port forward on all WANs to the LAN IP:port, and then the export will include remote lines for every port forward it finds. Also works to forward multiple ports at the same instance.
* Use OpenVPN Manager client management port if specified for the server concernedPhil Davis2013-08-251-2/+7
| | | | | | If the OpenVPN server has the client management port field specified, then use that port number when generating the OpenVPN Manager client config file, otherwise use the default of "166". See: forum.pfsense.org/index.php/topic,63668.0.html Discussion: https://github.com/jochenwierum/openvpn-manager/issues/17 Related pull request on pfsense repo: https://github.com/pfsense/pfsense/pull/783
* RFC2136 hostnames should also be listed as choices for openvpn client export ↵jim-p2013-07-152-1/+6
| | | | hostnames.
* Replace spaces in a CN with _ in filenames when exporting an OpenVPN client. ↵jim-p2013-07-142-3/+3
| | | | Also only use a CN if there isn't a username to use instead. Unbreaks Windows Installer export with spaces in CN.
* Properly handle filenames containing spaces when exporting an archive. Fixes ↵jim-p2013-07-111-4/+8
| | | | #2856
* When we don't need a client cert, add a line to tell the client that we ↵jim-p2013-07-111-0/+3
| | | | don't need a client cert, or else the OpenVPN Connect app will try to force the user to pick one.
* Add Proxy Type OptionN0YB2013-06-061-10/+12
| | | | Allow UPD protocol with socks proxy
* Add Proxy Type OptionN0YB2013-06-061-1/+1
|
* Add Proxy Type OptionN0YB2013-06-061-14/+31
|
* Add Proxy Type OptionN0YB2013-06-052-7/+30
|
* Attempt to fix openvpn client export http proxy password entry.jim-p2013-05-012-2/+2
|
* fix typo/wording.jim-p2013-04-271-1/+1
|
* We are crafting a URL, not user output. Use & not & here. Unbreaks export.jim-p2013-02-061-16/+16
|
* Update HTML code in OpenVPN ExportColin Fleming2013-02-063-134/+139
| | | | | | Tidied up the javascript tag, deprecated the ampersand and escaped the slashes, added summary to tables, added missing end table cell removed duplicate width.
* Do not mix OpenVPN's secure modesbcyrill2013-01-272-2/+2
|
* Reword inline config link for iOS since that same client also exists for ↵jim-p2013-01-232-10/+24
| | | | Android with the same quirks. Provide a list of commonly used clients with download links at the bottom of the export page.
* Update OpenVPN Client Export again, rearrange options to make them more ↵jim-p2013-01-223-45/+84
| | | | clear/easy to follow. Also bump version and promote package status to reflect how stable it has become.
* Fix up the inline config format a little to make Android and iOS both happy.jim-p2013-01-172-17/+11
|