Main repository for pfSense
Go to file
Phil Davis faf61f12de Add option to specify client management port for OpenVPN client export use
See forum http://forum.pfsense.org/index.php/topic,63668.0.html and OpenVPN Manager GitHub discussion https://github.com/jochenwierum/openvpn-manager/issues/17
This allows a different client management port to be specified for use by OpenVPN client export when generating a client config for use with OpenVPN manager. Typically a company could have multiple offices with OpenVPN "road-warrior" access. Some users might need to connect to different offices at different times, so they would have multiple OpenVPN client configs installed on their laptop. For this to work with OpenVPN Manager, each client config needs to have a different management channel - only 1 can use the default of "166". The company can chooose a different number in the road-warrior server "client parameters" section at each office. Then the generated client config from each office will have a unique management channel port number.
2013-08-25 23:23:54 -07:00
boot Add hw.usb.no_pf="1" to loader.conf on nanobsd 2013-02-01 22:58:38 +01:00
cf/conf trigger setup wizard 2009-11-16 01:44:37 -05:00
conf.default Fixes #2979 2013-05-29 10:47:43 -03:00
etc Delete old route for remote gateway when its IP changes. It fixes #3155 2013-08-22 16:14:24 -03:00
root Add nonewline to end of file to avoid issues when new options are added 2013-04-29 11:05:22 -03:00
sbin Whitespace fixes 2013-08-01 11:14:08 +00:00
tmp Be a little smarter about the default kernel in rare cases where we cannot determine what was in use. 2013-01-03 09:29:50 -05:00
usr Add option to specify client management port for OpenVPN client export use 2013-08-25 23:23:54 -07:00
.gitattributes Add .gitattributes file to help maintain proper newlines. 2012-12-10 11:21:56 -05:00
.gitignore Ignore vim swap files 2013-03-08 14:41:01 -03:00