Provide upgrade config code to migrate unbound settings from 2.1 package to 2.2 base. Bump config version to 11.1. It fixes #3880
Make sure unbound user and group is also created during upgrade config
Add a note clarifying the usage of OpenVPN's Auth Digest setting.
NTP Service GPS page always reverts to 'Custom' GPS type

Remember and correctly display GPS type setting
Provide a toggle for apinger debug messages to be logged to syslog. To help with roubleshooting issues
Merge pull request #1287 from jean-m-cyr/master
Fix close button in the info box
Merge pull request #1288 from brunostein/fix_button_close_info_box
Remove unbound files, menu and service during config upgrade, otherwise things can go really bad with functions redeclared un base and package unbound.inc and config corrupted when upgrading from 2.1.x with unbound installed to 2.2. PBI and package section are both removed later during package upgrade
outgoing ip incorrectly set in unbound.conf

DNS resolver outgoing IP interface IP address is incorrectly set to the
last inbound interface IP address... fix it.
Merge pull request #1289 from jean-m-cyr/master
Support IPV6 in unbound.conf

IPv6 addresses are not included in unbound config and access list
Remove also old unbound startup script
Merge pull request #1290 from jean-m-cyr/master
Be more strict on user removal checking array id and also username to avoid removing wrong users when browser back button is used. It should fix #3856
Be more strict on removing groups checking group id and group name, it avoids issues like happened to users on ticket #3856. While I'm here, replace GET by POST
Remove useless check for alias description matching an interface description

While looking at other checks in the code I noticed this check. It was not effective anyway, because the first line inside "if ($_POST)" below does
unset($input_errors);
which undoes this check anyway.

In any case the check is not relevant. For example I might have interface WAN with description (which is really the alternate/display name for an interface) as MYISP.

I cannot also have an Alias with name MYISP - that is checked for already later in the code.
But I can have an Alias with description MYISP - in the case of an Alias the description really is just helpful text for the user, it is the name that really counts for use in the pf configuration.
So the code is not needed.
Merge pull request #1292 from phil-davis/patch-18
firewall_aliases_edit UI text changes

If type URL Table then the heading "Description" on the 3rd column gets suppressed (I am not really sure why that is, since the description data entry box still appears - I guess someone intended that the data entry box itself also be suppressed, since URL Table takes just a single line entry, the overall description of the alias should be enough - no need for a per-line description.)
In any case, if the user then selects some other Alias Type, the "Description" heading on the 3rd column is not re-enabled.
This change fixes that.
I also implemented what is suggested in Redmine #3893 - making the 1st column heading say "IP or FQDN", "Network or FQDN". IMHO that looks fine on the UI and cannot do any harm. (and yes, the longer explanatory text  already tells the user that an FQDN is allowed in these cases.)
Merge pull request #1293 from phil-davis/patch-20