One of the biggest reasons I moved from my prior DVR setup to a Tablo was the ability to remote stream while traveling. I recently switched from a cable internet provider to a fiber internet provider. My new fiber internet provider apparently uses CGNAT, everyone in district has the same external V4 IP. Tablo Connect no longer worked.
(Apparently I can’t post more than a single link, search “Greenlight changes NAT, kills inbound connections”
The answer, thanks to several networking nerds help was to:
Install Tailscale on my chromecast and on a spare windows PC as a router
Make the windows PC a router and advertise it as an exit node
Note in the instructions below he details making a Linux box a router, that is no longer required, it works fine with a windows PC. Unlike the author I always need to connect using the VPN as the issue I am fixing is the CGNAT issue.
Hi. I’ve been searching for the same solution. I have Starlink which uses Cgnat. I have a windows box which I have enabled as an exit node and advertised the routes using subnet router documentation but my Tablo unit is still unable to connect behind cgnat. With or with out exitnode on
CGNat is a PITA to deal with when it comes to in/out traffic. Unless you have a decent router that can handle some stuff. OR if you’re a complete tech geek (I am)
1st thing (Non Star Link ISPs ask them if they have a static IP package, it may cost more, most of the time it’s like $30 extra), the easiest, upgrade to a Starlink business account and you will get a public IP address. The public IP isn’t static and it will change every 30 days.
2nd thing, you could run a reverse proxy server… Caddy Server maybe the easiest if you have some computer skills. There are other free companies out there that do the same.
3rd thing, Tailscale.
4th thing, go full IPV6 on your WAN and LAN. Unless you’re a decent network tech/engineer, i wouldn’t advise this.
This is def not Tablos fault… this is completely Starlink’s config. A lot of people have to overcome this issues for many reason.
@Royboy06 , Can your client connect locally to Tablo when on the same network ok?
If so then the you must run the command on the windows machine
tailscale up --advertise-exit-node --advertise-routes=xxx.xxx.xx.0/24 where the XX are your local network IP specific
You then must enable the endpoint in the tailscale web console
Then on the client you must open tailscale and instruct it to use the endpoint
I will add that after posting these instructions I experienced buffering when streaming remote, I tracked it down to the chromecast client not having sufficient processor power and storage to both run tailscale and the tablo client.
I switched to using a fire tv stick 4k max and it worked fine for several months remotely after that.
The reason I selected the fire stick 4k max was due to this processor benchmark