tailscale: iOS Tailscale client not connecting to Reolink camera
What is the issue?
I set up a Reolink camera(E1 Zoom) recently.
I assigned it a static IP 10.0.1.XX.
I have tailscale clients on my:
- Synology (exit node, subnet advertising)
- iPhone
- iPad
- Mac Studio
Then on my Synology tailscale nodes, I ran: tailscale up --advertise-routes=10.0.1.XX/32,10.0.1.YY/32 --advertise-exit-node
Now, when I connect my iPad and Mac Studio to a non-local area network (cellular hotspot or another Wi-Fi network) and enable Tailscale without enabling the exit node, I can access my Reolink camera using the Reolink client(MacOS) and the Reolink app(iPad). ✅
Now, when I do the same with my iPhone, I can not access the camera. 🔴
But when I enable the exit node, I can. ✅
I can ping the IP of the camera from all devices with and without enabling the exit node, but I am confused as to why on iPhone, I have to enable the exit node to access the camera.
Hunch: The iOS client of Tailscale only allows TCP and not UDP, but when you enable the exit node, then all calls are routed to the exit node and hence it works. But then why is this not happening in iPad? I would have assumed that iPad would be a fork of iOS.
Steps to reproduce
- set up a Reolink E1 Zoom camera
- switch your iPhone to a non-local area network
- turn on tailscale VPN
- try to access camera using the reolink app
- enable exit node
- try to access camera using the reolink app again
Are there any recent changes that introduced the issue?
No response
OS
iOS
OS version
16.6.1
Tailscale version
1.48.2
Other software
No response
Bug report
No response
About this issue
- Original URL
- State: open
- Created 3 years ago
- Comments: 20 (4 by maintainers)
I was able to reproduce this issue with a Reolink Duo 2 camera and my iPhone. I can access the camera dashboard via the camera’s IP address and through Tailscale, but it does not work with the iOS app. When I use the subnet router as an exit node, the iOS app works.
@Cyphs, IOS 18.2!
That is a whole different story then, and is most likely caused by the fact that multicast traffic (often used for device advertisements) is not routed through Tailscale.