Computers & Hardware > Apple Related
No internet
Weaver:
I have had apps such Netflix or Safari suddenly saying 'no internet' or something similar and telling me to turn mobile network on, as if they have lost the WLAN. Stupidly, I have not thought to really debug the situation with things like pinging the router doing a traceroute to the isp and so forth at the time. Ridiculous that I did not also check things like the routing table IP address ownership and so forth.
A quick off / on on 'Wifi' in Settings will cure it. I think I may have posted about something similar before but that iirc was a temporary thing, with no on/off required.
It do not see how it can be the fault of the WAPs as they have not changed. The signal level is excellent and the speed reported by the WAP for my ipad which is ten metres away from the WAP is 200 - 300 Mbps. The problems started with ios 11.4.0 and then 11.4.1 I think. Certainly no problem before then. I am just hoping that iOS 12 will be a lot more reliable. I would really like a very boring release that just concentrates in delivering bug fixes found as a result if serious in depth testing.
Anyone else getting this kind of problems?
Westie:
I'm still on iOS 10.3.3, with no possibility of updating this (relatively) old iPad. :(
sevenlayermuddle:
DHCP issue perhaps? If using DHCP, any chance of switching to fixed IP?
Weaver:
Well, I do use DHCP but the address is effectively fixed in that it is locked down. The thing is that has not changed either, and I have not had problems until the last month or so. Good point tho. I should have done more checks when it happened. I am loath to make it statically configured because being an iPad it is portable.
Actually I don't know if this is a fair argument but when I used a bogus RFC1918 IPv4 address with not nat and no default IPv4 gateway is there was no ipv4 connectivity then I did not get the no internet error message and indeed accessing web sites was fine because I was doing so over IPv6 successfully. So the question then is what exactly was the condition that triggered the error message? It was not "no working IPv4" but indeed it could be "IPv4 expired". I suppose that I could make the DHCP lifetime ridiculously long or better for testing ridiculously short to see if that might help trigger this phenomenon.
d2d4j:
Hi weaver
My first thought would be power save feature, which turns off Wi-Fi when you reach a certain amount of power left. I think it’s 30%. I have mine turned off for power save mode
I thought the latest update was to help older devices with power consumption usage. Prior to the latest update, the mobile would goto about 20% battery and die suddenly. The latest version does not do this and is much more graceful
You can set each Wi-Fi connection separately, so you could set static for 1 ssid and dhcp for another, and it used each correctly
I have not seen your issue in iOS 11
Many thanks
John
Navigation
[0] Message Index
[#] Next page
Go to full version