I did this and it still seems to randomly disconnect.
dan
joined 2 years ago
If you have a separate subnet for it, then why do you only want it to be connected when you're not on home wifi? You can just leave it connected all the time since it won't interfere with accessing anything outside that subnet.
One of the main benefits of Wireguard (and Tailscale) is that it's peer-to-peer rather than client-server. You can use the VPN IPs at home too, and it'll add barely any overhead.
(leaving it connected is assuming you're not routing all your traffic through one of the peers)
In countries like Australia that have good consumer protection, they'd have to replace failed CPUs even outside of the warranty period, because they've still failed in a time frame shorter than a regular person would expect a CPU to last. The USA really needs better consumer laws.
The majority of users aren't contributors though. It's fine to mention it in contributor documentation but I find it weird to advertise it as an end-user feature given most apps written in other languages don't do this.
It's also a floating signifier for a lot of things.
Like what?
conditional Auto-Connect. If not on home wifi, connect to the tunnel.
You don't need this with Tailscale since it uses a separate IP range for the tunnel.
Edit: Tailscale (and Wireguard) are peer-to-peer rather than client-server, so there's no harm leaving it connected all the time, and hitting the VPN IPs while at home will just go over your local network.
The one thing you probably wouldn't do at home is use an exit node, unless you want all your traffic to go through another node on the Tailnet.
Yeah my wife and I are both on Android, and I haven't been able to figure out why it does that.
The Android client is open-source so maybe someone could figure it out. https://github.com/tailscale/tailscale-android
small minority of Rust programmers who are very loud
They also list "written in Rust" as the primary feature of software they write, even though the majority of users don't care as long as it works properly.
and they kept denying there was an issue, until there was so much proof that they couldn't deny it any more and were like "okay fine there's an issue so we're going to be extra generous and extend your warranty one whole year"
flavors of iron
Yum yum
Is it just you that uses it, or do friends and family use it too?
The best way to secure it is to use a VPN like Tailscale, which avoids having to expose it to the public internet.
This is what I do for our security cameras. My wife installed Tailscale on her laptop and phone, created an account, and I added her to my Tailnet. I created a home screen icon for the Blue Iris web UI on her phone and mentioned to her, "if the cameras don't load, open Tailscale and make sure it's connected". Works great - she hasn't complained about anything at all.
If you use Tailscale for everything, there's no need to have a reverse proxy. If you use Unraid, version 7 added the ability to add individual Docker containers to the Tailnet, so each one can have a separate Tailscale IP and subdomain, and thus all of them can run on port 80.
Headscale is a replacement for the coordination servers, which are only used to distribute configs and help nodes find each other. It won't change client-side behaviour.