ingenium

On my Pixel 3 XL, there was CA on the first 2 carriers as usual, but no CA at all with the third. It was a non contig 20 MHz carrier. Sent from my Pixel 3 XL using Tapatalk

Is it contig? In SF some higher usage sites got a third, non-contig carrier to presumably help with load. Sent from my Pixel 3 XL using Tapatalk

I would be really curious to see your packet captures. 68.28.x.x is CDMA on my Airave 3 and 4, and 68.31.x.x is LTE (and wifi calling). It seems like yours doesn't fit that in CDMA nor LTE. Definitely report back the IPs that you discover. You can also let it power on and dump the state table on your firewall. Look for the two connections on UDP port 4500. That's a quick and easy way to grab the IPs. Sent from my Pixel 3 XL using Tapatalk

I don't believe so. None of the Airaves have. I also heard that 1x HD Voice does not work on any device which supports VoLTE (including devices which support it but don't have it enabled yet, such as the S9). It has something to do with the way calls are routed in the backend, VoLTE capable devices are routed differently than non-VoLTE ones. Sent from my Pixel 3 XL using Tapatalk

For mine it took about 1-2 days before phones would even see it in neighbors. Then they started connecting to it about a day later. Basically, I think there's some sort of automatic integration that has to go occur at the network level. I say this because when it was finished, my MB had changed PCIs. I think anytime a device like this comes online, all the others like it in an area change PCIs. Small cells behave the same way. Sent from my Pixel 3 XL using Tapatalk

Did you notice the TAC change? Sent from my Pixel 3 XL using Tapatalk

I think dd-wrt may actually be one of the firmwares that does restrict it, or at least has an option to. I haven't used dd-wrt in 10+ years though so I'm not sure where it would be in the settings. If your mom has Chrome, you can use Chrome remote desktop to remotely connect to her computer and browse through the router settings yourself. Sent from my Pixel 3 XL using Tapatalk

You shouldn't need to change anything on your router. It's just saying that those ports shouldn't be blocked. The Airave uses UDP encapsulated IPsec, so it should just work out of the box for most people. The Airave 4 to does not provide wifi. The 3 did. Sent from my Pixel 3 XL using Tapatalk

CDMA likely needs GPS to come online. Are there any obstructions outside the window that might block the signal? If so, she might want to try a different window. I'd also have her unplug it and plug it back in to make sure it's in securely. When I plugged my antenna in, it got a GPS lock within a minute. Worst case, have her power cycle it and let it sit overnight. New satellites will pass overhead that it might have better luck locking onto. Once it gets a lock, I don't think it needs to get it again until it's power cycled. Edit: is LTE up? If so, there's also a possibility that your router is only allowing each MAC address to have a single IP. I think I've seen a few routers configured that way before

I'm guessing that it's using 5G as a secondary/tertiary carrier, and that LTE is PCC (so it can use it for upload). Sent from my Pixel 3 XL using Tapatalk

It is. Macro 1x is garbage in most areas and has been for years. They've cut CDMA carriers so much that they're too overloaded. As a result, quality is dropped to support more calls rather than dropping them or having them fail. The more calls there are on a macro, the worse it gets. I switched to Google Voice when possible for calls about 4-5 years ago because the robo garble and poor quality made it unusable. 1x800 seems to be worse than 1x1900. That's the only reason I have an Airave actually. Pixels (before the 3) didn't support wifi calling, and even though my macro 1x signal is -75, I needed an Airave to use 1x for calls. The difference is night and day. Sent from my Pixel 3 XL using Tapatalk

It does work with VoLTE actually, but it's likely not on the whitelist yet, so it needs to be forced. Unlike the Airave 3, it actually works. The 3 would work for a bit, then break all calls and SMS. I'm guessing Sprint won't "allow" it (by whitelisting it on phones) until they launch it network wide, but it does work. Sent from my Pixel 3 XL using Tapatalk

I can confirm that you can't edit the site notes for it in the most recent beta. I receive the same error. Sent from my Pixel 3 XL using Tapatalk

Yes, no one needs that speed on their phone. But I see it as a proxy for how much capacity is available, since the network is currently unloaded. So in that sense, 800+ Mbps means that a site can handle a lot of traffic without getting congested, vs 400 Mbps means it can absorb about half as much traffic before becoming congested. Sent from my Pixel 3 XL using Tapatalk

