starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-12 04:10:32 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[Bug] Tailscale Android beta app doesn't create routes when using Headscale #697

New Issue
Closed
opened 2025-12-29 02:22:18 +01:00 by adam · 1 comment
adam commented 2025-12-29 02:22:18 +01:00
Owner
Copy Link

Originally created by @Ziomal12 on GitHub (Apr 25, 2024).

Is this a support request?

  • This is not a support request

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When connected to self-hosted Headscale instance android client cannot ping nor initiate connections to other devices on tailnet. (Checked with Termux ping command, Ping tools and CX file explorer for SMB and ConnectBot for SSH).

The only scenario I was able to get a ping was when pinging exit node that the android client was currently using.

Other devices in tailnet can ping android client without issues all the time.

Seems like when connected to Headscale server the app doesn't create routes:
headscale:
Routes: [ 100.100.100.100/32 -> 0.0.0.0 tun0 mtu 0 ]
tailscale:
Routes: [ 100.76.31.70/32 -> 0.0.0.0 tun0 mtu 0,100.87.172.75/32 -> 0.0.0.0 tun0 mtu 0,100.91.28.81/32 -> 0.0.0.0 tun0 mtu 0,100.119.22.118/32 -> 0.0.0.0 tun0 mtu 0,fd7a:115c:a1e0::/48 -> :: tun0 mtu 0,100.100.100.100/32 -> 0.0.0.0 tun0 mtu 0 ]

Bug filed with Tailscale https://github.com/tailscale/tailscale/issues/11731

Expected Behavior

It should connect

Steps To Reproduce

  1. Download Android Beta Client from Play Store.
  2. Login to self hosted tailscale instance.
  3. Enable tailscale.
  4. Try to ping other device in tailnet from Android client (fails).
  5. Enable exit node.
  6. Try to ping currently used exit node from android client (successful).

Environment

- OS: Ubuntu 22 LTS
- Headscale version: 0.23.0-Beta9
- Tailscale version: 1.65.40-t449be38e0-g24dc71d8d24
Docker and native Headscale version

Runtime environment

  • Headscale is behind a (reverse) proxy
  • Headscale runs in a container

Anything else?

No response

Originally created by @Ziomal12 on GitHub (Apr 25, 2024). ### Is this a support request? - [X] This is not a support request ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior When connected to self-hosted Headscale instance android client cannot ping nor initiate connections to other devices on tailnet. (Checked with Termux ping command, Ping tools and CX file explorer for SMB and ConnectBot for SSH). The only scenario I was able to get a ping was when pinging exit node that the android client was currently using. Other devices in tailnet can ping android client without issues all the time. Seems like when connected to Headscale server the app doesn't create routes: headscale: `Routes: [ 100.100.100.100/32 -> 0.0.0.0 tun0 mtu 0 ]` tailscale: `Routes: [ 100.76.31.70/32 -> 0.0.0.0 tun0 mtu 0,100.87.172.75/32 -> 0.0.0.0 tun0 mtu 0,100.91.28.81/32 -> 0.0.0.0 tun0 mtu 0,100.119.22.118/32 -> 0.0.0.0 tun0 mtu 0,fd7a:115c:a1e0::/48 -> :: tun0 mtu 0,100.100.100.100/32 -> 0.0.0.0 tun0 mtu 0 ]` Bug filed with Tailscale https://github.com/tailscale/tailscale/issues/11731 ### Expected Behavior It should connect ### Steps To Reproduce 1. Download Android Beta Client from Play Store. 2. Login to self hosted tailscale instance. 3. Enable tailscale. 4. Try to ping other device in tailnet from Android client (fails). 5. Enable exit node. 6. Try to ping currently used exit node from android client (successful). ### Environment ```markdown - OS: Ubuntu 22 LTS - Headscale version: 0.23.0-Beta9 - Tailscale version: 1.65.40-t449be38e0-g24dc71d8d24 Docker and native Headscale version ``` ### Runtime environment - [X] Headscale is behind a (reverse) proxy - [X] Headscale runs in a container ### Anything else? _No response_
adam added the bug label 2025-12-29 02:22:18 +01:00
adam closed this issue 2025-12-29 02:22:18 +01:00
adam commented 2025-12-29 02:22:19 +01:00
Author
Owner
Copy Link

@Ziomal12 commented on GitHub (May 8, 2024):

Fixed by Tailscale app update.

@Ziomal12 commented on GitHub (May 8, 2024): Fixed by Tailscale app update.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#697
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?