remove css
Attempt to recognize pfsync entries from pf logs.
Merge pull request #779 from CharlieMarshall/fileCss

remove css from edit.php page
Add scope to target when it is a link-local, it helps ticket #3150
Add scope to target when it is a link-local, it helps ticket #3150
Add patch from the ticket to fix #3149
Remove this particular form tag that doesn't appear to serve any purpose on this page, and breaks the drop-down zone selector. Fixes #3153
Fixup check for existing easyrule block rule to account for the ipproto and when the ipproto is blank.
fix text to remove non-applicable copy/paste from v4 relay
Delete old route for remote gateway when its IP changes. It fixes #3155
Certificate Manager, for 'Create an internal Certificate' use the correct 'Digest Algorithm'
Merge pull request #781 from PiBa-NL/CreateCertificate_DigestAlgorithm

Certificate Manager, for 'Create an internal Certificate' use the correct 'Digest Algorithm'
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.
Merge pull request #783 from phil-davis/master

Add option to specify client management port for OpenVPN client export use
Support the names used by the status page as well as those used internally by service entries.
Also run mtree check post-upgrade.
If upgrading NanoBSD, try to grab the previous timezone file so the zone is preserved on the next boot.
s/require/require_once/g for filter.inc to avoid redeclaration errors in some rare cases.
Improve var names in get_memory

realmem is the amount of actual (real) memory installed - the size of the RAM card - e.g. 256MB
physmem is the amount of memory available to FreeBSD after BIOS, video... has stolen some of realmem.
The variable names currently used are not very helpful for code readability. This standardises them. No functional change here.
Use updated get_memory var names

The value of minimum_ram_warning is designed to be compared to hw.physmem - so do that. Usse the appropriate physmem or realmem value in each place.