opnsense not updating - DNS problems

[kabutosan]

Hi there!

This is driving me crazy... my opnsense works great, and DNS seems to be working great for all clients connected, but it isn't updating. It seems opnsense isn't able to resolve hostnames and getting updates. FW rules seem ok; unbound service is up and running and resolved.conf correct. Any hints?

cat /etc/resolv.conf
domain localdomain
nameserver 127.0.0.1
nameserver 8.8.8.8
nameserver 8.8.4.4
search localdomain

[phoenix]

What errors are you seeing when you try the update? Have you also tried changing the mirror on System: Firmware/Settings page - see if that makes any difference?

Do you get any valid response if you 'ping host' from the OPNsense konsole?

[kabutosan]

This is what I see:

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 23.7.11 at Sat Jan 20 14:08:20 EST 2024
Fetching changelog information, please wait... fetch: transfer timed out
Updating OPNsense repository catalogue...
Waiting for another process to update repository OPNsense

I tried to change repo... same result. 

Thanks!

[kabutosan]

This is the full output.

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 23.7.11 at Sat Jan 20 14:08:20 EST 2024
Fetching changelog information, please wait... fetch: transfer timed out
Updating OPNsense repository catalogue...
Waiting for another process to update repository OPNsense
All repositories are up to date.
pkg: Repository OPNsense cannot be opened. 'pkg update' required
Checking integrity... done (0 conflicting)
Your packages are up to date.
pkg: Repository OPNsense missing. 'pkg update' required
self: No packages available to install matching 'opnsense'
***DONE***

If I try to update manually, I receive a time-out error after a while, so It seems DNS-related.. but I am not 100% sure.

pkg update
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/23.7/latest/meta.txz: Unknown resolver error
repository OPNsense has no meta file, using default settings

[kabutosan]

Problem solved! It was related to the Hardware CRC that was ON. I will dig into the settings and logs to better understand the relation between the DNS lookup and this setting.

Thanks!