OK, it is clearer now, thanks

If I get it correctly, this is a kind of kasm but only for the local user, right?

Yep, at least for their own internal mistake. I rebooted them a few times in that time because updates and important config updates. Even for power outages (2 iirc) they are resilient, they are set to automatic boot up when the power is back.

It didn’t happen in more than 5 years…

For critical equipment you need to spend the extra dollar to minimize this kind of stuff

I see, well if borg really ticks all checkbox es and you know how to use it I would explore any further.

Sincerely, borgbackup is really a top solution with a lot of nice features

If you have already borg, why don’t use it?

Interesting article, thanks for sharing

I don’t have time now so I will sketch the solution

You need a proxy server in your vps that will redirect the traffic to your home. Caddy is usually recommended here and I am planning to migrate to it (current is nginx)

For your dns you need something is called zone name resolution, it will resolve different ip depending where the request came from

Good luck

Hi,

Welcome to the ipv6 fantastic hell and it’s sequel about dual stack and 6to4 and 4to6 half cooked solutions.

First of all, I would not care a lot the ip addresses, not even google can extract a lot of info from the ip and ipv6 will cycle the subnet work part (via your isp) making tracking extremely difficult. On to of that you can select your dhcp6 daemon to give an address validity as low as minutes (but not practical), 24h validity should be enough. 1h validity only in severe paranoia mode.

It is important to make sure that your lan track the Wan interface for correctly updating the prefix renewal.

Try not to make a nat for ipv6 but firewall most of the stuff you don’t like, ipv6 comes wit great advantages that will dissappear if you nat the connections. And a tip, there are a lot of ipv6 icmp messages that shouldn’t be blocked in your firewall because it really improves your performance. If you nat it they will be out.

:)

I see, well, it it still serves you good, nothing to say here

Good point! I totally forgot that.

But if I am able to recall correctly the QoS for the VoLTE and just regular data is totally different and the antenna may refused to provide you enough data for a non-prior service

???

There are a lot of reputable VoIP companies, my employer right now uses them and we never faced a problem. But makes sure it is reputable ;)

And you could also port your number so to all effects it is your number.

I don’t know, I still believe it is the easiest way forward. But in the end it is your call

That much? Shit, then update the processor, probably spending 15€ is going to update the speed a lot!

Uh?!?

If that equipment is not able to get 60Mb/s there is something terrible wrong here…

What you need is a sip server / interface for making VoIP call through internet, there are many implementations and servers, selfhosted and paid. Pick up one you like.

Please, be aware that the quality of the voice call depends and a lot of the data rate. Keep this in mind uif you are in remote locations with poor coverage.

It is always recommended the asterisk + the freepbx for the gui. Please be aware that I don’t have experience with those systems

I think I didn’t get exactly what you want. Ant it keeps me wondering that perhaps there are a few concepts not so clear.

Do you want to receive streaming from a server? do you want to setup the server? Or something completely else?

If you want to receive the streaming from a server, the most compatible cost-effective solution is the Amazon fire. Works with remotes and you will be able to play every media you have because the server will transcode the file on the fly if the fire stick doesn’t support the format.

If you want something more open to tinker or to get more functionality then a raspberry pi will be enough, because once again, the heavy lifting is done by the servers (via plex server or moonlight server).

More powerful boxes exists but then you need to start thinking carefully what is your use case for not eating money.

Precisely bitwarden movement proves my point. Bitwarden tried to degrade the features/compatibility of the solution and they couldn’t because of the vaultwarden implementation.

Can they always add new features after a pay wall? Sure! But once foss Sw is here it is simple impossible to remove functionality, at most, to get some coins for services not fully selfhosted.

If tailscale tries to do something similar is goint to be a shoot into their own leg, because all the sw already disclosed makes it impossible. Could they make the relay a paid one? Sure but then they will face the competence of a vps with the Headscale implementation.

This and only this is because in your home lab only foss Sw should be allowed, even if you need to pay some money from time to time

Honestly, this seems more than your assumptions and fears than anything else.

Clients are open source and foss, the moment something strange is in, Headscale could adapt.

If they finally goes to full close source, then the community will fork (emby - jellyfinn drama).

Your arguments don’t hold together, for the good of the community

I really don’t see how the enshitification could work when we have the fee version of the central servers Headscale

So yes, it could be a pay wall for some advance featuresike funnels and so on. But the primary use is secured…

I have more than 120 electronic identities, impossible to track the counter or to remember the tld of all websites I visit.

The concepts is only useful in a very small and defined scenario.