Recent posts

#1
General Discussion / Re: Change TTL of mDNS/SSDP pa...
Last post by viragomann - Today at 04:57:26 PM
Quote from: h3zwe on November 19, 2026, 09:27:27 PMThis interaction has a time-to-live value in the multicast packet header of 1, so when it tries to cross the Docker bridge to another subnet, it gets dropped since the TTL is decremented by 1 and TTL=0 on the next subnet which is a drop rule.

Is there any way to fix this in OPNsense?
I don't expect, that the packets even reach the OPNsense interface. So there is nothing, OPNsense can do to forward them.
As you wrote yourself, it gets dropped in the docker bridge, since it is a gateway to your local network in fact.

Consider to connect the container to another virtual network, which has a layer 2 connection to OPNsense (and use UDP Broadcast relay to forward it to the other network segment).
Maybe this works with an macvlan in docker, I don't know.
#2
German - Deutsch / Re: Änderung bei Config wieder...
Last post by viragomann - Today at 04:15:05 PM
Quote from: Zapad on <strong>Today</strong> at 11:19:57 AMWie Less, More, Nano, Vi funktionieren wissen immer weniger User.
Auch wenn man das wüsste, muss man sich erst mal bewusst sein, dass man sich in Less befindet, wenngleich es die Anzahl an Backups gar nicht erfordern würde. Ich hatte da auch meine Schwierigkeiten, wieder raus zu kommen.
Da wäre ein entsprechender Hinweis schon angebracht.
#3
General Discussion / Re: Has anyone heard of / trie...
Last post by julian_bldt - Today at 02:43:24 PM
Quote from: Patrick M. Hausen on November 21, 2026, 11:20:44 PMWhy not use GPL or Affero GPL?

Hi Patrick,

I started with the AGPL, actually, and switched on purpose. The AGPL allows anyone to sell the software or run it as a paid hosted service as long as they publish their changes, and that is exactly what I did not want. A one-person project can't compete with a company that takes the code and puts a price on it.

So it is PolyForm Shield now: free to read, run and modify, also commercially inside your own company, but not to resell as a competing product.

Julian
#4
26.7, 26.10 Series / Re: https://nginx2root.com/ Is...
Last post by Timeraider - Today at 02:19:40 PM
Quote from: franco on November 21, 2026, 09:01:04 PM-SNIP-


You can see that nginx is one of the earliest ones maintained by Fabian who very rarely still helps out with a PR review at least.  I'd say since 2020 it has been more or less on life support. The plugin also has some technical debt due to being so old that makes it hard to modernise, too. But back then we all didn't know better.


Cheers,
Franco

Thank you for that clear answer, that actually does help a lot.
I can certainly understand being... for the lack of a better word.. "stuck" with legacy stuff and especially if it relies on old building blocks (aka, not something that a github bot can simply copy over from upstream with one click but instead needs manual adding, checking etc. etc.) which at the time were fine but can't keep up with nowadays changes.
Sounds like its perfectly fine as reverse proxy for most homelabs whereby it simply does internal proxying while tailscale, cloudflare or VPNs handle the external part, while having it fully handle external connections/threats might be debatable and probably advised to make sure there is no option to move on to(as much as I do have to say that the person implementing the UI certainly did a great job in making additions like honeypots, bot protection, WAF).
Makes it understandable that OPNsense would rather put their effort into the main product, which I still agree is a very strong product thanks to that.

Quote from: nero355 on November 20, 2026, 05:22:09 PM
Quote from: Timeraider on November 20, 2026, 01:25:49 AMWhile at the same time the only full replacement for a very easy to set up nginx is 3 other plugins with one being limited to paying customers and it would still be missing functionality that I'm used to.
The real full replacement is IMHO simply setting up a seperate Server/VM/LXC and hosting all those things there instead of running it on your OPNsense Router/Firewall which should not be bothered with all of this stuff :)

Considering the way our weird world has changed it might be also time for the OPNsense Team to consider not offering all of these additional packages anymore.....????

