← Back to context

Comment by baq

4 days ago

tailscale has a much better chance to work when you need it most. WireGuard is blocked by too much stuff.

Tailscale uses wireguard.

What it provides is a opinionated configuration management - which is admittedly great which is why I use it as well, but it's nonsensical to say tailscale works in places where wireguard is blocked.

You're likely just noticing the preconfigured nat traversal which tailscale provides and never set one up yourself, as you'd need a static IP for that and it's unconfigured by default.

  • > it's nonsensical to say tailscale works in places where wireguard is blocked

    I have two machines on my desk, I configure a wg service on both. I also configure tailscale on both. Everything works.

    I move one machine to another network, at a friend's place.

    Wg does not work anymore. Tailscale works. So this is very much sensible to say what GP said.

    Now, you can have all kinds of explanations about why wg dos not work and ts does, you know STUN, DERP, ts using wg under the hood, and whatnot but the facts are cruel: I cannot wg to my machine, but I can ts.

    • I was just pointing out that the statement wrt "wireguard being blocked while tailscale works" is nonsensical.

      It remains nonsensical no matter how uninformed the user may be - even if he's proud of being such, as you seem to be.

      This was not a discussion about what tool to use if the person doesn't know about networking and is generally ... "less technical".

      5 replies →

I’ve never noticed wireguard be blocked by something, have you experienced this?

  • many times in public/hotel wifis. it's usually places which blanket ban UDP and allow TCP 80 and 443 exclusively. tailscale somehow manages to get a connection.