this post was submitted on 22 Mar 2025
26 points (100.0% liked)

Selfhosted

44902 readers
894 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I have solid experience configuring and maintaining Linux, but my knowledge in networking is quite basic. What should my first configurations and preparations should I do before flashing Openwrt and setting it up for my home network?

PS. If I can use the switch as a NAS, I'd be delighted.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 8 points 2 days ago* (last edited 2 days ago) (1 children)

So, this question is very difficult to answer. I don't want you to be discouraged though.

I can't answer you because I don't know your goals. Since we're in /c/selfhosted, I assume you're experimenting with some self-hosted setups, which is awesome! But what exactly are you hoping to do with OpenWRT? And what’s the plan for the switch? Are you aiming for better network control, VLANs, firewall rules, or are you just looking to have network area storage?

If you can share more about what you’re trying to accomplish, folks here will be much better equipped to help you figure out your next steps.

[–] [email protected] 2 points 1 day ago

Thank you for all the questions to help me clarify my use case 🙂

At the very basic, I'd like to:

  1. achieve better security through segmentation by isolating cloud-connected devices, guest devices from trusted devices.
  2. Being able to "pin" a Mac address to an IP, and being able to use internal network name resolution to reach those devices.
  3. a blocklist for known ad-domains / malicious domains.

Once the basics are in place, I'd like to elevate my netsec game and implement:

  • a high level monitoring capability to seen what devices are communicating with what domains / IPs
  • An IDS capability of some sort to be able to detect anomalies in my LAN.

The NAS part is just for convince, it would be nice to have a samba / NFS with my files available when I need them.