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

How to use routes? In Android for example. #327

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

Originally created by @thehijacker on GitHub (Sep 14, 2022).

Issue description

I think this is third time I am setting up Headscale. Each previous attempts I gave up as I was unable to configure it the same way as with Wireguard directly. I have three networks at home. All three reachable on docker server. 10.0.107.0/24, 10.0.208.0/24 and 192.168.28.0/24. My goal is to reach all three when I connect to Headscale server with any client. Client should be Windows or Android.

To Reproduce

I started the server using Docker. Then created namespace and connected two clients to it. One is another linux server, other is my Android phone. For linux server I added "--advertise-routes=192.168.28.0/24,10.0.107.0/24,10.0.208.0/24" parameter to tailscale command. Then I enabled all three routes on Headscale and this seems to work.

But for Android client I just can not find an option to add this routes client side. So when I am connected I for example can not ping 10.0.107.0/24 devices.

Can I add them on Headscale server side?

Context info

Headscale version: 0.17.0-alpha2
Android client: 1.30.1
OS: Linux Ubuntu

root@docker-server:~# docker exec headscale headscale nodes list
ID | Hostname      | Name          | NodeKey | Namespace | IP addresses                    | Ephemeral | Last seen           | Online  | Expired
1  | Mi 10T Pro    | mi-10t-pro    | [4LfgH] | clients   | 100.64.0.1, fd7a:115c:a1e0::1   | false     | 2022-09-14 10:39:52 | offline | no
2  | web-wg-server | web-wg-server | [goF/h] | clients   | 192.168.28.1, fd7a:115c:a1e0::2 | false     | 2022-09-14 10:01:20 | offline | no
root@docker-server:~# docker exec headscale headscale machines routes list -i 1
Route | Enabled
root@docker-server:~# docker exec headscale headscale machines routes list -i 2
Route           | Enabled
10.0.107.0/24   | true
10.0.208.0/24   | true
192.168.28.0/24 | true
Originally created by @thehijacker on GitHub (Sep 14, 2022). <!-- Headscale is a multinational community across the globe. Our common language is English. Please consider raising the issue in this language. --> <!-- If you have a question, please consider using our Discord for asking questions --> **Issue description** I think this is third time I am setting up Headscale. Each previous attempts I gave up as I was unable to configure it the same way as with Wireguard directly. I have three networks at home. All three reachable on docker server. 10.0.107.0/24, 10.0.208.0/24 and 192.168.28.0/24. My goal is to reach all three when I connect to Headscale server with any client. Client should be Windows or Android. **To Reproduce** I started the server using Docker. Then created namespace and connected two clients to it. One is another linux server, other is my Android phone. For linux server I added "--advertise-routes=192.168.28.0/24,10.0.107.0/24,10.0.208.0/24" parameter to tailscale command. Then I enabled all three routes on Headscale and this seems to work. But for Android client I just can not find an option to add this routes client side. So when I am connected I for example can not ping 10.0.107.0/24 devices. Can I add them on Headscale server side? **Context info** Headscale version: 0.17.0-alpha2 Android client: 1.30.1 OS: Linux Ubuntu ``` root@docker-server:~# docker exec headscale headscale nodes list ID | Hostname | Name | NodeKey | Namespace | IP addresses | Ephemeral | Last seen | Online | Expired 1 | Mi 10T Pro | mi-10t-pro | [4LfgH] | clients | 100.64.0.1, fd7a:115c:a1e0::1 | false | 2022-09-14 10:39:52 | offline | no 2 | web-wg-server | web-wg-server | [goF/h] | clients | 192.168.28.1, fd7a:115c:a1e0::2 | false | 2022-09-14 10:01:20 | offline | no root@docker-server:~# docker exec headscale headscale machines routes list -i 1 Route | Enabled root@docker-server:~# docker exec headscale headscale machines routes list -i 2 Route | Enabled 10.0.107.0/24 | true 10.0.208.0/24 | true 192.168.28.0/24 | true ```
adam added the bug label 2025-12-29 01:27:04 +01:00
adam closed this issue 2025-12-29 01:27:04 +01:00
adam commented 2025-12-29 01:27:05 +01:00
Author
Owner
Copy Link

@juanfont commented on GitHub (Sep 20, 2022):

Can you please raise this in Discord?

@juanfont commented on GitHub (Sep 20, 2022): Can you please raise this in Discord?
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#327
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?