Comment on My Dream of a Home Router / Server
abeorch@friendica.ginestes.es 6 days ago@Onomatopoeia I think in this case redundancy could be better delivered through a degree of distribution / modularity - perhaps through keeping compontents separate (I have an issue with an application but that doesn't knock out router features) but also through chain of trust with friends and family - you can't access your device (network, power, application ) then you could access backups stored with others - But I do take the point - and discused it in another comment - that perhaps modularity is the answer (e.g. Having a battery backup component that cound support a router component and an app server component ) but perhaps I'm over thinking this anyway - I have no practical way of implementing such a solution / framework myself - perhaps I'm just provocatively discussing it so that people like #Netbox and @bananapi see the discussion and think - hmm perhaps we should have closer relationships with Openwrt or Yunohost - or encourage them to come together somehow..
Onomatopoeia@lemmy.cafe 6 days ago
Exactly, keeping components separated, especially the router.
Hardware routers “cost money because they save money” (Sorry, couldn’t resist that movie quote). A purpose-built router will just run and run. I have 20 year old consumer routers that still “just work”. Granted, they don’t have much in the way of capability, but they do provide a stable gateway.
I then use two separate mesh network tools, on multiple systems. The likelihood of both of those failing simultaneously is low. But I still have a single failure point in the router, which I accept - I’ve only had a couple outright fail over 25 years, so I figure it’s a low risk.