ingenium

I swear you're a troll, because I'm honestly in disbelief if you actually believe what you say. ISPs get more revenue by charging for faster service! Not based on what the service is used for. That's how the backbone providers work, and that's how the industry has always been priced, that's how data centers work. That's how Comcast, Verizon, etc pay for their own bandwidth at transit points to peers. ISP "packages" would be akin to the electric company wanting to charge me one price for electricity that goes to my Samsung TV, but a different price that goes to my Vizio TV or to my computer, despite them all using the same quantity of electricity. Thank God I can easily switch electric companies! . The entire concept is absurd, and in a properly functioning market it would be a complete non issue, since no ISP would be stupid enough to even attempt it. Except, we are not in a perfect, competitive market. We're in a monopolistic market, one that's government granted in many areas. A government granted monopoly comes in exchange for proper regulation. That's the only way the system works. I fail to see the regulatory burden that you claim net neutrality would impost on "startup ISPs". It's actually more work to maintain fast and slow lanes! Use QoS on a per customer and on a general, indiscriminate bandwidth level, based on the bandwidth they purchase. Just sell bandwidth at a certain price, and if you're not making money, then raise the price. Don't charge me one price for using 100GB for Netflix, someone else a different price for 100GB of YouTube, and another person a different price for backing up 100GB of files. Build capacity to handle the bandwidth that you sell to people. Plain and simple. And I'm not even going to get into all the money the ISPs took from the government to fund broadband expansion, which they then just pocketed and never fulfilled. Sent from my Pixel 2 XL using Tapatalk

My guess is Sprint is done with it. They have the magic box + calling plus, and the new Airave provides wifi as well as CDMA and LTE. No sense in giving out the router anymore when they can just give out the Airave 3 instead. I think the router was a stop gap for not having an eCSFB capable Airave. Sent from my Pixel 2 XL using Tapatalk

Comcast shouldn't be blocking it. From the way you described it, it sounds like possibly the UDP NAT connection timeout could be too low on your router, resulting in the VPN tunnel being dropped. That, or it's a defective device. Timeout settings are an advanced setting in routers, and I don't think most make it accessible. The defaults for most routers should be fine though, unless you're doing lots of torrents or P2P that utilizes lots of connections (which would cause the lookup table to get full and drop the VPN connection) It should, LTE should be seamless handoffs. Sent from my Pixel 2 XL using Tapatalk

As long as it's still cycling on it's own, it's almost certainly still doing updates. Sent from my Pixel 2 XL using Tapatalk

Just leave it overnight. It does multiple resets and firmware upgrades when you first set it up. It takes about a day to start functioning reliably. Sent from my Pixel 2 XL using Tapatalk

It SHOULD work as long as both NATs handle UDP connections correctly. The Airave sets up 2 outgoing IPSec VPN tunnels using the standard ports, one for CDMA and one for LTE. UDP NAT timeouts tend to be lower than TCP, but as long as the airave sends or receives a packet every minute or so it should be fine. I think UDP NAT entries tend to be cleared after 1-5 minutes of no activity. I imagine this is already done to prevent NAT from clearing the connection thinking it's finished. A second NAT shouldn't be any more problematic than single NAT in this regard, so you should be fine. Sent from my Pixel 2 XL using Tapatalk

Any B25 carrier that isn't in the G block is technically B2. B25 is a superset of B2. Sprint has many second B25 carriers throughout the country (Columbus, Cleveland, and San Francisco for sure). I didn't realize they were also broadcasting it as B2... likely it's for roaming compatibility with other providers whose phones may only support B2 but not B25. Sent from my Pixel 2 XL using Tapatalk

Yes, though with as low of a signal as you have, it may be taking longer to receive it. I think it's more likely to be delivered if you have a good connection on a non-loaded site. The MB likely waits until the site appears to be at low usage before downloading the update. I'm not sure when I received the update, but when I checked yesterday or the day before it was there. Sent from my Pixel 2 XL using Tapatalk

And that's the point you're missing, there isn't competition for most ISPs. It's a monopolistic environment. It's akin to saying to switch electric or gas companies, it's not possible. That's why it needs to be regulated just like other utilities. Honestly, I'd take it a step further and prefer the government to own the infrastructure (fiber to the home), and then lease it to companies at a reasonable cost and contract out maintenance. That's how you ensure actual competition. Sent from my Pixel 2 XL using Tapatalk

