Unbound and IPv6
-
Long time lurker and user here.
I've installed the 2.3 snapshot and am having some issues with unbound, which seem to be also present in 2.2.6, using IPv6 (Cox communications). Mainly, every time the WAN DHCP lease is renewed (although the IP does not change), Unbound stops and then attempts to restart, but fails due to a ports already in use issue. This only happens with IPv6 configured, and the error is IPv6 related :
php-fpm[7597]: /rc.newwanipv6: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1422151519] unbound[57995:0] error: bind: address already in use [1422151519] unbound[57995:0] fatal error: could not open ports'I do not have the local DHCP leases getting added to unbound, or anything like that. Any ideas ?
-
I suppose, then ,that PFSense with Unbound on IPv6 is simply not a good combination. In looking through the forums, it appears that this and similar issues have been around since 2.1.x, with no answer in any of the threads.
-
Unbound works just fine in combination with IPv6 and DHCP6 WANs. That log might just be log spam that something's trying to start it when it's already running, though maybe it's slow to die in your case for some reason. You end up with the service stopped under Status>Services?
-
@cmb:
Unbound works just fine in combination with IPv6 and DHCP6 WANs. That log might just be log spam that something's trying to start it when it's already running, though maybe it's slow to die in your case for some reason. You end up with the service stopped under Status>Services?
It does stop and has to be started manually.
-
I've uninstalled and reinstalled Pfsense on 3 different hardware versions, both 2.2.6 and 2.3 and get the same problem with IPv6.
-
I resorted to installing the Service Watchdog. At least it will keep my network running, until this bullshit with unbound gets sorted.