I set up Headscale and Tailscale using Docker on a VPS, which I want to use as my public IPv4 and Reverse Proxy to route incoming traffic to my local network and e. g. my home server. I also set up Tailscale using Docker on my home server and connected both to my Headscale server.
I am able to ping on Tailscale container from the other and vice versa and set up –advertise-routes=192.168.178.0/24 on my home server as well as –accept-routes on my VPS, but I can’t ping local IP addresses from my VPS. What am I missing?
Both container are connected to the host network, I have opened UDP ports 41641 and 3478 on my VPS.

@riffy@lemm.ee
link
fedilink
English
36M

Try v1.60.1

Dataprolet
creator
link
fedilink
English
16M

Of what?

@riffy@lemm.ee
link
fedilink
English
36M

image: tailscale/tailscale:v1.60.1

To pull that version of tailscale. Latest broke subnets.

Dataprolet
creator
link
fedilink
English
16M

Doesn’t seem to work.

@riffy@lemm.ee
link
fedilink
English
26M

You might have other issues then, but I’d use that version of tailscale since it was the last version to work with subnets. Also, only the owner’s account works cuz sharing subnets broke even longer ago, and I’m positive neither has been fixed. Good luck!

lemmyvore
link
fedilink
English
26M

Subnets seem to work for me with 1.62.0 docker image. In what way were they broken?

@riffy@lemm.ee
link
fedilink
English
2
edit-2
6M

I reported it the day the update was released cuz all of my containers are on their own ip. Got that update and nothing was reachable till I rolled back.

GitHub

Dataprolet
creator
link
fedilink
English
1
edit-2
6M

deleted by creator

Create a post

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:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

  • 1 user online
  • 127 users / day
  • 422 users / week
  • 1.16K users / month
  • 3.85K users / 6 months
  • 1 subscriber
  • 3.68K Posts
  • 74.2K Comments
  • Modlog