pfSense

Before starting Unbound during boot there's a ~10s wait (found in services_unbound_configure()) for any interface assigned to wan to finish its DHCP6 client configuration. Presumably this helps to mitigate issues when Unbound is bound specifically to a DHCP6 WAN interface, though it's not clear to me exactly what those issues may be. This timer doesn't take into account that the relevant interface may be assigned a different identity, or that there may be multiple DHCP6 WANs. Refactor this timer so that all WAN interfaces are checked.