Messages

Plan some time for a reinstallation with ZFS and a reasonably large EFI partition ;-)

First of all, thanks for all your help! Just a question for the future - do I understand you correctly that if the boot partition is 512K it would be a good idea to plan for a repartitioning followed by a reinstall at some convenient point in the future? I run ZFS and my gpart output looks like this:

Code Select Expand

# gpart show -l
=>       40  234441568  ada0  GPT  (112G)
         40     532480     1  efiboot0  (260M)
     532520       1024     2  gptboot0  (512K)
     533544        984        - free -  (492K)
     534528   16777216     3  swap0  (8.0G)
   17311744  217128960     4  zfs0  (104G)
  234440704        904        - free -  (452K)(I realise that the boot partition size is not a current issue but a theoretical future one.) I don't suppose there is a way to do a repartitioning in situ without a full reinstall?

No compilation required, it's just a script. Download it, chmod +x it and run it as root.

Doh! Thanks

So there is a general recommendation to keep your bootloader up-to-date, but I am not sure I understand how this utility achieves this. Am I to understand that there is updated code in one place on the disk but this has not been copied to the right place? My output from the utility is:

Code Select Expand

One or more efi partition(s) have been found.

Examining ada0p1...
Efi partition ada0p1 is already mounted in /boot/efi.
Would run: cp /boot/loader.efi /boot/efi/efi/freebsd/loader.efi
Would run: cp /boot/loader.efi /boot/efi/efi/boot/bootx64.efi

One or more freebsd-boot partition(s) have been found.
The root file system is zfs.

Examining ada0...
Would run: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 2 ada0

-------------------------------
Your current boot method is BIOS.
Updatable EFI loader: 2
Updatable BIOS loader: 1
-------------------------------

Hello! There is a small utility for checking the bootloader.

I have never compiled anything from scratch on my OPNsense system. How would I go about installing this utility?

find: /usr/local/lib/libicuio.qo: No such file or directory
find: /usr/local/share/man/man3/SSL_CTX_set_default_verify_dir,3ossl.gz: No such file or directory

That looks like typos in the script. "libicuio.qo" should be "libicuio.so", and "SSL_CTX_set_default_verify_dir,3ossl.gz" should be "SSL_CTX_set_default_verify_dir.3ossl.gz".

I tried an upgrade from 25.1.9_2 to 25.1.12. The system booted up but many of the services were not running. I had noticed before the reboot that the upgrade script seemed to be installing 25.1.11, not 25.1.12. Attempting to reboot left the system unresponsive and I had to pull the power to reboot. Since I use snapshots, I was able to get back to a working system on 25.1.9_2 but I will hold off on upgrades until 25.7 seems stable.

It seems if you are on older versions like my 25.1.9_2, the upgrade from the dashboard will not go straight for 25.1.12 and therefore the fix of partial upgrades will not be installed, leaving the system broken with 25.1.11.

When I upgraded from 23.1.7 to 23.1.9 a long time ago, my system started to show strong oscillations in CPU use, from 0 to 100, all the time. It would reach 100% about every 10 seconds or so. Because of the high average CPU, the temperature of the system went up by a couple of degrees. I have lived with this ever since because I couldn't isolate what was driving it.

After I upgraded from 25.1.7_2 to 25.1.7_4 and now 25.1.9_2, this oscillation has disappeared and now I am seeing a nice smooth line of CPU use (obviously subject to traffic volume). System temperatures are also lower.

Just thought I'd thank all the developers for continuous improvement - I have no idea which component makes the difference in my case, but this was a long-desired improvement.

Thanks gspannu, I got the beta installed and it's working much better.

I recently migrated from the "legacy" OpenVPN client configuration to the "instance" one.

I have an existing, working client setup under legacy that it would be nice to be able to migrate, but since the old one was set up with the help of the wizard and includes both the VPN setup, firewall rules and a dedicated interface, I am a bit daunted how to replicate the legacy client in the new Instances setup, without the wizard to guide me.

The documentation I found mentions two examples (site-to-site tunnel and road warrior) but neither fits my scenario. I just need to route traffic from a specific client on my LAN to a tunnel to my VPN provider.

Has anyone found improved documentation to guide them?

So the more files change the larger they get over time.

Thanks, but looking at my list the size goes 903M -> 3.67G -> 1.17G -> 804M in date order from 30/8 to 27/10. That doesn't constitute a constant increase. Is this because updates replace some larger files with smaller ones? I have not made any configuration changes of my own between these snapshots.

I have a series of snapshots going back to 24.7.1. Their sizes vary greatly, and I would like to understand why and if there is anything I can do to influence the size.

I use the AdGuardHome plugin. Normally, I update it via its web interface. At the moment, there is an issue that has been fixed in the latest edge release but not yet released as a stable release. I know that you can update the plugin using the command line and -u, but I assume that only looks for a new stable release. Is there any way to install instead a specific release like the edge release?

Having installed 24.7.2, I can confirm the issue is fixed by this update.

Unfortunately, the fix did not stick. Reporting was recorded for about two hours and then stopped. This is definitely an issue.

Thanks Franco for pointing to Github, great that it is logged.

I am having the same issue.  I was told to reset the RRD data in Report > Settings but that did not work for me.

Thanks for responding. I have reset my RRD data and so far (🤞) it is working. I will monitor and if it should stop collecting, I will post back here.

(I am running on a PCEngines APU2E4, as you can see from my signature. Very happy with the hardware.)

After I upgraded from 24.1.10_8, my Health reporting has stopped working. See screenshot – in this case, the reporting worked for a while after the reboot but then stopped. After the next reboot, the reporting did not even capture anything. This is true of all the reports – the States reporting is just one example.

Also, the end time in the chart (in this case 16:55) never updates – after you have called up the graph the first time, the time remains the same.

Any pointers welcome on ways to track down the issue.