pfSense

Improve processing of DNS server changes

What a pain this was. The user can blank out a DNS server from a position in the middle of the list. e.g. they had all 4 entries previously filled, and then they blank out DNS server #3. The way the DNS servers are stored in the config, they are just the defined ones in an "un-indexed" array. So actually entries 1, 2 and 4 on the screen become 1st, 2nd and 3rd in the config. The selected gateways for 1, 2 and 4 then have to end up in positions 1, 2 and 3 to match the stored DNS servers....

Enhanced validation of general DNS servers and gateways

Change string to "Maximum new connections per host / per second(s)"

Clarifying the setting's meaning.

As suggested by forum member "Senser" on
https://forum.pfsense.org/index.php/topic,65472.msg356024.html#msg356024

Catch a validation issue reported on the mailing list thread: IPv6 address data validation from: Brian Candler. It prevents putting a subnet in the address field since it then breaks the whole filter generation process

Fixup pkg_nochecksig option

Fix for #3416

Correct javascript error which prevents PPP/PPPoE per-link settings from
being displayed (bandwidth, MTU, MRU, MRRU).

Make Local the default filter for Traffic Graph

to preserve the previous standard behavior that shows "Local" when Traffic Graph starts.

Make Local the default filter for Traffic Graph

to preserve the old behavior, that it shows "Local" traffic when first started.

Return all when all or remote is selected on Traffic Graph

Add specific permission for easyrule.