Recent posts

#1
The thing is, such N1x0 units were like 300€ complete with 16 GByte RAM and 256 GByte SSD a year ago. Now they are more like 600€ (both assuming good brands, not el cheapo no-name SSDs that fail after one year of heavy ZFS use).
#2
Zenarmor (Sensei) / Re: Cannot allocate memory
Last post by oldRaven - Today at 05:05:48 PM
I had to do the same as of September 2026
(OPNsense 26.7.4_1-amd64)

System Tunables to -
dev.netmap.buf_num: 1000000
dev.netmap.admode: 0   
dev.netmap.ring_num: 256   
dev.netmap.buf_size: 4096

and reboot.

Many thanks!
#3
Virtual private networks / Re: Validating the WireGuard V...
Last post by marsk - Today at 04:26:32 PM
Not only understanding the flow is important for me.

I have worked as an infrastructure architect for many years on servers, virtualization, and storage,
not networks, and I am dyslexic.

Having a diagram gives me a grip of a system within three seconds, and the same goes for my colleagues and customers.
All documentation I write for systems I deploy always starts with a diagram.

So I really want to thank you for helping me.

I also think the documentation for OPNsense really could benefit from some diagrams for easier understanding.

//marsk
#4
Notification services with multiple options and various events for which notifications can be received.

Plugin changelog: https://pkg.greelan.net/changelog/os-notify-greelan.html
#5
Main interface

#6
It's wonderful and excellent work—thank you very much.


#7
Zenarmor (Sensei) / Re: Zenarmor Cloud Agent servi...
Last post by awatson2012 - Today at 04:14:28 PM
I'm seeing the same issue, anyone got a fix? Zenarmor Cloud Agent is showing as stopped when it's not installed so my monitoring shows a failed service. Currently on OPNsense 26.7.4 and Zenarmor 2.6.2.
#8
Virtual private networks / Re: Validating the WireGuard V...
Last post by marsk - Today at 04:12:36 PM
Thanks nero355

Can you please just take some pen and paper and make a drawing of what you see in your mind .

You do not need to write the name of the components just visualize them with a box of any kind,
and attach a photo so I can try to make a logical diagram.

//marsk
#9
26.7 Series / Unbound Error
Last post by spetrillo - Today at 03:37:03 PM
Hello all,

I am troubleshooting an Unbound issue. When I restarted Unbound from the cli it spit out the following:

[1790256794] unbound[48659:0] warning: setsockopt(..., SO_SNDBUF, ...) was not granted: No buffer space available
[1790256794] unbound[48659:0] warning: so-sndbuf 4194304 was not granted. Got 57344. To fix: start with root permissions(linux) or sysctl bigger net.core.wmem_max(linux) or kern.ipc.maxsockbuf(bsd) values. or set so-sndbuf: 0 (use system value).


I checked the kern.ipc.maxsockbuf tunable and it is set to 4262144.

Is this something I should be worried about?

Thanks,
Steve
#10
Quote from: marsk on Today at 02:47:06 PMif I got it right.
IMHO both attempts are OK and if it's enough for you as a reminder from time to time then that's perfectly fine, right ?!

I would personally create something like this :
- Draw a Client device.
- Then a huge circle representing OPNsense Firewalling.
- On the left edge of that circle one of your LAN Interfaces with the remark that it's also holds the Gateways for the VLANs and thus any VLAN Interfaces.
- Then a line from the Client device to the LAN Interface.
- Under that line Ethernet and again under it another one with any VLANs.
- On the right middle side of the circle one of your WireGuard interfaces.
- On the right edge of that circle one of your WAN Interfaces.
- Then a line representing let's say Ethernet over Fiber being used to connect to your ISP that is a small cloud outside the circle.
- In the middle of the circle the Routing/NAT Engine of OPNsense connected to every Interface except WAN.
- However you also need seperate "Just Routing" connections to the LAN and WireGuard Interface so maybe doing something seperate with NAT would be better ?!
- The Remote WireGuard Peer would be connected to the previously drawn small cloud outside the circle.
- And then a long VPN connection line all the way from the WireGuard Interface to the Remote WireGuard Peer.

And last but not least : Put the whole WireGuard processing/peer selection/encryption process in a seperate drawing and maybe connect it to the WireGuard Interface ?? :)



/"Quick Brainfart" which might have some mistakes or missing things in it...