(cherry picked from commit 7c5db320)

(cherry picked from commit ba9bbebe)

(legacy) there are a few ACL's without a visible UI part included, which may result in less practical redirectings when the index is not authorized.

Add the license to the ACL, so we know for sure the menu is visible.

issue https://github.com/opnsense/core/issues/724

(cherry picked from commit 1fd55b12)

(legacy) fix crashreport PHP Warning:  Illegal string offset 'wan' in /usr/local/www/services_dhcpv6.php on line 57

(cherry picked from commit 4f0a083e)

(legacy) fix crashreport Call to undefined function get_services() in /usr/local/www/fbegin.inc on line 38

(cherry picked from commit aa305e7d)

(cherry picked from commit d92af436)

(cherry picked from commit ebad9352)

(cherry picked from commit 1363689d)

(cherry picked from commit 45594476)

(cherry picked from commit d0e3d2dd)

(cherry picked from commit f173a3be)

(cherry picked from commit ababecf8)

(cherry picked from commit 70445dcb)

(cherry picked from commit c3358d74)

(cherry picked from commit 8b12976f)

(cherry picked from commit e342cd97)

(cherry picked from commit a9fa3d52)

Lookie how far we've come...

(cherry picked from commit 6ee8eb78)

(cherry picked from commit 48c5641f)

(cherry picked from commit 21418708)

(cherry picked from commit a8962f5e)

(cherry picked from commit 6374e846)

(cherry picked from commit 08c1e186)

(legacy) change behaviour of associated nat rules (https://github.com/opnsense/core/issues/695), show rule but hide edit and duplicate buttons

If for some reason a config has "typeless" rules, which don't belong to any active nat rule the user won't notice this anymore (and doesn't have the ability to remove them).
This can happen with imports from old configs for example or manually changed configs.

(cherry picked from commit e1dd1839)

Closes #726

(cherry picked from commit 26a8f686)

(cherry picked from commit 0f0a1959)

(cherry picked from commit bb2be712)

(cherry picked from commit f53146b3)

There are a few cases where the gateway code is eligible
to drop a gateway on grounds of being disabled, inactive,
unconfigured or where the actual interface assigned is
disabled.  This is undesire because users that configure
a gateway won't be able to use it.

There are no bad side effects from the former by selecting
a whatsoever dysfunctional gateway, because the problem still
has to be fixed by the user in the gateway setup itself.

Worst of all, removing a disabled but used gateway makes
it not show up on edit, effectively wiping its setting on
save.  This breaks POLA.

While there, also enable the null routes for IPv4 and IPv6.

PR: https://forum.opnsense.org/index.php?topic=2100
(cherry picked from commit 2db592b1)

(cherry picked from commit 7fb658c1)

(cherry picked from commit 27a4c795)

(cherry picked from commit 4c5a093b)

(cherry picked from commit c0d4c4be)

(cherry picked from commit a3b63565)

(cherry picked from commit 1aedcd49)

(cherry picked from commit 9910a79f)

(cherry picked from commit 551289a5)

(cherry picked from commit 32c774fb)

(cherry picked from commit d61fb7f9)