Quote from: franco on October 24, 2025, 08:58:46 AMYou still don't know if it's trying to connect via IPv4 or IPv6 and disabling non-working IPv6 or preferring IPv4 via setting have always been good options.
Cheers,
Franco
True, I failed to mention that I disabled dhcp6 on my wan interface and even clicked to disable ipv6 to try to narrow things down. My thoughts on that was when I set this instance up, I had it on my lan (ipv4 only) behind an older opnsense (21) instance and it updated just fine. It stopped updating once I replaced the 21 instance with this one. And the obvious difference was the ipv6 interface. So that's where I began troubleshooting the update errors.
In troubleshooting mbuf errors that were showing up in dmesg, I disabled the following.
* hardware checksum offload
* hardware TCP segmentation offload
* hardware large receive offload
Once disabling those I didn't get any further messages appearing in dmesg or on the console. Plus an added bonus that updates work again... :). Kinda weird that would be enough to do it.
Code Select
root@repulse:~ # pkg update
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
root@repulse:~ #
After all of thie I've re-enabled ipv6, and I don't get errors when trying to update.
"