-
Notifications
You must be signed in to change notification settings - Fork 57
Open
Description
I have a Cradlepoint is on a remote network with subnet of 192.168.1.0/24. There is another device on the subnet at 192.168.1.140 that I am able to ping at the NetCloud console from the Troubleshooting tab but when I try to access it through Tailscale I am unable to access it.
I've tried enabling the route on the Tailscale web UI and pinging directly at 192.168.1.140 from another device on the Tailnet and I've tried using 4via6. Both result in this showing up on the logs:
Thu Nov 14th 15:01:48 2024 tailscale ERR 2024/11/14 20:01:48 netcheck: DetectCaptivePortal(found=false)
Thu Nov 14th 15:01:32 2024 tailscale ERR 2024/11/14 20:01:32 exec ping of 192.168.1.140 failed in 3.919646ms: exit status 1
Thu Nov 14th 15:01:27 2024 tailscale ERR 2024/11/14 20:01:27 exec ping of 192.168.1.140 failed in 5.042896ms: exit status 1
Thu Nov 14th 15:01:22 2024 tailscale ERR 2024/11/14 20:01:22 exec ping of 192.168.1.140 failed in 3.623354ms: exit status 1
Thu Nov 14th 15:01:17 2024 tailscale ERR 2024/11/14 20:01:17 exec ping of 192.168.1.140 failed in 4.037542ms: exit status 1
Thu Nov 14th 14:31:49 2024 tailscale ERR 2024/11/14 19:31:49 exec ping of 192.168.1.140 failed in 3.934125ms: exit status 1
Thu Nov 14th 14:31:44 2024 tailscale ERR 2024/11/14 19:31:44 exec ping of 192.168.1.140 failed in 4.030021ms: exit status 1
Thu Nov 14th 14:31:39 2024 tailscale ERR 2024/11/14 19:31:39 exec ping of 192.168.1.140 failed in 3.637541ms: exit status 1
Thu Nov 14th 14:31:34 2024 tailscale ERR 2024/11/14 19:31:34 exec ping of 192.168.1.140 failed in 3.607541ms: exit status 1
The Cradlepoint is running OS v7.24.22. Do I need to modify the Network settings on the Cradlepoint to enable the route?
TIA,
Ben
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels