Messages

1. Install on ZFS
2. Update ( do a minimal configuration to have internet access, it will be temporary)
3. Import configuration - machine will reboot
4. Check for updates - all official plugins will be reinstalled
   If using third party plugins you will need to add the repo manually and also the configuration file if you have it
5. One more reboot for everything to start properly

For ZA do your own research, I'm not using it.

Reinstall was surprisingly smooth from usb drive. Installed 26.7 with ZFS file system. Nearly all configuration was restored/imported correctly (including Qfeed etc) and plugins were installed again. Update to 26.7.5 went through.
Only thing missing is ZA.

Please simply boot a Linux or *BSD Live ISO from your favorite USB Stick and use 'smartctl -a /dev/<whatever>' to see the full S.M.A.R.T. output and post it here so we can double check for you before you reinstall :)

I connected the Samsung Pro 830 SSD to my main pc and checked it with Samsung Magician, it says drive is OK, so I will reinstall on this drive.

SMART is status OK (from within BMC/UEFI).
I have password protected config backup with me.
Already downloading usb install image.

Where is a good reinstalltion guide documented?
And what kind of configurations are perhaps not backed up by the GUI backup feature?

Unfortunately it is a very old installation which stated at OpnSense 19.x times without ZFS and was never reinstalled since, only upgraded.
All upgrades went smoothly since 7 years.

Any other options without ZFS?

I waited now for 45 Minutes and still the same line.

Configuring loopback interface .. 1o0: link state changed to UP
done.
Configuring kernel modules ... amdsmn0: <AMD Family 19h System Management Network> on hostb0
amdtemp0: <AMD Family 19h CPU On-Die Thermal Sensors> on hostb0
done
Setting up extended sysctls ... done.
Setting timezone: Europe/Berlin
Writing firmware settings:sh: opnsense-version: not found
Mirror ABI cannot be a subdirectory
OPNsense SunnyValley
Writing trust files. .. done.
sh: /usr/local/opnsense/scripts/system/certctl py: not found
Writing trust bundles ... done.
Setting hostname: OPNsense. ramses. internal
Generating /etc/resolv. conf ... done.
Generating /etc/hosts. . .done
Configuring system logging ... done
Configuring firewall . load_dn_sched dn_sched FIFO loaded
load_dn_sched dn_sched QFQ loaded
load_dn_sched dn_sched RR loaded
load_dn_sched dn_sched WF2Q+ loaded
load_dn_sched dn_sched PRIO loaded
load_dn_sched dn_sched FQ_CODEL loaded
load_dn_sched dn_sched FQ_PIE loaded
load_dn_aqm dn_aqm CODEL loaded
load_dn_aqm dn_aqm PIE loaded
ipfw2 (+ipv6) initialized, divert loadable, nat loadable, default to accept, logging disabled
igb3: link state changed to UP
.


On the first reboot attempt it stopped 1 line earlier at ipfw2 line and then just a "dot"

I upgraded my OpnSense from latest 26.7.4_x to 26.7.5.
After couple of minutes after 26.7.5 upgrade it went unresponsive.
I rebooted with ctrl+alt+del, but now it hangs every time on following screen.
Second time soft rebooting same result.

Physical machine
AMD Ryzen 5700X with 16cores
ASRockRack X470D4U2-2T mainboard
32gb ram
2port Intel x550 (onboard)
4port Intel X710-T4L
4port Intel i350-T4 v2
256gb ssd

Hi,

I upgraded today from 2026.1.11_10 to 26.7
Since the upgrade my WireGuard setup connecting my home OpnSense with my Azure OpnSense does not come up again.

In error log of WireGuard there is following new entry:

2026-07-16T18:31:17Errorwireguard/usr/local/opnsense/scripts/wireguard/wg-service-control.php: The command </usr/bin/wg syncconf 'wg0' '/usr/local/etc/wireguard/wg0.conf'> returned exit code 1 and the output was "Name does not resolve: `xxxxxxxx.spdns.org:51820' Configuration parsing error"

I tried to recreate the entry but still get this error.

I changed my Azure B2s_v2 to an D2s_v5 and enabled Accelerated Networking. But even after several reboots i still see VLAN_HWCSUM, VXLAN_HWCSUM and VXLAN_HWTSO on the hn1 device 😭

[ifconfig hn1]

Hi all,

I am running OPNsense 26.1.6 on an Azure VM and I am trying to use Zenarmor.
However, the Zenarmor engine stops shortly after startup with this error:

netmap_register_if: hn1: failed to disable offloads for interface

I already disabled the usual hardware offloading options under System > Settings > Networking and also enabled interface-level hardware override on the LAN interface.
The following options are disabled:

Disable hardware checksum offload

Disable hardware TCP segmentation offload

Disable hardware large receive offload

Disable VLAN hardware filtering

I rebooted the firewall after applying the changes.
I also tested both native and emulated netmap modes in Zenarmor, but the result is the same.

The problem is that ifconfig hn1 still shows offload-related capabilities after reboot, including:

VLAN_HWCSUM, VXLAN_HWCSUM, VXLAN_HWTSO

MTU is 1500, so that does not seem to be the issue.

My question is:
Has anyone successfully run Zenarmor on OPNsense inside an Azure VM / Hyper-V hn interface and found a way to fully disable the remaining offloads so that netmap can start correctly?

I would especially like to know:

• whether there is an additional OPNsense tunable or loader/sysctl setting required for hn interfaces
• whether this is a limitation of the Azure/Hyper-V network driver
• whether anyone has a working Azure VM configuration for Zenarmor with hn interfaces

Any advice or working example would be greatly appreciated.

Thanks!

I understand I should configure at least the two allow rules to divert traffic to suricata but what happens with the block rule? I do nothing?

If it is already blocked by the FW rule, it does not need to be diverted further.

Did you solve it?

Thank you for the hint 👍

I have the same issue after. (pppoe)

Hallo zusammen,

Ich habe an meiner OPNsense 22.1.4 insgesamt 3 WAN angeschlossen. 1x Starlink direkt für Hauptlast ohne den Atarlink Router. 1x 6MBit ADSL2+ Telekom PPPoE an Drytek Vigor 165. 1x 5-15MBit LTE per Mikrotik LTE Modem.

IPv6 und PPPoE laufen ja derzeit unter 22.x nicht so rund, außerdem habe ich mit PPPoE ein zusätzliches Problem dass seit Providerwechsel/Neueinrichten des PPPoE Device mein PPPoE Log nicht mehr angezeigt wird.

Man liest oft das man die PPPoE Einwahl und das setzen der VLAN ID 7 unbedingt durch die OPNsense machen lassen soll für "stabileren Betrieb". Aber eben auch ab und zu Beiträge das einige doch das Modem einwählen lassen und es funktioniert.

Ein Vorteil von OPNsense PPPoE und VLAN ID 7 ist, dass nur 1 Kabel zum Vigor benötigt wird um trotzdem auf dei Oberfläche zugreifen zu können.
Ein Nachteil von obiger Konfiguration ist (temporär) die derzeitigen Probleme bei IPv6 over PPPoE.

Was sind weitere Vorteile und Nachteile wenn ich OPNsense PPPoE/VLAN ID überlasse vs. Vigor 165 Modem einwählen lasse und die IPv4/IPv6 direkt am WAN Port anliegen habe.

Grüße

Manuel

Problem still persists even after four days and two reboots.