I agree with it partly but on the "not bothered with all of this stuff" it is debatable. The "let everything do what it does best" is kind of an old saying that seems to hang on in current age but doesnt really apply much anymore. Reverse proxy is exactly the thing that makes sense here because it can directly influence and inform other security applications on the firewall. It can update firewall rules, throw information to crowdsec, IPS etc. etc. meaning everything gets blocked at the edge of your network, not halfway inside it.
Theoretically using a "firewall" as router isnt its role either, but I can garantee that at least half OPNSense devices are currently working as modem :P
NASes are fine running docker containers, servers are fine being used for raid storage alone, mobile phones are gaming emulators etc.
Ofcourse there is only one thing I can't understand and thats people trying to use an OPNsense box as accesspoint, but thats a different story XD

#################

Anyway, good to see an clear answer from Franco which actually helped make some decisions. Tried the other options on OPNsense but felt stuff was missing or not as logical so ended up putting SWAG with honeypots and certbot together with Crowdsec on my server and running it through there.
Did miss some visibility there, but nothing that cant be solved with some homemade Python .. and help from Claude Code for the API and UI stuff XD

(In case there is a chance of someone asking, in advance, .. no, below is not generally available software, simply something I made to monitor very specifically things I want to monitor on my network through a docker-run image. Can always share the source code but it is very specifically made for software products I use in my home, so usually I wouldnt recommend it unless someone is willing to fork it to adjust and maintain for themselves.. as I will remove features whenever I stop using something XD)



#5
IMHO All the tooling you need is already present on OPNsense, so all it takes is a shell script that ties it together.

- bectl for snapshot management
- opnsense-update to perform the update
- reboot

To get a feel for bectl you might want to refer to this old post of mine.


Assume your current active BE is named 26.7.9 (makes sense to use version numbers, IMHO - others prefer timestamps like 202611221257), and an update to 26.7.10 is available you would:

Rename the BE to 26.7.10, because we will be installing into the live filesystem:
bectl rename 26.7.9 26.7.10
Create a new BE named 26.7.9 which will contain the current state before the update, so we can roll back to it if necessary:
bectl create 26.7.9
Then update and reboot.

For daily scheduled jobs - if that is frequent enough for you - intending not to interfere with the managed OPNsense installation, I suggested placing the script in the /root directory, making it executable, and then doing a symlink:

ln -s /root/daily-update.sh /usr/local/etc/periodic/daily/update
The script will then run every night at 3:01 local time.

See here for comparison.



HTH, kind regards,
Patrick
#6
The SSD is broken. Unlikely for a new unit but possible. Contact Deciso for warranty.
#7
German - Deutsch / Re: Änderung bei Config wieder...
Last post by Zapad - Today at 11:19:57 AM
Ja, das hat so geklappt, Danke.

Man darf aber nicht vergessen das es immer mehr Gui klicker sind und Terminal/shell nur zur Not benutzen.

Wie Less, More, Nano, Vi funktionieren wissen immer weniger User.
#8
Best send a mail to sales with your issue if you bought it directly from deciso.
#9
General Discussion / Re: How secure is OPNsense wit...
Last post by Seimus - Today at 11:09:48 AM
There can be Vuls, that can be exploited even if you do not host anything on the Internet.

There is another problem, even if you do not host anything on the internet, your devices connect to the Internet, PCs, Phones e.g users. Imagine one of the user gets infected, that infected device may start probing your network and try to take over the most essential parts of it e.g "your GW". You may not expose the network to the Internet but you expose it to the LAN.

I would definitely not take for granted that if you do not host anything on the Internet that you are 100% safe.
If you do not have time to upgrade, well than schedule at least auto updates, even thought I am against it.
Upgrading a core components should be always a manual task where the administrator reviews & verifies,

Regards,
S.
#10
Thanks for the tips, guys! I'm not exactly sure what the issue was, but I adjusted the firewall rules, NAT and set the static routes to (for DNS)  10.2.0.1/32 and 10.3.0.1/32 again, and everything seems to work now. /30 worked but now I am using /32 again.

VPN failover is what I want to look at next thanks!

Does anyone know how I need to configure Unbound so that DNS requests get sent over the VPN tunnel? When I set the interface to the WireGuard (/32) under Unbound > General > Advanced > Outgoing Interface, it doesn't do anything by itself, but once I also set the static routes to the DNS servers, it starts working. Is that all that's needed?