Messages

Hey @cookiemonster many thanks for taking the time to respond I saw that the credentials files were different on the OPNSense old vs new. I will take a look at the docs but I think you might be right and I have to manually re-register all of the network agents! PITA!

For other benefits I will post back here the solution.

Cheers

Really, no one has experienced this.


When I bring up the new 25.7 instance and import the backed up config. The Crowdsec config looks exactly the same as the old OPNSense system. But the network devices that are running and reporting via the new LAPI connection are not there anymore and are not reported.

Checking on the command line, the network machines don't exist.

I am moving over to a new machine. Setup OOtB then install all of the plugins from my old installation as importing the config does not install them automatically.

Once rebooted the crowdsec configuration does not seem to work as none of my network crowdsec agents can connect to the opnsense crowdsec lapi.

The setup config seems to have come across fine all of the options are configured exactly as my old opnsense installation.

I really don't want to have to manually go around all of the network servers with the crowdsec agent running and start again.

Are there some crowdsec config files I have to manually bring across from the old installation.

Any help appreciated.

Just an update on this after much F***ing about.

I installed a stock freebsd 14.3 system with the mods described above to enable the mrsas driver. Once installed, I then installed the latest 25.7 using the following commands:

# fetch https://raw.githubusercontent.com/opnsense/update/master/src/bootstrap/opnsense-bootstrap.sh.in
# sh ./opnsense-bootstrap.sh.in -r 25.7

This went perfectly and resulted in a working OPNSense 25.7 installation.

A lot of work but ultimately I got there in the end!

Cedrick,

If teh bootstrap essentially installs OPNSense on top of a stock 14.3 release. What is going on with the 25.7 installer?

Clearly there are some differences as the stock 14.3 installer works fine in both UFS and ZFS modes.


I also tested 25.7 install on the IDSDM Dual SD card module. And that worked fine. Reduced the power from 42W to 28 Watts also.

FreeBSD 14.3 installs fine with the above hack to force using the mrsas driver.

However, OPNSense 25.7 does not install using the same hack. Tried both UFS and ZFS installs.

Ideas anyone?

So your suggestion would be to download the FreeBSD 14.3 installer iso and install that to the target drive?

We can do that. Will report back.

Cheers
I did find this, but it seems to relate to RAid mode operationof the H730 mine is configured as HBA no raid mode so is just passing the drives through.

You may experience installation issues with FreeBSD 14.3 on a Dell R330 with a PERC H730 due to incorrect driver loading. The operating system may default to the mfi(4) driver, which is incompatible with the H730 and can cause kernel panics or data corruption, especially when using ZFS. The correct driver is mrsas(4).
Fix the H730 driver issue
Stop at the boot loader prompt. When the system boots from the installation media, press a key to enter the boot menu. For FreeBSD, this is typically Escape or a different key indicated on the screen.
Add the correct driver hint. At the boot loader prompt, enter the following command to force the system to use the correct mrsas driver for the H730 controller:
sh
set hw.mfi.mrsas_enable=1
Continue booting the installer. Type boot and press Enter to proceed with the FreeBSD installation.

Well thanks for the thoughts on this.

Have checked out the server with Win Server and Ubuntu installs to the same drive.

No issues.

Will keep working on it. Maybe someone from the release team will respond with ideas.

Cheers

@pfry - Thank you for responding. But the installer gets to 100% creates the partitions on the drive etc. Seems to write to the drive during install but cannot complete.

Where would this config go. We are installing from the iso full installer. Which is a live system then logging in as installer/opnsense and then following the prompts.

Installer gets to 100% after creating file systems then when the file explorer window appears with the Exit at the bottom. Pressing Exit results in an installer error dialog.

Pressing continue show errors reading the directories creating during install.

Can't get past this stage. Tried reformatting the HDD and creating a clean partition table. Then installing again with the same results.

System is a Dell R330 with a 730 Raid controller. Configured as non raid mode.

Runs linux and windows OS fine on the same HDD.

Any help appreciated.

Many thanks.

Your workaround worked using Archive Manager. I also managed to extract it using 7z on the command line. But not via Gui.

Cheers

Yes checked the shasum. This was via my Ubuntu 24.04 desktop.

Cheers

Tried downloading the latest DVD ISO from a few mirrors. Once downloaded I cannot get it to extract the ISO.

See attached image.

Does anyone else have this issue?

Cheers

Any further thoughts?

Yes exactly like the VLAN 50 setup on the HP Switch. If I plug into port 11 or 12 I get a correct lease in the VLAN50 network. If I plug into port 9 I get no lease. 

Inside ESXI the Vswitch has a PG for the OPNSense LAN connection and another PG for VLAN 30 which has the OPNSense Guest network connected 10.0.30.0/24 providing DHCP and DNS and also a test VM connected. The test VM gets a correct lease in the Guest network VLAN30.

I also configured a new wifi network on VLAN30 and that also cannot provide leases to connected devices.

Confused! The only thing I can think is that the OPNSense LAN PG is operating in VGT mode VLANID4095 and the new PG for VLAN 30 is operating in VST mode VLANID 30.