Netflix is just an example here. Netflix may be able to afford it, but not a new entrant to the market. Look at YouTube when they first started. It prevents new players from entering the market in the future, not even necessarily in video, but anything bandwidth heavy. The logistics of paying extra to every ISP as a startup is absurd and logically insurmountable. You basically lock in the current players as the content providers going forward. As a customer, you pay for the bandwidth, the ISP shouldn't care what it's being used for. Charge the customer what you need to to handle the costs for the level of bandwidth they subscribe to, don't try to double dip and charge the other end as well. Sent from my Pixel 2 XL using Tapatalk

Actually that's not true, that's a benefit of being a common carrier is that they aren't liable unless they are alerted to that particular instance. Once they start monitoring it and restricting it on their own, then they are responsible for policing it. As it stands, they just have to alert the responsible parties of the copyright infringement. Also, not all torrents are piracy. Some games use torrents to distribute updates for example. Sent from my Pixel 2 XL using Tapatalk

Or if the ISP decides they don't want to pay more for Netflix and pull access to it, like cable and satellite providers do all the time when they have a contract/price dispute with a channel. Sent from my Pixel 2 XL using Tapatalk

The MB can't connect to B41 if it's not there... it broadcasts B41 only, but it will connect to a macro on B25 or B41. The only qualifications are 1. that the macro's signal is strong enough to use, and 2. Sprint has the B41 spectrum required for the MB in that location Sent from my Pixel 2 XL using Tapatalk

The MB uses B25 for its relay connection. It prefers B41, but it will happily use B25 if that's all that's available. It rebroadcasts that as B41. So when you see B41 around you're house, that means you're on the MB, which is then connecting to the macro via B25. When you get out of range of it, you go back onto the macro on B25. Both are using the same signal from the macro, but the MB has high gain antennas and will generally be faster and more stable as a result. Sent from my Pixel 2 XL using Tapatalk

The B41 PCI is the MB, their PCIs are around 500. So whatever B25 macro you connect to with your phone is the same one that the MB is using. Sent from my Pixel 2 XL using Tapatalk

Tap the relay icon, and it'll show the frequency it's using, the band, and the PCI. Use SCP or market maps to match up the PCI to sites in your area. The MB unfortunately doesn't show the GCI, so this is the only way to figure it out. Sent from my Pixel 2 XL using Tapatalk

Google Pixel 2 XL always has SRLTE engaged. It uses ISIMv2. SMS seems to always go over CDMA rather than over LTE via IMS. Sent from my Pixel 2 XL using Tapatalk

The Pixel 2 XL also does SRLTE all the time. The big downside seems to be that SMS always uses CDMA again instead of using IMS. So long messages will be split, incoming ones are out of order (and delayed a minute or 2 sometimes), and sending takes a while. Otherwise, I suspect incoming calls will be more reliable. Sent from my Pixel 2 XL using Tapatalk

It's been this way for a couple years for me, but getting worse. It can't really get worse than it is now unless Sprint adds more customers, since they've already thinned CDMA down to the minimum. The addition of calling plus and VoLTE will take load off of CDMA, so it should start to improve actually. Sent from my Pixel 2 XL using Tapatalk

My guess would be the loss of the extra 1x carriers that are now used for the second B25 carrier. The remaining 1x carrier is likely overloaded, resulting in dropped calls or failed calls. 1x800 in some markets (Pittsburgh, SF) is so overloaded that calls are compressed to the point of being unintelligible at times. 1x1900 fairs better, but still shows signs of being overloaded at times. Sent from my Pixel 2 XL using Tapatalk

I found that the airave wifi crawls for a bit shortly after it's booted (likely it's still booting internally for a while after first broadcasting a signal) and when using a lot of LTE data. Basically, I think it gets CPU limited and wifi or general routing is the first thing to get cut (lower CPU scheduling priority perhaps). Sent from my Pixel 2 XL using Tapatalk

Yes, that's what the Essential engineering screen looks like. The Kyocera Hydro Icon I have on FreedomPop for logging has the same style. It's actually kind of nice, since it stays up as an overlay and makes screenshots more informative (such as NSG or SCP running, or a speed test). Sent from my Pixel 2 XL using Tapatalk

I think it's only single carrier B25. I have logs from a couple months ago that covers there. The service is pretty bad, but Verizon roaming was also failing, and AT&T was no service indoors, so it could just be a bad area for all providers. Sent from my Pixel 2 XL using Tapatalk

Sure it is. The eNB completely controls it. With proper VoLTE I imagine it will take being on a call into consideration for band selection. Sent from my Pixel 2 XL using Tapatalk

Weird. I luckily haven't had any problems since Tapatalk integration was added back. I wonder if it's something in our configuration or user accounts that's triggering it? Sent from my Pixel 2 XL using Tapatalk