I switched to T-mobile home internet, now my rover is offline and data center connection is a 3. Any easy solutions?
Data center light is green, has hallow, just now no internet connection.
Did you hard power everything down before moving the DC connection? If yes, and it still doesn’t work, connect the core to your home WiFi and turn on cellular. I’m guessing the latency is too much for RTCM to use Yarbo’s internet servers vs local HaLow.
2. T-Mobile Firewall & IP Blocking
Because T-Mobile Home Internet lacks a public IP address, it aggressively blocks unauthorized outbound traffic, which often triggers an automatic security block on the Data Center: [1]
- Check the T-Mobile App: Open the T-Mobile Internet app and check your connected devices list. Ensure the Yarbo Data Center has not been automatically paused or placed on a blocklist
Found this but not sure what good it does me.
That makes no sense. How does a lack of a public IP address aggressively block unauthorized outbound traffic? Yarbo isn’t doing anything that requires a public IP address assigned to the DC. No one would have that in their home network.
I can tell you that I had a similar issue when I swapped to a new router with a new IP scheme for the internal network. Everything was offline until I powered everything off and it all got new IP addresses on my new internal network.
I tried powering it down and up two times, nothing. Hooked just the dc back to starlink and good to go. Now I am going to have to contact someone, but which one of the two yarbo or t-mobile?
Found this also…
Isolate with a Mesh Node / Extender: Many Yarbo users resolve T-Mobile Ethernet drops by plugging the Data Center into a secondary Wi-Fi extender or a mesh router node (like an Amazon eero or TP-Link) rather than plugging it directly into the T-Mobile gateway. The secondary router acts as a buffer and handles the data packets more reliably
That sounds more likely.
Does the T-Mobile router do 100Mbps? Do you have a link light? The DC can only do 100Mbps.
Don’t know the specs, you can’t do anything on this thing. Link light was blinking. I don’t have it plugged directly into t mobile there is two switches in between. Only thing I changed was taking my main ethernet cable out of starlink and plugged it into t-mobile. All my other wire stuff works. I have like 14 bitcoin miners running just fine on either provider.
They may be blocking something or blocking outbound DNS to any DNS server other than theirs.
T-mobile of course says it is nothing on their end, doesn’t see any blockage of anything. Their gateway is not like a normal router, there is nothing I can change on this end. They say to call yarbo.
Got a spare router you can throw behind it to put the DC on?
I have an older tp link mesh setup. I got it to work hooking the dc into one of the mesh nodes. But I had to connect wifi to the rover to get it to work. I could then delete the wifi off the rover and the connection stayed a 2 and I sent yarbo out to work. I tried a tmobile mesh node but I couldn’t get it to work. I will have to play with it more tomorrow am as I wanted to get more grass cut so I only had so much time to play with it. More rain is headed here tonight.
I love technology, but when it don’t work it is very aggravating. Spent most of my day on this tmobile stuff.
Yeah, meshes can be finicky with IOT devices. Especially Yarbo. That’s one of the reasons I never recommend connecting the core to WiFi.
I hope I can at least get it to work on a tmobile mesh node. It really sucks having a whole extra wifi mesh running just to get internet separation. At least with tmobile’s node it would be the same network.
For sure
Spoke to soon back to connection 3. Back to starlink she goes. I really want tmobile to work, others have it. Not sure if it is the new version of router or what that others have it working and I can’t.
Connection 3 will work (local HaLow mode AKA offline mode), but the core needs some other way to get internet access at that point, like WiFi or cellular. My guess is, local mode is just less latent than Internet for the RTCM data.
Called Yarbo, they say everything is working on their end. On the line with Tmobile again…