IPV6 broken since update, unbound stops

Started by dominick-cc, April 14, 2024, 05:53:26 PM

Previous topic - Next topic
April 14, 2024, 05:53:26 PM Last Edit: April 14, 2024, 06:00:37 PM by dominick-cc
Hi all,

I recently upgraded from an N5105 topton box to an N100 router by the same manufacturer. I loaded the config I backed up from the old router to the new. Additionally, I also setup Opnsense with ZFS on the new router (previously it wasn't). Prior to this I was running 23.x on my N5105 box -- so now I'm on 24.1.5_3:

OPNsense 24.1.5_3-amd64
FreeBSD 13.2-RELEASE-p11
OpenSSL 3.0.13

The internet mostly works, but something is broken with IPV6 -- and unbound seems to be breaking if I leave it for a while. I can see it not capturing any data in the reporting output. Restarting the unbound service resolves it -- but why does this happen?

On boot, pretty reliably I see the following 4 errors/warnings:

2024-04-14T11:43:45-04:00 Error opnsense /usr/local/etc/rc.newwanip: The command '/usr/local/sbin/ntpd -g -c '/var/etc/ntpd.conf'' returned exit code '1', the output was ''
2024-04-14T11:43:38-04:00 Error dhcp6c transmit failed: Can't assign requested address
2024-04-14T11:43:37-04:00 Error opnsense /usr/local/etc/rc.bootup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-14T11:43:37-04:00 Warning opnsense /usr/local/etc/rc.bootup: dhcpd_radvd_configure(auto) found no suitable IPv6 address on lan(igc1)


So I'm having this issue: https://forum.opnsense.org/index.php?topic=39469.0

But I also have some other issue with IPV6 "found no suitable IPv6 address on lan" that I'm not sure how to resolve.

To add to the confusion, some clients on my networks (android phones) can't load some websites (like llbean.com). But they load fine on my Windows machine on the same network.

Any ideas? I changes a lot of variables all at once by doing this hardware upgrade, with the new version of Opnsense. So I'm not sure where to begin.

Flaky IPv6? The reboot may have triggered it and not the update.

I think I also missed a mute on the Unbound "error" message.

https://github.com/opnsense/core/commit/1afe0405bc


Cheers,
Franco