Selfhosted

40226 readers

835 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Router with Homeassistant (lemmy.world)

submitted 1 year ago by alomsimoy@lemmy.world to c/selfhosted@lemmy.world

3 comments fedilink hide all child comments

I want to build a x86 small form factor computer in order to run the router and home assistant on it, and I'm looking for the best solution:

At first I though on setting up HaOS as a router and using a dhcp plugin on homeassistant, but is a very barebones setup without much advanced networking capabilities. Also I didn't find a way to easily setup WAN.

Then I though I could set up a hypervisor and run a router OS like VyOS or openwrt and HaOS. I know proxmox, but maybe there are lighter hypervisor more capable of delivering this setup.

And finally I though that I could use openwrt and install (either natively or via docker) homeassistant on it. This currently seems like the less headachy way, but I could be totally wrong.

I can't find much documentation on either of those methods, so I'm asking to you what would you do, and if somebody is using a similar setup, to share some insights.

you are viewing a single comment's thread
view the rest of the comments

[–] greyscale@lemmy.sdf.org 3 points 1 year ago (2 children)

Once upon a time I had a little intel j1900 box with esxi on it, running pfsense in one vm and ubuntu + docker in another.

that lasted right up until I broke it, and seperated the two out again, having a home NAS and a ubiquity UDM instead for a router.

Life was too short to juggle that setup.

[–] cstine@lemmy.uncomfortable.business 4 points 1 year ago

Yeah I think that's pretty much a universal story: you consolidate things until it breaks, at which point it's impossible to fix anything because absolutely everything is broken all at once.

Routing should probably be separate hardware for most people, as should DNS (if you're running your own) and then you can probably lump most everything else on a single server or so.

[–] a1studmuffin@aussie.zone 3 points 1 year ago

Similar story here, it's a great idea until it goes wrong, then you've got two appliances down instead of one.

My Home Assistant instance has become so mission critical to my household that I've got a dedicated Pi 4 for it, with a fallback Pi 4 and preflashed SD card ready to hot swap and restore from backup.