List GWGs in Interface to send update from
DyndDNS edit: unset vars when no longer used
Update copyright_years to be calculated on the fly.
Move to zerocopy_enbale for bpf to optimize bpf logging which uses bpf interface. This should increase the general performance since pflog is always enabled.
Use empty here for testing even if the setting is unset
Do not allocate the same pipe to everyone rather give each person its own!
Oops correct php syntax
minor spelling correction for pfSense master branch

Signed-off-by: Isaac (.ike) Levy <ike@blackskyresearch.net>
Allow individual line descriptions on alias bulk import

This enhancement allows the user to make a text file of IP addresses, IP subnets and/or IP ranges, like they have always been able to do, but with this they can put a description after each IP number and that description text will be saved in the alias. All existing functionality without specifying a description is unchanged, so it is backward-compatible.
This is handy when having aliases that are on all my pfSense boxes, I can make 1 text file, bulk import it on every system and now include descriptions of each chunk of IP address space.
Note: The artificial limit of 200 character descriptions is to catch the case where a user pastes a long list or IP addresses, but they are all on 1 line. An error message is given, rather than importing the 1st IP and considered the remaining ones as the description.
Bulk Import: fix copy-paste var name error
Update reserved_keywords checks to match firewall_aliases_edit

firewall_aliases_import should have the same checks for reserved names as firewall_aliases_edit
This code should really be in a function in a common include file, but which one is the appropriate one?
For now I made the checks the same.
Add an option to force a gateway to be down, it fixes #2847
This might also say "icmpv6" here and lead to a bad rule.
Add 'limited' to ntpd restrict list to workaround CVE-2013-5211. It fixes #3384
Check for vertical bars in alias detail descriptions

The descriptions of each entry in an alias are stored in config.xml as a list delimited by "||". So you cannot have "||" in the actual description (or the description effectively splits into the next entry). Also you cannot start or end the description with "|" or it will be very confusing having the config with "|||" in it.
This code validates all that sort of invalid input.
Check for vertical bar at start or end of description