Closed Mark3xtrm closed 3 weeks ago
did you have this issues with the prior stable version (0.22.3)?
Just wanted to mention that I recently began configuring headscale as a transition from tailscale. I experimented with this specific situation using my iPhone and encountered the same problem. It didn't connect over cellular, so I had to turn on wifi again for it to connect. Once connected, I can turn off wifi and it seems to work fine over cellular. I'm running headscale (v0.22.3) in a Proxmox LXC. iPhone Tailscale client version is 1.66.3.
This issue is stale because it has been open for 90 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
Hi guys, I implemented the latest headscale with the latest client for iOS on an iPhone and iPad and the same thing happened on both. As mentioned by @timmyb824 enabling the VPN while on wifi and then turning it off makes the device connect to the advertised nodes and subnets.
Is this a support request?
Is there an existing issue for this?
Current Behavior
Probably it's me and I can't figure out how Headscale (btw nice piece of sw) works but this is what happens and idk if it's normal:
*(I'm not sure if this it's always the case when rebooting the phone)
Currently, these are my nodes
And these are my routes
Idk if this too is normal but: when I paired my devices, none of them automatically appaired in the routes list, and I had to add them with the advertise command. I did this with my Linux PC (
srv
) and my Android phone (rn7-mrk
) with the "Run as exit node" on this one. Off course I can't do this on iOS as the Tailscale doc says. Idk if I have to at least advertise all nodes in the Headscale net to make it function properly and to avoid the problem aboveExpected Behavior
I expect to be able to connect to the Headscale mesh network even using only the data connection, even after a disconnection from it through the toggle in the Tailscale app
Steps To Reproduce
Environment
Runtime environment
Anything else?
No response