Open Network Issue With Cat-M

The Hologram Network Team has identified an issue with TCP settings on the carrier side that only affects Cat-M and only in certain areas and certain carriers with certain servers. We’re working with the carriers to resolve the issue and hope to have more information soon. We appreciate your patience on this and those of you who have submitted diagnostic reports to us as these were helpful to help look into the issue.

In the meantime, there is a workaround to use PPP instead of the TCP stack on the modem itself which is what calling the connect function does. Note that doing this does open you up to the possibility of increased data usage since it may cause extra traffic to be routed over that connection. Just something to be aware of and keep an eye on.

We’ll keep you all posted as we work with the carriers to resolve this issue.

For more information about using PPP for this, one of our community members has a helpful post here: switching from NOVA-U201 to the R410M - Failed to Connect

Also can run sudo hologram network connect and sudo hologram network disconnect

Can you confirm this is isolated to the TCP stack and doesn’t affect the UDP stack on the R410M? My concern is if this is a NAT thing or any issue in the Network Layer vs TCP implementation in the Transport Layer.

Based on our side of the investigation so far, this looks like it should only be an issue with TCP but if you’re noticing anything with UDP please let us know.

Any idea when this issue will be resolved? We can confirm that both Verizon and AT&T are not working in Los Angeles area for AWS cloud. But it works for Azure and GCP.

Yeah, understand the frustration here. We’re still working on it with various partners. Its been a bit of a hassle trying to figure out where across the maze of networks things are going wrong. We are basically zeroed in on a cause though and are pushing for a resolution. We’re hoping to have a more solid update for everyone next week.