Turns out unbound reload flushes cache as well. Also, unbound-control
may hang when it runs into an "undefined state" (stoping a stopped
service, right), and lastly it wants to chroot after being chrooted
on reload, something that cannot be fixed with using unbound-control.
Keep unbound-control-setup in case somebody finds the facility useful.
IPFW and PF are used for more than just firewall and shaper, e.g.
NAT, policy routing or shaping, and the plugin framework supports
registering multiple user-facing services per file.
pkg can display to-be-deleted packages, but won't resolve these
issues when triggered using "upgrade -n". Thus, it's pointless
to try to keep this code until a newer pkg release can actually
cope with resolving the full upgrade cycle before upgrading.
This is the glue needed to be entirely plugin-agnostic, it only
needs new hooks for spots we haven't pluginified yet. The dns
subsystem is another likely candidate in the long run.
Allows to move these plugins away from core: bsnmpd, igmpproxy,
relayd, miniupnpd. ACL and menu entries pending...
It's difficult to say we can remove Relayd from base just yet.
Unbound and Dnsmasq sure are not going anywhere due to their
dependencies into DHCP. Relayd is similarly intermingled.
The amount of work required in the past two years for this
original pfSense 2.2 item has been immense. Still deleteing
unused functionality like the cache, "reload" not being
implemented, DHCPv6 static registration missing in action.
While there, dedup the dnsmasq static DHCP registration.
PR: https://github.com/opnsense/core/issues/1250
PR: https://github.com/opnsense/core/issues/624
exception 'Exception' with message 'Error at /usr/local/opnsense/mvc/app/library/OPNsense/Auth/LDAP.php:236 - ldap_bind(): Unable to bind to server: Invalid credentials (errno=2)' in /usr/local/opnsense/mvc/app/controllers/OPNsense/Base/ApiControllerBase.php:84
Stack trace:
0 [internal function]: OPNsense\Base\ApiControllerBase->APIErrorHandler(2,
