pfSense

gateway monitoring, give apinger some time to properly 'initialize' before using its results

(cherry picked from commit 29fa6f0f46ba039a67a93c00a08bcaecc3935b78)

Restore bad login message

If the user chose to have DDNS Hostnames forced, respect that in the backend code for static map IPv6 hosts. Fixes #7324

(cherry picked from commit bad77fc0aca53e560710eaa75b3de198d7edb8f3)
(cherry picked from commit 50608d158646e32a612f845bcd0dfa91ce37d713)

shaper, hfsc cannot use priority, as such don't show the field in the webgui.
Also for the other shapers 0 is a valid priority
While fairq causes a error loading rules with a priority above 7 so prevent that.

(cherry picked from commit 417991954c631fcc33ed3dc38a99ae3efecfea6e)

Some systems - only one that I am aware of, complain that unbound is starting before dchp6 has completed leading to problems, this occurs only on boot.

Further examination did indeed show that the problem is caused by unbound starting before the dhcp6c - RTSOLD - rc.newwanipv6 have completed, making sure that these have all run before unbound is allowed to start corrects the problem....

Do not use reference to avoid losing data

Ignore upgrade_167_to_168() when upgrade_166_to_167() runs, they are both the same

Always run additional_config_upgrade() and do it after config is written

Each item in additional_config_upgrade() must write config after changing it

Detect old workarounds in config upgrade and deal with them