Hello,
Just got OPNsense installed as a transparent filter bridge today. The bridge/firewall is working fine. All clients/devices have internet access being processed thru OPNsense.
The only issue I have and have been working on this most of the day is when I try to do a package update.I get the following error: Could not find the repository on the selected mirror.
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 25.7 (amd64) at Tue Oct 14 20:56:57 EDT 2025
Fetching changelog information, please wait... fetch: https://pkg.opnsense.org/FreeBSD:14:amd64/25.7/sets/changelog.txz: Network is unreachable
Updating OPNsense repository catalogue...
pkg: http://mirror.venturasystems.tech/opnsense/FreeBSD:14:amd64/25.7/latest/meta.txz: Network is unreachable
repository OPNsense has no meta file, using default settings
pkg: http://mirror.venturasystems.tech/opnsense/FreeBSD:14:amd64/25.7/latest/packagesite.pkg: Network is unreachable
pkg: http://mirror.venturasystems.tech/opnsense/FreeBSD:14:amd64/25.7/latest/packagesite.txz: Network is unreachable
Unable to update repository OPNsense
Error updating repositories!
pkg: Repository OPNsense cannot be opened. 'pkg update' required
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***
I think this maybe a DNS issue. I am using my modem/router IP for the DNS. I also tried Cloudflare and Google. Same results.
I have a gateway setup for my MGMT interface that I'm using to get the updates. I found some 'fixes' by googling the error but none have fixed the issue for me. I also ran 'pkg update' from the shell.
I have another instance of OPNsense running as a VM and have no problems getting the updates.
Any help would be greatly appreciated.
Thanks
EDIT: when I run the diagnostic tool for DNS Look up, it responds:
Response
Type Answer Server Query time
AAAA pkg.opnsense.org. 644 IN AAAA 2001:1af8:5300:a010:1::1 192.168.1.1 30 msec
From my end http://mirror.venturasystems.tech is working. And "Network is unreachable" is not a DNS error IMO. Could be a routing issue.
Cheers,
Franco
Thanks,
I was thinking also it may be a firewall rule. The MGMT interface is on the same subnet as my local network. I set up a gateway for it and made FW rules for HTTP, HTTPS and SSH. I just made a Allow All Out rules, now I'm getting a different response: Could not find the repository on the selected mirror.
I've got something hosed up and I'm running out of ideas.
Thanks