Messages

Hello Franco
I just ran the opnsense-bootstrap script to upgrade to version 24.7, and everything went well. I'm now on version 24.7.12-4 and therefore able to upgrade to version 25.
Thank you very much for your help.

Hello everyone

I'm once again having an update problem on one of my many Opnsense firewalls. This time, the firewall is in version 24.1.10_8, which normally corresponds to a version of Freebsd 13. But the problem is that my system is already running Freebsd 14.

root@parefeu21:~ # opnsense-version
OPNsense 24.1.10_8
root@parefeu21:~ # uname -r
14.1-RELEASE-p3

When updating from the graphical interface, it fails because at one point it tries to look for the next file, which doesn't exist due to this difference between the Opnsense and Freebsd versions.

Fetching base-24.1.8-amd64.txz: ..[fetch2: https://pkg.opnsense.org/FreeBSD:13:amd64/24.7/sets/base-24.1.8-amd64.txz.sig: Not Found] failed, no signature found

The correct path should be this: https://pkg.opnsense.org/FreeBSD:14:amd64/24.7/sets/base-24.7.12-amd64.txz.sig

What should I do in this case?
Is it possible to downgrade from Freebsd 14 to Freebsd 13 to perform this update?
Or should I use the opnsense-bootstrap script?

Thanks for your good ideas.

I forced it by setting the correct path to the repository in setting mirrors

But when I return to the status, the path is invalid.
it displays
Mirror https://pkg.opnsense.org/FreeBSD:13:amd64/22.1//FreeBSD:12:amd64/21.7

I can't test with another mirror because for the update, I use a Squid proxy that only whitelists certain sites, including pkg.opnsense.org.

I need to be able to modify the path to the mirror correctly. Is this possible from the command line?

Hello everyone,
I'm trying to update an older version of Opnsense, currently 21.7.8, but I'm having trouble.
I noticed that my FreeBSD system is on version 13, when it should be on version 12 with Opnsense 21.

root@pf:~ # opnsense-version
OPNsense 21.7.8 (amd64/OpenSSL)

root@pf:~ # uname -r
13.0-STABLE

When I run an update with the opnsense-update tool, I get the following message:
root@pf:~ # opnsense-update -p  -A 22.1
Updating OPNsense repository catalogue...
pkg-static: https://pkg.opnsense.org/FreeBSD:12:amd64/22.1/latest/meta.txz: Not Found
repository OPNsense has no meta file, using default settings
pkg-static: https://pkg.opnsense.org/FreeBSD:12:amd64/22.1/latest/packagesite.txz: Not Found
Unable to update repository OPNsense
Error updating repositories!

How can I successfully update to version 22.1 and then to future versions?

Thank you.

Hello everyone,
A quick clarification regarding my first message. Safesearch works very well with other search engines like Google; the results of a search for adult content are not displayed. This is important because the internet access concerns schools. However, for Qwant, the results are displayed including images, which is problematic. Of course, the sites are blocked, but I also want to hide the search results. In the source code core/src/opnsense/service/templates/OPNsense/Unbound/core/safesearch.conf
the content is as follows:
# Qwant
local-zone: "qwant.com" redirect
local-data: "qwant.com CNAME safeapi.qwant.com"

How can I redirect the Qwant site to benefit from safesearch protection?
Perhaps https://www.qwantjunior.com/?

Thanks for your suggestions.

Hello, I've enabled Safe Search in Opnsense, and I'm having a problem with the Qwant search engine. In the config file, Qwant is redirected to safeapi.qwant.com, but it no longer exists. How do I enable Safe Search with the Qwant.com search engine?
Thank you.

Hi,
thank you for the answer

It bothers me to have to restart a complete installation because I have a dozen virtual machines under vmware with opnsense and I can't see myself reinstalling from the beginning

I get the following message when I update a firewall to version 21.7 and it tells me that everything is up to date
I have a timeout with the fetch command

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 21.7.8 (amd64/OpenSSL) at Fri Nov 24 17:12:37 CET 2023
Fetching changelog information, please wait... fetch: transfer timed out
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.txz: .......... done
Processing entries: .......... done
OPNsense repository update completed. 777 packages processed.
All repositories are up to date.
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking for upgrades (0 candidates): . done
Processing candidates (0 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***

An idea ?

Best regards

Good morning,

I am having difficulty updating opnsense through a squid proxy
I am in version 21.7 and I managed to update my server to version 21.7.8 via my squid proxy. The proxy connection string is entered in the /usr/local/etc/pkg.conf file.
pkg_env: {
http_proxy: "http://your-poxy-ip:port/"
}

I can only use the pkg.opnsense,org repository, it is the only one that is authorized on the proxy
However, I cannot upgrade to version 22.1, it tells me that I am up to date whether I launch an update via the graphical interface or via the pkg command on the command line

Has anyone ever encountered this problem?

Best Regards

Thierry