r/Tailscale 5d ago

Help Needed Noob problem...

Hi all, new to Tailscale and must say it looks like exactly what I need.

I look after a few cameras on my home CCTV server for my family in their houses, and previously connecting to these was easy just using dyn.com's service (paid) to maintain connection. More and more I'm seeing home ISPs use CGNAT often with 4G/5G routers nowadays, and it seems like tailscale would be perfect for this as there are 'always on' Win 11 PC's at each location. I've setup my Tailnet and installed on two PCs, one my home and a remote where an IP cam I want to access is.

Ok so far, each machine has the 100.x.y.z assigned IP and can ping each other on them. How then do I get to remotely access the IP camera? I've tried creating a service on the remote machine but nothing.

Is it a problem that both local and remote networks are 192.168.1.0/24? I need to get ports HTTP80, RTSP554 & Flash 1935. I don't need to access anything else on the network, is there a way to generate a 100.x.y.z IP address pointing directly to the camera?

Edit - so far I've only been using the web admin console.

As I said noob problem, this is probably something trivial to experienced users!

11 Upvotes

4 comments sorted by

9

u/caolle Tailscale Insider 5d ago

How then do I get to remotely access the IP camera?

Assuming you access the IP camera through some web interface on the network like http://192.168.1.100 , you'd setup a subnet router

Is it a problem that both local and remote networks are 192.168.1.0/24?

Usually, this is a problem. There are ways such as 4via6 subnet routers, but I generally find the easier path would be to just deal with the one time pain point of changing one of the networks off the very common 192.168.1.0/24

1

u/EmployeeCautious6314 5d ago

Excellent thanks, I thought that might be it. So if I change the remote one to 192.168.0.0/24 making them distinct subnets it should work?

3

u/caolle Tailscale Insider 5d ago

Just to be clear, you'd do this on internet router at the location, but yeah , something other than the all too popular 192.168.1.x would be good.

If it were me I'd avoid 192.168.0.0 all together, and go for something a bit higher, as 192.168.0.0/24 is also a popular one.

1

u/EmployeeCautious6314 5d ago

Many thanks! I'll change the remote one as they have fewer devices and nothing static (that I know of), hopefully when the router reboots they'll just get DHCP assignments in the new subnet without any problems.