Advanced DHCP Client Options & Config File Override

DHCP v4:
Protocol Timing
Send Options
Request Options
Require Options
Option Modifiers

DHCP v6:
Interface Statement
Identity Association Statement
Prefix Interface Statement
Authentication Statement
Keyinfo Statement

DHCP v4 & v6:
Config Override File
Add section tag to v6 documentation links.

Put v4 send, request, require & modifies in lease requirements and requests section.
No functional changes.
Config file formating:

FIX - Add new line after comment so first option statement is on uncommented line.
Prefix send host-name with tab.
Don't restrict the content of descr when making CA/Certs, it's free-form.
Add the ability to disable Growl or SMTP notifications but keep their settings intact. Remove automatic test messages on save. Add individual test buttons for Growl and SMTP that work even if the service(s) are disabled.
EAOrigin.pat - Traffic Sharping Layer 7

The EA Store is now Origin, Tested and works (for now) will make changes if i come to anything useful.
Merge pull request #670 from francisuk/patch-1

EAOrigin.pat - Traffic Sharping Layer 7
Split actual SMTP send into its own function.
Add a simple CLI mail script capable of sending an SMTP message using echo/piped input, e.g. ifconfig -a | mail.php -s"ifconfig output"
Fix exec perms on mail.php
Update list of mobile service providers
Allow queues to be deleted, it fixes #3037
Fix max length for wpa passphrase, it fixes #3034
TCP flags are valid on any type of rule, don't skip them on block or reject rules
allow defining dhcp static mappings using dhcp-client-identifier
add MSS clamping to setup wizard. Now that MTU and MSS are separate, the MTU description was wrong, and both need to be there.
not true you have to log in again since HTTP basic auth was deprecated.
Don't flip the IPv6 allow setting just because people are upgrading. Just upgrading versions shouldn't change this behavior. As much as most of us would like people to start deploying IPv6, the vast majority aren't going to be immediately post-upgrade, and changing this can change the firewall policy behavior by allowing v6 that previously wasn't allowed. Upgrades should never change the firewall behavior like that. At the time it was done, everyone using the 2.1 code base was using it for IPv6, so of course it tripped up quite a few people.
Provide full path to route binary
Provide full path to route binary