Topics

The new services widget in 26.7.2 looks great. Thank you OPNsense team for iterating the design.

The new services widget is really good. One minor suggestion: please add a "Services" text header and an orange line to the top of the widget so that it matches every other widget.

After updating to 26.1.3, I see the following errors when I check for updates:

pkg: glib-bootstrap has a missing dependency: python311
pkg: glib has a missing dependency: python311

Everything is working correctly but I am not using IPS/IDS.

I completed a test rules migration with 26.1 in a VM. I clicked to remove all rules in the legacy interface. I thought the old Rules interface would disappear, but it continues to coexist with Rules [new]. I rebooted the router but both are still there. Is that the expected behavior?

Thank you devs for the hard work that went into 26.1! It's going to be a great release and I am especially looking forward to the new rules interface. I have some feedback to share based on my initial testing of the rules migration. Please take my comments in the helpful spirit I intend:

• Anti-lockout instruction clarity: The instruction text says "enable the anti-lockout rule" while step 2 says "Deselect anti-lockout in advanced settings." Given the wording of the control itself ("Disable anti-lockout"), I suggest revising the instruction text to: "To prevent being locked out during the rule migration process, enable automatically generated lock-out rules..." and updating step 2 to: "Uncheck the 'Disable anti-lockout' checkbox."
• Import rules dialog: The dialog would be clearer with an explicit "Import" button instead of relying on the checkbox. On first use, I wasn't sure what to click to initiate the import—I expected the checkbox to validate the file and then present a button to execute the import.
  
• Destination field validation: The firewall rules in my test VM are the default LAN rules (allow LAN to any, v4 and v6). The import validation failed with "[destination_net] A value is required." The rules export should automatically populate "any" for the destination_net field in these cases. If this behavior is by design, the error message should clarify whether to enter "any" or "*" to resolve it. (I used "any" and the import succeeded.)
  
• Import completion feedback: No confirmation is displayed when the import completes—the dialog simply disappears. In my test case with no floating rules, the dialog closed with no visible indication of success because the default view is floating rules and I didn't import any (i.e., it looks like nothing happened). Suggest adding a confirmation dialog: "X rule(s) successfully imported. Select the interface dropdown to view imported rules for each interface."
  
• Typo: "Now we can import the exsiting rules..." → "existing"
  

I am trying to monitor the status of my WAN gateway using Uptime Kuma and the OPNsense API. Despite my best efforts and google skills, I cannot get it to work and would appreciate any help. The monitor is showing red/down continually and there are no errors in the Uptime Kuma messages area. I am pretty sure it is an error in the way I am configuring Uptime Kuma. Here's what I have done:

1) Setup a new user, with access to the Gateways and generated the key/secret
2) Used CURL -k -u "<key>":"<secret>" https://myIP/api/routes/gateway/status from the Uptime Kuma console and I get the expected response
3) Configured Uptime Kuma as follows:

• Monitor type = HTTP(s)-Json Query and the URL is the same as in step #2
• Json Query expression and associated fields are set to $.status == ok
• Method is GET, body encoding is JSON and body/header fields are blank
• Authentication is set to basic auth and I put the key/secret into the username/password fields

I've tried various combinations of putting the authorization into the header/body, encoding the key/secret into base64, checking/unchecking the "ignore TLS/SSL errors". I'm probably just not using the right combination of things.

My Acme automation to Proxmox completes successfully but Proxmox still uses the old certificate. I've tried rebooting Proxmox and the debug.2 log shows the automation completes successfully. I know Acme is updating the certs because I can manually upload them to Proxmox, and the new certs are applied. Is the Acme Proxmox automation working for anyone? I am running OPNsense 25.1 but I noticed this issue with 24.7.12 too.

I updated from dev RC2 to the release (switched to the community channel). No problems with the update and everything seems to be working fine. Thanks OPNsense team for continuing to delight your users.

The latest version of Graylog now includes support for OPNsense log parsing. No need to maintain custom code for parsing and best of all it is available in the Open community version: https://go2docs.graylog.org/illuminate-current/what_is_illuminate/graylog_illuminate.html

The only downside I've found is that it is labeled as "pfsense"  :)

Upgraded from 24.1.10 on bare metal with IPv4 only. Upgrade took a little longer than usual (probably the OS upgrade), but be patient and it will finish. New widgets are running happily. AdGuard, Acme, DDNS, Nut and mDNS all seem to be working correctly.

Thanks OPNsense team for the awesome new release!

Just updated Protectli FW4B to 24.1 from 23.7.12_5 using the GUI. I run some VPNs, Acme, AdGuard, DDNS, MDNS, Unbound, and ISC DHCP. Everything is running great. Thanks Devs for keeping OPNsense awesome!

Thank you for the awesome new release! I upgraded without problem and added a new DDNS using Cloudflare API token (new feature in DDClient 3.10). The logs show that DDNS is being updated without error. However, the IP and Updated columns of the UI remain blank (see attachment).

Keep up the great work.

I have some firewall rules that have logging enabled. I can see the rules triggered in the live view and in plain view (Informational priority), but nothing shows up in Firewall->Log Files->General. I've tried all of the priority levels and turning logging off/on. I am on v22.7.4. The documentation (https://docs.opnsense.org/manual/logging_firewall.html#live-view) covers the live and plain views, but says nothing about the general view. Are firewall logs supposed to be displayed in the general view or it is for something else?

juls