Messages

Thanks for the push in the right direction Franco.  I'd looked at using the custom flavour option but couldn't fully understand what was expected.  I've now found what to put here for it to work correct.

Is there any room to contribute to documentation for these types of subjects, to make them a bit easier to understand for others in the community?  I'd be more than happy to contribute, I'm just not sure how to contribute.

Ashley

Hi Patrick,

Thanks for your reply. My interest in being able to do this is to control what release is used in my environment at any given time. The environment doesn't always allow the current release to be installed a couple days after release on the test cluster, and then on the production cluster prior to the next release date. It would simply be more convenient to be able to say "I want to freeze the release at some date/version so that both environments can be synchronized in relation to the other constraints that exist.

Does that make the "need" clearer?

Hi,

I've been enjoying using OPNsense but now have more and more to manage.  We have 2 HA clusters setup to allow for testing on one cluster before updating the main cluster.  My question is, is there a way for force the update to a specific version and not just the latest version?  I've been digging around here and all over the internet, and have been trying some testing using opnsense-update using the -r option, but have not found the solution yet.

For example, I currently have version 23.7.10 installed and would like to upgrade the first cluster to 24.1.2, wait a certain amount of time, then complete the same upgrade path on the main cluster.  Would this be possible?

Thanks!

Hi,

I'm having a strange problem which I've only just noticed.  When I modify the Squid configuration on my primary node and perform an xmlrpc sync to the secondary node, the Squid configuration is not automatically reconfigured/reloaded.  I need to connect to the secondary node and manually reconfigure/reload the Squid configuration for the synchronized changes to be taken into account.  Is this normal behaviour?  I can't remember ever having to do this before, but I'm also not 100% sure that this hasn't been a problem in the past as I don't modify the Squid configuration very often.

Thanks for any insight!

Hello,

It appears that the OPNsense squid configuration templates need to be updated for the change in language file paths with the update to 23.7.8 when using Squid error pages.  The template configures Squid to look for the error pages under /usr/local/share/squid-langpack/en-us which doesn't exist.  The actual path is /usr/local/share/squid-langpack/en.

This error unfortunately causes Squid to fail to start.  A workaround is to select the OPNsense error pages instead.

I'm not sure who would be responsible for adapting the template configuration following a modification by Squid package maintainers.

Thanks,

Ashley

Hi,

Ok, thanks for the information.  It's good to know that in the link provided they provide a link to the Squid langpack download.  For those wishing to find this link a bit faster, the link provided for the langpack is http://www.squid-cache.org/Versions/langpack/.

Ashley

Hi again,

I just looked at the github link and it does seem as though all localization files and symlinks were deleted from the pkg-plist...  The problem is likely with the squid package and its maintainers.

Ashley

Hi,

I'm using the Squid error pages on both firewalls.  I did try switching to the OPNsense error pages and reinstalling the package, both actions didn't make any changes.

When I looked in the /usr/local/etc/squid/errors directory, only the COPYRIGHT and TRANSLATORS files existed, plus the local and templates directories.  All of the other localization directories and symlinks were gone.

Ashley

Hello,

I've noticed while applying OpnSense upgrades yesterday and today that the Squid update from 5.7 to 5.8 on the two OpnSense firewalls that I've upgraded causes the error pages to disappear.  The Squid service then refuses to start.  As a workarround, I've simply copied the errors directory from another OpnSense firewall, which allows the Squid service to start correctly.  I'm uncertain why the error pages seem to be deleted during the update, but this could be painful for those that do not have another firewall available.

Ashley Smith