100MB applications updating on cellular network

Question

Hi all,
Today I've encountered an interesting behaviour in the iOS app store when updating large applications while on a mobile network. When I pressed the " Update all" button (I had ~5 apps marked for update, 2 of them below 100MB), a popup came up telling me that some of the apps won't download since they're larger than 100MB - but when I pressed the OK button, they downloaded and installed anyway.
Is this behaviour expected? I've seen the popup so many times, I did not think to snap a screenshot of that...
I'm 100% positive that I was not connected to any wifi networks at the time (see attached screenshot below).
I apologize if this question has already been answered before (and for my choice of the category, did not know which one to choose for this).
Device and carrier details:
- iPhone 6 64GB
- iOS 8.1.3
- provider: si.mobil (Slovenia), Cellular data enabled and set to LTE

Answer 1

Most carriers don't put your phone's IP available on the internet.  First, the IPv4 ranges are running out - and with millions of phones all requiring IP addresses, you'd need millions of publicly available IP addresses that just don't exist.
Instead they use NAT.  If you have a home network with a router you probably have NAT. 
On your cellular network, your phone will be given an internal address, and you can get out to the internet through the NAT device.  But, because network connections coming from the internet to the NAT can't specify which phone they want, the NAT can't
direct the connection through to your phone.  There are protocols that can do this, but you'd have to get your carrier on board to implement them - good luck with that!
Some proof?  Take a look at the address : 10.205.41.235.  That's an
internal reserved Class C network.
One way around this, if you absolutely need phone A on Carrier B to connect to Phone C on Carrier D is to have a server that acts like a receptionist.  A connects to the server, and C connects to the server.  Something A sends to the server looks
up C (or the reverse) and then the server passes A->C and C->A communications as if they were local.
Darin R.