24.7.10_2 name resolution? rsync issue

[andyrtr]

After the 24.7.10 update a local rsync cron job fails with the time limit of 60sec. - removing the time limit allows it to work but the initial rsync directory synchronisation starts not before more than 2 minutes. Reverting to my fallback OPNsense device made it instantly sync again - moving again to 24.7.10 kept working it but after another 24.7.10 device reboot it's broken (or slow) again. Casual browsing seems to work well though for other devices.

Any idea where to look for specific logs or a bug?

[andyrtr]

There seem to some serious DNS issue traceroute -4 works well but traceroute -6 fails for all addresses.

[andyrtr]

My fallback device runs OPNsense 24.7.7 passing all test at https://test-ipv6.com/ and https://www.dein-ip-check.de/ipv6test where 24.7.10 fails. Command "traceroute -6 google.com" also works on the fallback device.

I've compared the backup xml files and cannot find any related difference. So I guess it's a bug in 24.7.10 failing IPv6 connections/DNS issue. The gateway monitoring in the current release shows the WAN_DHCP6 interface up with no issue.

[Patrick M. Hausen]

I have a handful of systems all running 24.7.10_2 and no IPv6 issues whatsoever.

You need to be way more specific about your setup and the failure you observe.

[andyrtr]

The box connects to a cable modem. It's a Zotac Zbox CI329 running Realtek NICs using the vendor driver (do I need to reinstall this after the kernel update?). The configuration is the out of the box default setup. I've added my local clients to get static IPs from DHCP4 and use unbound with DNSSEC enabled with a few filter list.

[andyrtr]

A cable modem reboot solved the issues here. No idea why the fallback device kept working. Sorry for noise.