You’re not advertising 196.x.x.x routes to your tailnet?
Comment on Tailscale difficulties
pirateMonkey@lemmy.world 2 days ago
Sorry for misformatted code.
tailscale-authkey1: image: tailscale/tailscale:latest hostname: myhost environment: - TS_AUTHKEY=xx - TS_STATE_DIR=/var/lib/tailscale - TS_USERSPACE=false - TS_EXTRA_ARGS=--advertise-exit-node,--accept-routes - TS_ROUTES=192.168.0.0/24 volumes: - ts-authkey-test:/var/lib/tailscale - /dev/net/tun:/dev/net/tun cap_add: - NET_ADMIN - SYS_MODULE restart: unless-stopped nginx-authkey-test: image: nginx network_mode: service:tailscale-authkey1
F04118F@feddit.nl 2 days ago
pirateMonkey@lemmy.world 2 days ago
No, I thought the routing was to forward the IP from the Tailscale 100.x.x.x subnet(? not sure I’m using that word correctly) to where the resources I want to access are (in my case, my local 192.168 addresses).
BCsven@lemmy.ca 1 day ago
The firewall on your server may need masquerading set and IP forwarding set.
stratself@lemdro.id 1 day ago
try adding the sysctls parameters to this docker container