False positive what? I didn’t give any specific examples of alerts, just simply monitoring metrics. Are you referring to the note on the Dnsmasq memory leak?

For any hams here, maybe this blog post will be up your alley. 73!

I write a tech and radio blog, if that’s your schtick. If not, no worries. Post your rss feed when you’re done!

https://roguesecurity.dev/

They misspelled “backdoors.”

I love avocados, but can’t say I’ve ever liquified them then drizzle on toast…

The OIDC settings in the Authelia config reference were the most nebulous to me, but they weren’t entirely stumping. The hard part was interpreting whether my errors stemmed from an issue on the client application side or on the Authelia side.

I would imagine you could likely extend the config snippets from my post to work in your situation with a few tweaks. The big lift, the OIDC provider is covered, so I’d be curious to hear what else you have to tweak!

Hey good for you, that’s awesome! My home network is also dual stacked.

You’re right about the apples to oranges comparison, but it’s not so wildly off, because the commentary is on adoption of new standards, regardless of bolt-on “fixes.” Unauthenticated SNMP went through three revisions prior to adding authentication and encryption support.

And IPv6 was codified in RFCs and first addresses issued in 1999 but look where we are now. I’d bet your corporate network doesn’t use IPv6 still. It’s unfortunate, but sometimes the wheels of change are slow.

Nagios is a premium offering. They have some open source components, but the software model is absolutely not built around the spirit of GPL.

Zabbix is the obvious alternative in my mind, and it is AGPLv3, so absolutely in the same spirit as the LibreNMS license. It’s a slightly different tool though, and less network-specific. Having used both, I prefer LibreNMS for specifically network monitoring, it’s laid out to cater more to an ISP-type entity running it, and I like that. Zabbix still gets my wholehearted stamp of approval though.

Updated the post to reflect your feedback here. Thank you!

You are absolutely correct, thank you. Sadly a bunch of devices still don’t support it, even in 2025 (like my microtik switch) for example. I will absolutely add a note about that though, thank you!

I absolutely have and used it for a while before landing on opensuse microos primarily. I absolutely see the benefit and enjoyed the git-centric nature, keeping flakes in repos with a flavor for each machine. What I didn’t enjoy, however, was the seemingly poor documentation. Quite frankly too, the drama surrounding the community doesn’t inspire confidence either. I decided I ought to try out guix but haven’t gotten to it yet. I do actually still have one nixos VM that hosts some services for me and is built entirely on the concept of the impermanence flake. That was pretty cool.

Excellent! Let me know if there are specific things you’d like to hear about.

Absolutely! I’d happily take any comments you have from running it in an enterprise setting, if you care to share.

That’s not how that works. network_mode: host shares the network namespace with the container host, so it doesn’t do any NAT, it only exists on the host’s IP. It would be akin to running a natively installed app, rather than in a container. macvlan networking is what gives a container its own IP on the logical network, without the layer of NAT that the default bridge mode networking that docker typically does.

God hasn’t responded to a single one of my issues or merged a pull request since I started on this earth. Slacker.

Today I fell off a ledge into orbit.

I would love to if I had them! Haha. I’m working on the dashboard right now, which will be part two.

I don’t have a great answer on the IOPS requirement, but I imagine it’s less than something based on elasticsearch/open search based on the reindexing. I’ll try and benchmark it if possible.

Great question, I’ve asked myself the same thing.

First, in my opinion they serve to achieve different things. While openwrt is a firewall, it’d a simple zone based firewall and it designed primarily as router firmware, not firewall software.

Opnsense is BSD based, openwrt is Linux based. Those both haves pros and cons. BSD has serious pedigree in the networking world. Juniper switches are still based on BSD even. Openwrt gets the Linux traffic shaping goodies like cake though.

I chose openwrt because it’s more suited to my environment, where I have 10 VLANs, a 10G fiber core, and want IDS/IPS. Openwrt is meant to be lighter weight, but is less feature-full.

There’s not even a potential Oxford comma in there. It’s an interjection, not a list.