this post was submitted on 31 Aug 2023
9 points (100.0% liked)

Selfhosted

40394 readers
328 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
9
My self-hosted home setup (programming.dev)
submitted 1 year ago by tiller@programming.dev to c/selfhosted@lemmy.world
17 comments fedilink hide all child comments
 

Dedicated wifi for automation allows me to have devices such as Xiaomi Vaccuum, or security camera not phoning home. OpenWRT with good firewall rules completely isolate my "public" containers/VMs from my lan.

Server was built over time, disk by disk. I'm now aiming to buy only 12TB drives, but I got to sacrifice the first two as parity...

I just love the simplicity of snapraid / mergerfs. Even if I were to loose 3 disks (my setup allows me the loss of 2 disks), I'd only loose data that's on these disks, not the whole array. I lost one drive once, recovery went well and was relatively easy.

I try to keep things separated and I may be running a bit too many containers/vms, but well, I got resources to spare :)

top 17 comments
sorted by: hot top controversial new old
[–] Ac5000@lemm.ee 3 points 1 year ago* (last edited 1 year ago)

Thank you for posting this with the explanations and great visuals! I am wanting to upgrade to a setup almost identical to this and you've basically given me the bill of materials and task list.

Anything you wish you had done differently or suggest changing/upgrading before I think about putting something similar together?

[–] Huschke@programming.dev 1 points 1 year ago* (last edited 1 year ago)

I would never use an ISPs router for my home network. It just causes so many issues that you can easily avoid by either using your own router directly or if that is not possible putting the device into "bridge" mode and using your own router behind it.

What are some of the issues?

The devices the ISPs send out are usually the cheapest hardware imaginable and therefore introduce substantial unnecessary latency.

Where I live some ISPs also used to use tools that genereted wifi passwords based on the devices MAC address. While this is apparently fixed now, a lot of non tech savvy users still use these old devices that are basically open to anyone now.

To save even more money, they sometimes deliberately send out faulty devices (as in devices that drop connection frequently, restart for no reason, etc) which is just horrible.

I know these issues because I worked in that field and there are a lot more unfortunately...

[–] Bjornir@programming.dev 1 points 1 year ago

That is a great quality post! Congratulations and thank you

Your home network is not too shabby either ;)

[–] Decronym@lemmy.decronym.xyz 1 points 1 year ago* (last edited 1 year ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
AP WiFi Access Point
IP Internet Protocol
NAT Network Address Translation
SSD Solid State Drive mass storage

4 acronyms in this thread; the most compressed thread commented on today has 7 acronyms.

[Thread #100 for this sub, first seen 1st Sep 2023, 11:25] [FAQ] [Full list] [Contact] [Source code]

[–] tuff_wizard@aussie.zone 0 points 1 year ago (2 children)

That’s… not all hand written is it? No one who is good at computers can write that well. We got into this BECAUSE we couldn’t write well, right?

[–] lemming@lemmy.sdf.org 2 points 1 year ago

Looks like excalidraw to me. I use it all the time to quickly make diagrams like these.

[–] twack@lemmy.world 0 points 1 year ago (1 children)

It's not, look at postgres under both DB in the last picture. That's not just the same writing, it's identical.

[–] Sotuanduso@lemm.ee 0 points 1 year ago (1 children)

Hmm, nice detailed specs on your home network. Mind sharing your IP? For, uh... totally trustworthy reasons. Asking for a friend. >: )

[–] Nails@lemm.ee 1 points 1 year ago (1 children)

192.168.0.1

[–] Sotuanduso@lemm.ee 1 points 1 year ago (1 children)

Got it. Sending the virus to 192.168.0.1...

[–] supercritical@lemmy.world 1 points 1 year ago

It’s been three months, I’m assuming the attack worked as intended lol

[–] transmatrix@lemmy.world 0 points 1 year ago (1 children)

As an FYI: this set up is vulnerable to ARP spoofing. I personally wouldn’t use any ISP-owned routers other than for NAT.

[–] tiller@programming.dev 0 points 1 year ago (1 children)

I'm not well versed in ARP spoofing attack and I'll dig around, but assuming the attacker gets access to a "public" VM, its only network adapter is linked to the openwrt router that has 3 separated zones (home lan, home automation, dmz). So I don't think he could have any impact on the lan? No lan traffic is ever going through the openwrt router.

[–] transmatrix@lemmy.world 0 points 1 year ago* (last edited 1 year ago) (2 children)

The risk is the ISP Wi-Fi. As long as you’re using WPA with a good long random passkey, the risk is minimal. However, anyone who had access to your Wi-Fi could initiate an ARP spoof (essentially be a man-in-the-middle)

ETA: the ARP table in networking is a cache of which IP is associated with which MAC Address. By “poisoning” or “spoofing” this table in the router and/or clients, a bad actor can see all unencrypted traffic.

[–] foggenbooty@lemmy.world 1 points 1 year ago

How would you change his setup to prevent ARP attacks? More network segmentation (clients and servers on separate VLANs) or does OPNsense additional protections I should look into?

[–] tiller@programming.dev 1 points 1 year ago* (last edited 1 year ago)

Well, to be honest if someone has access to my Wi-Fi, I'd consider that I've already lost. As soon as you're on my lan, you have access to a ton of things. With this setup I'm not trying to protect against local attacks, but from breaches coming from the internet