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.
Sometimes it is a bit difficult to work out which interface descriptive name is which pfSense internal interface name (wan, lan, opt1, opt2...). It is useful to know for:
a) hardware that has wan, lan, opt1... pre-printed on the case (some Alix cases for example), making it easier for less-trained remote office staff to work out which cable corresponds to which interface in pfSense.
b) looking in config.xml or other techo places where the internal pfSense name is stored/referenced - knowing that straight from a status GUI display saves having to first find the descriptive name in the config, then the pfSense internal name.
What do you think? Is this a worthwhile place to display this data?
Even the Error message says: "This Hostname, IP or MAC address already exists." the IP Address was not checked if it already was given to a client as static mapped
* Add filter expression
* Add limit number of rows option (default 100)
* Run one netstat for each section
* Load netstat result using ajax after page is loaded
