ip_prefixes cannot be displayed properly #498

Closed
opened 2025-12-29 02:19:07 +01:00 by adam · 1 comment
Owner

Originally created by @threerog on GitHub (May 2, 2023).

When ip_prefixes is 100.64.0.0/24, running tailscale status normally displays the IPs of all devices. However, when ip_prefixes is in other network segments, tailscale status cannot display the IPs of other devices,

Also, I have a question whether Hedascale supports multiple IPv4 ip_prefixes?
How to use multiple ip_prefixes if supported?

Originally created by @threerog on GitHub (May 2, 2023). When `ip_prefixes` is `100.64.0.0/24`, running `tailscale status` normally displays the IPs of all devices. However, when `ip_prefixes` is in other network segments, `tailscale status` cannot display the IPs of other devices, Also, I have a question whether `Hedascale` supports multiple IPv4 `ip_prefixes`? How to use multiple `ip_prefixes` if supported?
adam added the bug label 2025-12-29 02:19:07 +01:00
adam closed this issue 2025-12-29 02:19:07 +01:00
Author
Owner

@juanfont commented on GitHub (May 7, 2023):

Ranger other than 100.64.0.0/10 and fd7a:115c:a1e0::/48 (or their subnets) are not supported, and it can/will lead to odd behaviour.

This issue should be tackled in the Tailscale client.

@juanfont commented on GitHub (May 7, 2023): Ranger other than 100.64.0.0/10 and fd7a:115c:a1e0::/48 (or their subnets) are not supported, and it can/will lead to odd behaviour. This issue should be tackled in the Tailscale client.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#498