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.
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
o consolidate "unbound_" prefix for unbound.inc for pluginification
o services.inc includes unbound.inc rightfully, a bit like a
plugin would do in the future, but this also means we can
zap all requires from top pages, which are entirely spurious.
o get_dns_servers() moves to system.inc because it is used by
status_interfaces.php
o RIP read_hosts()
According to manuals and other project's code this should work as
expected, but to make sure we just advertise the name without a
default.
While there, clean up the config file generation and a few printf
bits that really shouldn't be in there.
PR: https://github.com/opnsense/core/issues/1250
