Recent posts

#1
Quote from: oldRaven on November 08, 2026, 02:37:26 PMI will be installing OPNsense on the XGS 126 in the next two weeks.  I will give you feedback soon.  Looking forward to testing.

Sounds good, looking forward to hearing how it goes.

One owner already runs a 126 with it, and that report covers every front port, flows in hardware and updates from the XGS menu (XGS 126 page). What no 126 owner has confirmed yet is F1 and F2 (SFP ports), PoE on ports 11 and 12, and fans. If you get to any of those, that's most useful feedback you could give.

Ready images, or your own build, are on  build page, and  install guide walks through it.

Once it's running,  appliance form puts your 126 on the list. If anything goes wrong, post here or open a problem report.
#2
26.7, 26.10 Series / Re: issue with legacy firewall...
Last post by nero355 - Today at 08:09:06 PM
Quote from: thebraz on <strong>Today</strong> at 12:07:06 PMSo, it's better to migrate the rules before doing the .8 upgrade?
When 26.7.5 was released you should have migrated your Outbound NAT Rules to the new Source NAT Rules before updating to it : https://forum.opnsense.org/index.php?topic=53062.0

And the migration from Firewall Rules (Legacy) to Firewall Rules [New] was something that you should have done before upgrading from 26.1.x to 26.7.x but luckily both the Firewall Rules and NAT Rules stuff can still be done even though both have been moved to a plug-in by now... ;)

Quote from: Monviech (Cedrik) on <strong>Today</strong> at 03:25:59 PMTo be specific, it does not show up if there are no legacy firewall or NAT rules remaining.

So it doesnt track if a migration has been done or not with some kind of flag, it just reads remaining rules and decides on that to show or not.
NICE! :)
#3
German - Deutsch / Re: Caddy Logs per Wazuh Agent...
Last post by marcquark - Today at 07:57:19 PM
Falls das hier noch mal jemand liest - mit Version 2.2.3 des Plugins funktioniert es jetzt
#4
26.7, 26.10 Series / Re: Is sloppy state tracking a...
Last post by nero355 - Today at 07:52:33 PM
Quote from: FlyveHest on November 10, 2026, 08:27:49 PMOnce again, thanks a bunch for the great help, now that the basic setup is done, I can get into the fun stuff and the main reason I chose to run OPNSense.
COOL! :) You are welcome!

Now go and have some OPNsense FUN!

LOL! :P



I blame Ubiquiti for all of this to be honest :

Just like you I had one of their Routers but instead of the Edge Series EdgeRouter it was the UniFi Series USG 3P and it never blocked this kind of Inter-VLAN Traffic so there were no issues at all until I moved over to OPNsense and noticed this huge difference!

But as mentioned earlier after some TCPdump and WireShark investigation combined with some reading about all of this it turned out to be a very easy fix :)
#5
Zenarmor (Sensei) / Re: Am I missing something or ...
Last post by Greg_E - Today at 06:07:01 PM
What I'm seeing is that features are greatly expanding, but not everyone wants or needs those features. I'm going to ask you for a tiered license with very basic blocking like in the free version, but more profiles and multithreaded, then add more features and tiers above it. As it looks right now, I'm priced out of the basic things that I want, sure every feature would be cool, but I bet I never have time to implement 75% of it. I need to check back to my email because I have a person working with me to try and find a plan that fits what I can pay. Budgets in education are especially tight right now, at least where I work.

As far as having a Forti competitor goes, as long as you don't have baked in admin accounts and some of the other emergency fixes that they've needed, you might have a winner there. I'm not fond of Forti devices, seem to have too many exploits too often.
#6
26.7, 26.10 Series / Re: [Solved] UPNP fatal error ...
Last post by franco - Today at 05:12:06 PM
Both port and plugin should be hotfixed now.  May take a bit for all mirrors to pick it up.


Cheers,
Franco
#7
26.7, 26.10 Series / [Solved] UPNP fatal error afte...
Last post by Cljackhammer - Today at 04:50:52 PM
I followed the instructions in the Reddit thread that Franco posted and the issue was resolved. This issue has been resolved.
#8
26.7, 26.10 Series / Re: UPNP fatal error after upg...
Last post by Cljackhammer - Today at 04:44:25 PM
Okay. Thanks Franco. I removed the default_min_port=1024 and friendly_name=OPNsense UPnP IGD &amp; PCP from the configuration file and the service started. I'm not sure if this will negatively impact anything. I'll wait to hear back from the Opnsense team.
#9
26.7, 26.10 Series / Re: UPNP fatal error after upg...
Last post by franco - Today at 04:40:18 PM
We're working through the sloppy submissions to the port and plugin now and hotfix as we progress.

https://www.reddit.com/r/opnsense/comments/1xtjd8f/comment/19shbpitagx35/


Cheers,
Franco
#10
26.7, 26.10 Series / [Solved] UPNP fatal error afte...
Last post by Cljackhammer - Today at 04:20:23 PM
Errorminiupnpd Error reading configuration file /var/etc/miniupnpd.conf
2026-11-11T10:16:53-05:00Errorminiupnpd invalid option in file /var/etc/miniupnpd.conf line 9 : friendly_name=OPNsense UPnP IGD &amp; PCP
2026-11-11T10:15:53-05:00Errorminiupnpd Error reading configuration file /var/etc/miniupnpd.conf
2026-11-11T10:15:53-05:00Errorminiupnpd invalid option in file /var/etc/miniupnpd.conf line 9 : friendly_name=OPNsense UPnP IGD &amp; PCP

Now the service does not start.