this post was submitted on 31 Jan 2026
44 points (100.0% liked)

Selfhosted

59858 readers
659 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.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

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

  5. Submission headline should match the article title.

  6. No trolling.

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
44
System Redundancy (feddit.uk)
submitted 4 months ago by Cyber@feddit.uk to c/selfhosted@lemmy.world
36 comments fedilink hide all child comments
 

After being home for weeks, I went away for business, the 1st night away there was a brief powercut and the firewall (on a UPS) seemed to get stuck.

So, that's no DNS, DHCP, or connectivity between wifi and LAN... All due to (admittedly aging) hardware issue.

Since then my entire home system has had issues whilst it all settles down.

It made me think about getting some redundancy into the system to handle a single failure.

So,.can you give me any insights into High Availability like CARP (for pfSense), VM failover (on Incus?), mesh wifi, Home Assistant, etc?

Of course there are going to be single points, like ISP line, etc, but seems like something to test out.

you are viewing a single comment's thread
view the rest of the comments
[–] just_another_person@lemmy.world 3 points 4 months ago* (last edited 4 months ago) (1 children)

So then as a next step, I'd set Wireshark up on one of your regularly hosts, set it to filter for DHCP traffic, confirm you're seeing regularly advertisements first, then reboot the device that's responsible for DHCP and make sure it resumes sending those advertisements when it comes back.

If it's the same device handling DNS, make sure it's also immediately returning responses after the reboot as well with dig or nslookup.