ingenium

Hopefully. Though it won't help upload failing due to low signal, which is very common. We need FDD-TDD CA. When they deploy that it's going to make such a big difference. Sent from my Pixel 3 XL using Tapatalk

Interesting. If I have a very weak LTE signal on wifi calling, it will sometimes drop LTE (or rather, it doesn't try to get it back once it drops on its own). If a call comes in, then I think it reconnects to LTE to allow a handoff to the macro if wifi drops. Otherwise, I maintain LTE with wifi preferred. It just doesn't update very often in SCP. Sent from my Pixel 3 XL using Tapatalk

We'd need to see how the Eero software is configured. It just seems like something isn't right with your setup, and I'm not sure what it is. Can you post the IP addresses of a few devices connected to the switch? Just to make sure that everything is getting a local IP. I would delete the forwards. What IP are you forwarding them to? Remember the Airave 4 has two IPs, so either way you'd only be able to forward to either CDMA or LTE, not both. They each use an independent ipsec tunnel using ports 500 and 4500. So at best the forwards would only work for one. Sent from my Pixel 3 XL using Tapatalk

It should be supported day 1. If you have an old phone you can swap to, it's a 5 minute process to switch to eSIM. Definitely worth it if you ever use a SIM from another carrier. Sent from my Pixel 3 XL using Tapatalk

You shouldn't need to port forward. And in fact, you can't with the 4. It's assigned two IP addresses, one for LTE and one for CDMA. Both use all of those ports, and you can only forward to one IP. I hate that Sprint gave that forwarding advice. It may break other things (53 is DNS and 68 is DHCP). What they meant to say was make sure that those 4 ports aren't blocked outbound on your firewall. Which unless you're on an enterprise, corporate, or public network, they won't be. You would have had to explicitly block them. Outbound on those ports is always allowed by default. Sent from my Pixel 3 XL using Tapatalk

I don't think so. This would break Vowifi -> VoLTE handoffs. I don't experience this on my 3, nor do other people. It could be that LTE is too weak at your location and not stable? I say that based on how low the signal bars are for you while one 1x. Sent from my Pixel 3 XL using Tapatalk

The eSIM works on phones purchased from Google. I'm using it on mine. The issue is that you can't migrate directly from physical SIM to eSIM on the same phone. You have to first swap to a different/old device, remove the physical SIM from your 3, and then setup the eSIM on it (select add, then select Sprint). The phone will have you sign into your Sprint account and select which line you want to use, and that's basically it. The issue I believe is because the IMEI is already in use and tied to the physical SIM, so it won't let you swap the IMEI to eSIM while in use. By swapping to a different device first, it frees up the IMEI to be linked to your eSIM. Sent from my Pixel 3 XL using Tapatalk

Why don't you just sign up for a plan with Calyx institute? It's $500/year I think and is unlimited on Sprint. No deprioritization. You can get a Sierra Wireless modem and put it in a USB enclosure, and then just stick the SIM in it. You don't need to do a device swap with Sprint. Or get the AT&T iPad plan (use an IMEI generator to get an iPad 4 IMEI). $35/month, also unlimited, but subject to deprioritization. My parents do about 200GB/month over it and haven't seen any deprioritization (they're in a rural area on an uncongested tower). There are ways to get unlimited plans without overages where you don't have to mess with load balancing and expensive plans. Edit: Check out this thread for more information on hardware and such https://s4gru.com/forums/topic/7844-build-your-own-devices-routers-relays-iot-etc there are a few of us that can give you advice. For my build, I picked up two of these antennas from LTEfix https://ltefix.com/shop/antennas/4g-lte-antennas/directional-panel/700-2700mhz-15dbi-4g-lte-directional-antenna/ for use with my Sierra Wireless MC7455. They work great. While the MC7455 is the only Sierra Wireless modem that supports all 3 Sprint bands, I wouldn't recommend it for Sprint because it has a bug that causes it to disconnect 1-2 times a day, requiring the modem to be power cycled. Other Sierra Wireless models don't have this issue, and you can get one with 3xCA B41 if you don't need B25.

I guess it comes down to what the default behavior is on most consumer hardware. I'm not sure if the DMZ there is isolated from the main network? My understanding on consumer hardware is that it's assigned a LAN IP, but all non forwarded ports on the WAN IP go to the DMZ device. It's a hack to avoid port forwarding or when you don't know which ports to forward, and is a security issue. Or at least that's the way I've seen it behave on a lot of residential routers. On more enterprise hardware, I know DMZ behaves as you said, offering an isolated place to put untrusted equipment away from your primary network. Basically acting as a separate vlan. But I'm guessing for the average user, their DMZ won't behave this way unfortunately. For anyone with capable hardware, I would recommend putting the Airave on its own vlan, with access to your other vlans blocked. That's the way I run mine. Sent from my Pixel 3 XL using Tapatalk

Calling+ is not a good proxy for VoLTE. It's night and day difference. VoLTE will never suffer from congestion. Calling+ is impacted severely by it. If you're moving (such as in a car), I've noticed the network will move you to B26 to minimize handoffs and cutouts while on a VoLTE call (remember, congestion doesn't affect VoLTE. It's as though B26 is unloaded). The network doesn't know you're on a Calling+ call, so you'll get stuck with B41 unusual upload, etc, and the call will cut out. As an example, I was in a subway station waiting for a train. There was a DAS with B25 and B26 only. Data was literally unusable. I couldn't even send a message in a chat. 0 throughput. Yet a VoLTE call I did was crystal clear. Read my wall post if you want a technical breakdown of the difference https://s4gru.com/entry/439-sprints-casting-call-of-voice-over-actors-an-in-depth-analysis-of-volte-calling-and-vowifi/ Sent from my Pixel 3 XL using Tapatalk

Partially. On the 3, because it had broken IMS on LTE after the final software update (broke calls and texts on eCSFB devices), I blocked the LTE ipsec tunnel at the firewall. This resulted in LTE being disabled and it regularly tried to re-establish the tunnel. If I removed the firewall rule, LTE would come back up in a few minutes. I tried the same on the 4 (I forget the reason why), which was easier since the CDMA and LTE sides are assigned separate IP addresses. On the 3 I had to block by destination IP address (the LTE tunnel used a hard coded IP address. This isn't the case on the 4). If communication is interrupted, the Airave will repeatedly try to re-establish the tunnel. I'm not sure if Sprint's side tries to do anything. I'm sure if the NAT entries are still there, Sprint's side would be able to bring the tunnel back up (or at least trigger the Airave to re-establish it), but since the Airave tries regularly anyway I'm not sure if this would have much benefit other than making it reconnect a few minutes faster. Sent from my Pixel 3 XL using Tapatalk

Turn on developer mode (Google instructions) and enable the option "mobile data always active". That should fix it. Sent from my Pixel 3 XL using Tapatalk

Yup. They also work fine when forced (with a Magisk module to basically ignore the VoLTE enabled flag). Same for Airave 4. The issue is that the relay connection from the MB to the donor is a single EUTRA session, with no way to prioritize VoLTE calls. If the donor is congested, then VoLTE call quality goes to crap and no one can understand each other (I know from experience). That's why it's behind held up I assume. Sent from my Pixel 3 XL using Tapatalk

Yeah, we're seeing this in Pittsburgh too. Dead giveaway that the site has been upgraded to MMIMO. Sent from my Pixel 3 XL using Tapatalk

I did a packet capture on the Airave 4 (and 3). There are no inbound connection period, only outbound which will work fine with NAT. I can post a copy if anyone is actually interested and wants to dig through it on Wireshark. For the typical home user, there is no reason that it needs to be in a DMZ. The ports listed are just the ports that it uses (outbound), and they must be set to allow outbound traffic on. Interestingly they leave off UDP port 123 (NTP), so it's possible that it's not actually required and it will just synchronize time over the IPsec tunnel once it's established. NTP is one of the first things it does though. I'm guessing the DMZ suggestion may be for corporate networks or other networks that may block outbound IPsec or are overly aggressive or restrictive. It's a catch-all, basically a way to guarantee that it will work. Port 53 is DNS (incoming not required, it just needs to be able to lookup hostnames and get responses), 67 is DHCP, and 500/4500 is UDP encapsulated IPsec IKEv2. IPsec helper on the firewall isn't needed, since I don't think it even attempts to use ESP and just goes straight to UDP. I see no reason why it wouldn't work even with double NAT. The only potential issue would be if the UDP NAT timeout is set too low and the NAT entries are removed before a keepalive packet is sent, but it would have to be a pretty low timeout (less than 30 seconds probably). So it will be fine just sticking it behind the router for almost any home user, and if not, then whoever setup the network will be competent enough to be able to fix it and relax the firewall rules.

I *think* with a 3a you might see LTE but not be able to authenticate on it. It's tough to say. Typically with Sprint phones, they will stick to 3G when inactive, but the 3 is a bit different with the ISIM. With mine, before the "hands free activation" ran to setup CDMA, it connected to LTE and had usable data (the SIM was associated with the line though), but calls wouldn't work until hands free activation ran a few minutes later. I don't know how well it would work tho, since I'm assuming you wouldn't get band handoffs, so you might just be on a single band. You might also have to force the phone into LTE only mode. Sent from my Pixel 3 XL using Tapatalk

It's possible that your router is blocking it for some reason. Are there any restrictions on your internet? Any filtering? Forced DNS? Network wide VPN? Network wide Tor? Anything out of the ordinary? Sent from my Pixel 3 XL using Tapatalk

Good info. I was wondering if there was a limit on the "unlimited" high speed roaming data. Sent from my Pixel 3 XL using Tapatalk

Since you mention ACL logging, I'm guessing you might have a more advanced switch? If so, you could do port mirroring on the switch and then run Wireshark (in promiscuous mode) on a computer connected to the mirror port. In my case I just ran Wireshark on my router on the vlan that only contains the Airave. That being said, you can try whitelisting those IPs. Or another option is to set a NAT rule to force all traffic to go through OpenDNS, while letting clients think they're using their hardcoded servers. I do this on a couple of my vlans. It's a preferable option to just blocking non OpenDNS traffic.

Was just about to edit my post. Turns out they're not hardcoded. I just found out that 71.252.0.14 is a Verizon fios DNS server. I forgot that I set my Airave VLAN to not use my local DNS server, but rather just pass along whatever my ISP assigned. So in that case I guess it does just use the DNS server assigned via DHCP. I have no explanation for the other 2 though.

So far I've seen 71.252.0.14, 10.192.132.119, and 10.192.4.119. Typically it only uses the first one, but for some lookups, it queries all 3 at the same time, but it only gets a response from 71.252.0.14 (at least on my network).

You need root and need to use a Magisk module to enable the Diag port https://forum.xda-developers.com/pixel-2-xl/how-to/guide-qxdm-port-activation-pixel-2-xl-t3884967 I don't believe you need the custom Magisk binary, just the module. It will allow band locking with the free version of Network Signal Guru. Be aware that on the Pixel 3, several of us have had USB connectivity start getting flakey over a few months and eventually stop working all together until the module was disabled. No idea why it gradually happens. But you can disable the module and reboot to get USB data connectivity back. Sent from my Pixel 3 XL using Tapatalk

Sprint can easily fix capacity on some sites if they wanted to, with the opex expense. There's unused B41 that they could have deployed on just some sectors (such as ones covering stadiums and venues, where the current sectors are overloaded to the point of not working at all). Most Sprint sites don't even have the backhaul to fully utilize the spectrum that is on air. Not to mention the lack of rank 3 and 4, meaning they don't get the speed boost from 4x4. They probably figure there's no reason to enable it since they don't have the backhaul for it anyway. There are lots of ways Sprint could add capacity without adding macros, but they don't. Sent from my Pixel 3 XL using Tapatalk

They have a lot deployed in Chestnut Ridge, NY at least. I was in that area last summer and found a ton. These are just a few that I marked in a residential area, but riding in the car I kept connecting to them everywhere. Sent from my Pixel 3 XL using Tapatalk

You can set quotas and limits on the Google APIs. You can even have it alert you when you reach a certain threshold, so you know when you're approaching the quota that you've set. Sent from my Pixel 3 XL using Tapatalk