Messages

But still, the Deciso DEC697 uses a 256GB NVMe. Any one knows the brand and model ?

You can use nvmecontrol or smartctl to get that information. I don't own a DEC697 but a DEC750 (1st gen) and at work we run some older 6XX unit with a SATA SSD. From that small sample I can guess that Deciso likes to use Transcend SSDs.

I also recommend and use these as boot devices for e.g. TrueNAS. They are not the fastest but have really high TBW (write endurance) numbers even for the smaller ones. Nice industrial grade stuff.

In my DEC750 there's a TS256GMTE710T.

Kind regards,
Patrick

You could just for curiosity boot a stock FreeBSD 15.1. I'd expect that to show the same behaviour.

Since even in the mid term the only way with releases is forward - if you have a spare device or the budget for another one, by all means give it a try.

The update replaces FreeBSD 14.3 with FreeBSD 15.1. There might be some change in the NVMe subsystem that does not work quite well with your hardware.

So what is the exact error message, please?

Logfile angucken?

Was mir schon mal passiert ist, war, dass ich den AGH über das Webinterface aktualisiert hatte, ein späteres OPNsense Update dann wieder eine ältere Version installiert hat. AGH versioniert die Config-Datei ubd weigert sich, zu starten, wenn sie zu neu ist.

Ich hatte dann die Zeile mit der Version einfach aus der YAML entfernt, AGH gestartet, und dann nochmal übers UI aktualisiert.

sshd - secure shell daemon. That's what you mean? That's a service to remotely log in to a system from the command line.

"backup to the sshd"? Or is that a typo and you mean "backup to the ssd"? A backup on the same machine is not a backup. If the SSD fails - no backup.

So, yes, you can backup via SSH/SFTP to another machine. Which is one of the recommended ways.

I don't understand the question about the FS. There is really no reason to use anything but ZFS in 2026. Apart from very small embedded systems and/or VMs when the underlying VM storage is ZFS, already.

System > Configuration > Backups:



In System > Firmware > Plugins you will find additional backup destinations:

- git
- Google drive
- Nextcloud
- SFTP

HTH,
Patrick

It's because of OPNsense using RFC 5424 file format (IIRC). That's why e.g. Caddy has an option to log in traditional plain ASCII.

You can just invoke "top" and sort by CPU. FreeBSD top can do that. And lots of other things.

Use

Code Select Expand

pkg info -l wifi-firmware-ath12k-kmod-wcn7820_hw20

to see where the files are installed, then try to "kldload" them manually. They probably just do not end up in /boot/modules but somewhere under /usr/local.

But there is a periodic backup mechanism with various destination options in OPNsense, already. Standard, out of the box.

You were the one who started this mess by claiming Radia Perlman was using the term "forwarding" wrong. Well the entire networking world but you seems to use it like she does and I do. And I do not really understand your point. If you need to be precise, name the layer concerned.

If you did not make the effort to code it why should anyone make the effort to review it?

The caveat is essentially: don't mix policy based and VTI based connections. Pick one of them for all peers.

Well sorry about the feeling around the Free Tier BL. it's updated several time a day and shares back depending on what you share too.

OK, so maybe I misunderstood something.

I was referring to these:

https://app.crowdsec.net/blocklists?page=1&pricingTiers=%5B%22free%22%5D

Which are either available for free, anyway, without Crowdsec. Or essentially dead like Cruzit.

Any of the lists named "Crowdsec XY" are in the premium or platinum tier.

So do you say that a Crowdsec curated blocklist is always included, even in the free tier, without explicitly deploying it to a bouncer? That was not obvious to me from the documentation.

Thanks for taking the time to address issues.

Kind regards,
Patrick