this post was submitted on 01 Jun 2026
72 points (100.0% liked)

Selfhosted

60526 readers
1349 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
72
Internal network monitoring (lemmy.world)
submitted 1 month ago* (last edited 1 month ago) by ueiqkkwhuwjw@lemmy.world to c/selfhosted@lemmy.world
21 comments fedilink hide all child comments
 

How do you monitor your homelab network for internal attackers? E.g. you have a publicly available service and theres a vulnerability that you miss or you pull a bad update and suddenly someone has access to your VM/machine/container. How could you increase the chances of automatically detecting that?

The built in IDS in opnsense seems pretty useless, and doesn't really help detect if e.g. someone is trying to exploit services between your vlans (I could be using it wrong though).

Crowdsec in opnsense is nice but it seems to also be primarily for protecting from malicious actors coming from the WAN.

I've heard about the opnsense zenarmor plugin but you have to agree to a privacy policy to use it?

Another option I guess would be collecting firewall logs and making custom notifications for things that you think would be suspicious on your network.

I also know update cooldowns and not exposing anything could largely solve this too, but the monitoring and alerting question really interests me.

you are viewing a single comment's thread
view the rest of the comments
[–] daniskarma@lemmy.dbzer0.com 5 points 1 month ago* (last edited 1 month ago) (2 children)

I'm in the process of building a monitoring system with grafana stack.

Right now I have monitoring panels for some common metrics and logs. I am yet to set up alerts.

The idea being that if something goes wrong some metric will grow up unexpectedly, for instance network traffic. And I would get a notification.

What I'm still considering is what would I consider abnormal behavior, so I could set up the thresholds.

[–] Mikelius@lemmy.ml 2 points 1 month ago (1 children)

This is exactly how my network is setup. All devices log to my syslog server which I feed into a database with a self made python app, and Grafana goes from there. It's been running nonstop for like 5 years without any problems, so I'd say your in the right path!

It's also helped me catch things like:

  • finding out android leaked IPs outside VPN tunnels on connect (prior to headlines claiming this)
  • finding out nslookup on termux ignores the phone's DNS settings and tries to use Google instead
  • finding other devices that ignore my DNS server settings
  • noticing that my work Mac will turn itself on in some weird silent passive mode in the middle of the night to try and send data to apple (sleep or powered off don't matter) - caught this from the logs sent by my router
[–] ueiqkkwhuwjw@lemmy.world 1 points 1 month ago

Very interesting. Thanks for your input :)

[–] ueiqkkwhuwjw@lemmy.world 1 points 1 month ago

Yeah that's kind of what I was originally thinking to do too.