Just to confirm you do not have your rover connected to your home WiFi? If you do, forget the network and reboot.
2 Likes
My rover has never been connected wifi since she was born from the cardboard shipping womb.
2 Likes
Perfect!
2 Likes
Hi there, thanks for reporting this. To help us investigate further, please include the estimated timestamp of the issue in your support ticket so we can retrieve the relevant logs. If you’re not sure of the exact time, feel free to update the ticket the next time the issue occurs. We appreciate your patience and understanding!
Something odd is going on with my RTK. This is now the 4th time Halo has randomly crashed and fell back to 4G. Every time it’s happened Yarbo is inactive, just sitting on the charger and not being accessed at all.
I just discovered that when this occurs my Home Assistant becomes inaccessible on the local network. As soon as the RTK is rebooted, Halo is restored and my Home Assistant local works again.
I haven’t started digging into what’s happening yet - Is it just MDNS name resolution that’s failing, can I see it by IP, Is HA accessible remotely, for example. I’ll have to wait for it to happen again. Thoughts are welcome.
Some people have reported the DC cycling through tons of MAC addresses and it gets blocked by some network equipment detecting a port scan attack when this happens but that is a false positive. I think Ubiquity equipment has had the most issues with the DC from what I’ve seen. Also seen where people were blocking certain services it needed to work and it may have been a contributing factor to this behavior. I don’t know if Yarbo ever isolated the cause.
2 Likes
@yarbo-forum Sounds almost like mine. But never will never stabilize. Support sent me some things to check. Even though I had already done this, and it didn’t apply to me. But I humored them again. “This aligns with the issue you described, where the data latency keeps increasing. This is the result of the Data Center’s attempt to go online but failing repeatedly. We suspect that your home router might have placed the Data Center on a blacklist, which is blocking it from going online.”
“Please try logging into your router’s admin panel and add the following three MAC addresses to the whitelist. This should resolve the issue:”
HaLow MAC Address: 1e:9e:14:5f:a0:a8
Wi-Fi MAC Address: 78:22:88:b0:02:4a
DC MAC Address: 70:19:88:8e:1b:5a
I wish it would have been that easy. Then they did a patch, or fix remote. It was working. I was able to start mapping my large yard. Then the update, he heads for the trees, antennas break, and well he we are. Maybe it will he you. As for me I’m still waiting 
I’m using an Eero router. I added Reservations for the Wifi and DC MAC addresses (mine of course, not the ones you posted). I’d be surprised it that was it, but I’ll keep an eye on it report back if/when it happens again. So far, it’s been every week or two.
Adding the HaLow MAC doesn’t make any sense to me. That only applies for Core to DC connections. The router can’t see it.
1 Like
I haven’t had the latency issue at all. It’s almost always at 1 with the occasional flash to 2.
That’s strange. Why would it need to use dynamic MACs?
1 Like
well it doesn’t but they are using docker with several containers. It might just be something glitched that causes this condition when it can’t get a full internet connection.
2 Likes
Interesting. You’re chock full of little info nuggets 
1 Like
What dock is that in?
2 Likes
I bet I have read that document at least 3 times and completely glossed over on the docker…
2 Likes
My inventory fingerprints it as Ubuntu, FWIW.
1 Like
I don’t think it’s a reservation. I assume you are setting it to always get the same ip. I think they are thinking something is blocking the communication. When they say whitelist it, they are normally referring to always allow communication. It is normal as it is unlikely they know your equipment or what you may have setup. Normally though the only blocking comms on the same LAN is an ACL (layer 2). Outbound to internet would be different as it would pass through the router…
2 Likes
I don’t know what they’re suggesting, honestly. Hardware MACs shouldn’t be changing. This isn’t an iPhone.
1 Like
Well don’t forget there is a lot of virtualization going on in there too. But yes, hardware MAC’s should not change. I’ve only ever seen 2 MAC addresses and IP addresses on my network. DC and Rover. If you see 3, then you configured WiFi and should turn that off.
3 Likes