Got my Airave 4 and have it setup. It uses the same earfcn as my Magic Box, 39874. CDMA 1x uses channel 1125, which is right in the middle of the 15x15 B25 carrier, so I'm guessing it's misconfigured. I ran a packet capture on it during setup. It requests 2 IP addresses, one for the CDMA side and one for LTE. This is in contrast to the Airave 3 which used a single IP. So the internals are very much completely separated on the 4, much more so than on the 3. Both IPs are for the same MAC address (ie, the Airave 4 ethernet port has a single MAC, but 2 IPs assigned). At startup, the CDMA side does an NTP query to the hardcoded, private address 10.1.2.40 for some reason, before falling back to querying the NTP pool. The LTE side also queries the pool, but does not try the hardcoded address first. The CDMA side then looks up SEGW-Airspan-Combo-3G-GLOBAL.SPCSDNS.NET and opens an IPsec tunnel to it. It then looks up segw06.femto.sprint.net and establishes an IPsec tunnel to that address. This is the same domain range as the Airave 3. Valid options seem to be segw01.femto.sprint.net through segw10.femto.sprint.net. This tunnel is what is used for CDMA, so I'm guessing the first tunnel was used for configuration? The LTE side looks up SEGW-Airspan-Combo-GLOBAL.SPCSDNS.NET and establishes an IPsec tunnel to it. It then looks up SEGWAKR-PUBL.sc.spcsdns.net and establishes an IPsec tunnel to that address. I believe the latter is the tunnel for LTE, and the first is the configuration tunnel. The LTE side is similar to what is seen on the MB Gold. The Gold first establishes an IPsec tunnel to SEGW-AIRSPAN-IFUR-GLOBAL.SPCSDNS.NET, and then a tunnel to SEGWSKT-PUBL.sc.spcsdns.net. Note the similarities in the addresses. It's also interesting that the Airave 4 uses hardcoded DNS servers, querying 3 of them at the same time for the final IPsec tunnel.

Nothing besides doing an airplane toggle Sent from my Pixel 3 XL using Tapatalk

Either there was a super low signal, or B41 LTE was very congested. While 5G was empty. Not really impressed with the 5G speed seeing as no one else was on it. Maybe the site doesn't have enough backhaul? And that definitely looks like B41 LTE for upload on 5G. Sent from my Pixel 3 XL using Tapatalk

What shows up on your account? Does it work? Sent from my Pixel 3 XL using Tapatalk

They don't even provision the backhaul at many sites to fully utilize the B41 on air. There's no point in putting even more on air if they don't give it enough backhaul. Sent from my Pixel 3 XL using Tapatalk

Now that's interesting, and could be the issue. On Verizon my Pixel 3 will turn off CDMA, but on Sprint with VoLTE it keeps CDMA on and maintains SRLTE. So if I start to roam, presumably it will quickly drop to CDMA. For some reason it sounds like that isn't happening on your Samsung phone. I'm surprised it turns off CDMA actually. Sent from my Pixel 3 XL using Tapatalk

In that case I'm not sure. I won't have mine until the end of the week, so I can't do a packet capture to analyze. I'd say just leave it overnight and see if it's working in the morning. Sent from my Pixel 3 XL using Tapatalk

Same MAC address, but it uses 2 IPsec tunnels. It's possible that the LTE one is getting blocked. On the 3 it always initiates the CDMA side first, so if your network only allows 1 IPsec connection per device for some reason, it would explain why the CDMA side works. I'm pretty sure it doesn't need ipsec passthrough help, since it defaults to ipsec over UDP, but I could be mistaken on that. Sent from my Pixel 3 XL using Tapatalk

That's connected to the Airave? That looks like a macro earfcn, 41374. The last Airave always used the first carrier earfcn, but it appeared that this one would use the MB earfcn. Now that seems less certain. What are the macro B41 earfcns in your area? It also looks like the CDMA side supports 1xAdvanced (and presumably HD voice). Sent from my Pixel 3 XL using Tapatalk

I'm not sure what you mean by this. If you are actively using LTE on it, then it will reduce the speed available to other devices. Just like if you were on wifi and using data. For example, if your home internet is 100 Mbps, and you're doing a speed test or something else that is consuming 40 Mbps via the Airave, then there is 60 Mbps left for other devices on wifi. But if there is no active data transfer occurring via the Airave (ie your phone is idle), then it won't be using your internet. It's basically the same as if your phone was on wifi. Sent from my Pixel 3 XL using Tapatalk

With wifi preferred it should always use wifi calling. At least mine does. The only time when it didn't seem to use it was when I connected to WiFi that was using an LTE modem connected to a magic box. For some reason it didn't really like that combo. If it's not working, then my guess is that something is blocking or interfering with the ipsec tunnel on your wifi. Or the wifi signal is too low or there are other problems with it. It's possible it won't use it if it determines that the connection isn't stable/good enough. Sent from my Pixel 3 XL using Tapatalk