Exposing Apple, iOS 6 WiFi Problems, & The IPv6 Protocol

** Update 10.29.12 **  I’ve been covering the iOS 6 WiFi problem from day 1 (actually from the first hour iOS 6 was released) – I don’t profess to know everything, but I’ve found (and a lot of the readers that have communicated with me have also found) that more than likely one of the fixes I’ve written about below will resolve your WiFi connectivity issue.  If not, then it’s possible your WiFi problem is outside the scope of iOS 6.

I’ve been anxiously waiting all day today to finally get the time to write this article.  As you know, we’ve been talking a lot about the iOS 6 WiFi problems, I posted earlier the reason as to why iPhone 4s, iPad 2, and iPad 3 devices (after upgrading to iOS 6) and the iPhone 5 straight out the box (because it comes preloaded with iOS 6) are all experiencing WiFi connectivity problems on certain wireless networks.  And as I’ve pointed out the fix was to simply upgrade your wireless router to a firmware update that’s been released no later than the last 10 months – and if you have a wireless router that doesn’t have a firmware update available within the last 10 months then your only real option is to go out and buy a new one.

What I want to explain to everyone is exactly what’s going on with all of this WiFi connectivity drama, why iOS 6 seems to be causing all of these issues (which you’ll seen see it’s not iOS 6′s fault at all), and what’s really at play behind the scene.

What I’m referencing are things like Apple’s insatiable drive for profits, how the United States is behind the curve when it comes to Internet and wireless protocol, and how ultimately iOS 6 is the trigger that had to be pulled to force our country, and all of us in the U.S. that use iPhone and iPad devices, to catch up with the rest of the world’s technology.

First, why all of the WiFi problems with iOS 6?

Let me first try to explain, as best I can without completely losing everyone, why all of these WiFi problems are popping up in the first place.  And it all has to do with thing called IPv6 which stands for Internet Protocol version 6.  As you may have noticed if you own an iPhone 3GS and iPhone 4 AND you upgraded to iOS 6, you more than likely had absolutely no problems connecting to the WiFi networks.  I know here in my house we have three iPhone 3GS’s and after upgrading to iOS 6, all three have been connecting perfectly to any and all available WiFi networks.  And you may have noticed the same thing if you have an iPhone 4.  You upgrade to iOS 6 and bam… you connect perfectly to any and all WiFi networks available.

But wait a minute… those of you who have an iPhone 4s, iPad 2, and iPad 3 (sorry 1st gen iPad owners, you were never part of the equation to begin with) and you upgraded to iOS 6 you noticed immediately that you were having WiFi problems.  And of course, those of you who purchased the iPhone 5 noticed the same thing, but you didn’t have to upgrade to iOS 6 because the iPhone 5 was preloaded with iOS 6 right out of the box.

The reason why you were able to upgrade to iOS 6 on your iPhone 3GS and iPhone 4 and not have any problems is because the wireless cards in the iPhone 3GS and iPhone 4 are built to run, and connect to wireless routers, that operate on the old Internet Protocol called IPv4 (Internet Protocol version 4).  And if you’ve purchased a wireless router within the last 5 years (which most of you have) then your WiFi network has been connecting devices on IPv4.  So when you upgraded your iPhone 3GS and your iPhone 4 to iOS 6, and because these two specific devices are capable of IPv4 protocol connectivity, you’ve been connecting just fine without any problems.

But when you upgraded your iPhone 4s, iPad 2, iPad 3, and started using your iPhone 5 on these old wireless routers that are only capable of IPv4, your devices haven’t been able to connect.  And the reason why is because the wireless cards (or whatever they are called in iDevices) for the iPhone 4s, iPhone 5, iPad 2, and iPad 3 require IPv6 protocol if they are running on iOS 6.

Make sense so far???   Basically, if you are running iOS 6 on an iPhone 3GS or iPhone 4, you’ll probably never have a problem with WiFi connectivity because iOS 6 is not forcing these two specific devices to connect via IPv6.  But once the iPhone 4s, iPad 2, and iPad 3 are running iOS 6 – and of course the iPhone 5 that’s already running iOS 6 – these WILL NOT CONNECT to a wireless network unless the wireless network is capable of IPv6 protocol.

This is exactly why you are having problems with your iOS 6 devices connecting to WiFi networks.  And if you are someplace like your office building, Starbucks, etc… and you are having the WiFi connectivity problems with your iOS 6 enabled iPhone 4s, iPhone 5, iPad 2, or iPad 3, then it’s because the wireless routers in that location are outdated – which means they are not operating off the IPv6 protocol.  And since your iOS 6 enabled device is requiring IPv6, you are never going to successfully connect.

Why IPv6?  And how does it relate to the iPhone 4s, iPhone 5, iPad 2, & iPad 3?

First let me simplify my life a bit here.  I’ve already explained that the iPhone 3GS and iPhone 4s will connect fine on iOS 6 to virtually all WiFi networks.  The problems are isolated with the iPhone 4s, iPhone 5, iPad 2, and iPad 3 AND the fact that iOS 6 is running on these four devices.  So from this point forward, just assuming I’m referencing these four specific devices – that way I don’t have to keep typing them all out.

So why is IPv6 such a critical component, and literally the heart of all the WiFi problems?

Great questions — let me address them in a way that will hopefully leave you not only understanding the relationship, but also more educated as to what happens every time you connect to a network with your iPhone or iPad.

Perhaps the easiest way to explain why IPv6 is playing an important role in all of this is to compare IPv6 with IPv4.  And then I’ll tie all of this in with Apple.

Ready?

Ok, so without writing out a 30,000 word dissertation, let me first say that IPv4 and IPv6 are both IP address protocol platforms that are used here in the United States.  Whenever a device (a laptop, iPhone, Android tablet, a computer, your watch, GPS, printers, etc….) connect to either a network or a data source, an IP address is what allows that device to both send and receive data.

You may recognize this number (or maybe not), but a very common IP address here in the United States is 192.168.1.1.

This is typically the starting IP address for most of the wireless routers that are in use today in the United States and you may be familiar with this IP address because for the wireless routers that use this IP address as the standard point of connection, it’s what you’ll type into your address bar to access the admin dashboard of your wireless router.

Well the IP address of 192.168.1.1 is a typical IPv4 address.  The problem with IPv4 is that it’s limited.  And when you have an internet protocol that’s limited, this means you can only have a limited number of devices connecting to the internet via wireless networks, or really any networks for that matter.

Let’s say, for this example anyway, that the IPv4 protocol that’s our current standard here in the United States is only capable of issuing 422 million IP addresses.  The other way to say this is, the IPv4 protocol is capable of connecting only 422 million devices (computers, mobile phones, etc…).  Obviously, you can see the problem with IPv4, right?  With the explosive growth of smartphones like the iPhone, Android phones, etc… and tablets like the iPad, Kindle Fire HD, and Nexus 7, you can easily imagine 422 million IP addresses getting used up pretty quickly.

Well that’s where IPv6 comes in to save the day.  Because IPv6 protocol actually adds two more digits to the original IP address of 192.168.1.1 and creates a new starting IP address of 192.168.1.1.1.1 (notice there are two more digits added to the end of the old IPv4 protocol address).  So this means, under the IPv6 protocol we could literally connect not just hundreds of millions of devices but billions of devices.

** This is important **  With IPv6 protocol, we are now able to connect BILLIONS of devices (or distribute BILLIONS of IP addresses) versus only hundreds of millions on IPv4.

Now, the reason you are having problems getting your iOS 6 enabled device to connect to WiFi networks is because, as I mentioned earlier, the iOS 6 enabled iPhone 4s, iPhone 5, iPad 2, and iPad 3 all require IPv6 protocol.  But yet, the iPhone 3GS and iPhone 4 do not – again, this is why you probably aren’t having any problems getting on WiFi with the 3GS and iPhone 4 – both of these devices only need the old IPv4 protocol.

But what does “they need IPv4″ and “they require IPv6″ mean?  And how is this directly related to Apple and their devices?

To explain this best, I have to first explain to you what happens when your iPhone or iPad connects to a wireless network.  This is something that you have no idea is even happening, and it happens near instantaneously.

IPv4, IPv6, & Apple’s Authentication Token

Here’s what happens each and every time your Apple device, whether its an iPhone, iPad, or even an iPod Touch, connects to a WiFi network.

As soon as your Apple device detects a wireless network, the very first thing it (your iPhone, iPad, or iPod Touch) does before connecting to that wireless network is send a data packet to Apple’s website in order to receive what’s called an authentication token.  This transmission happens because Apple wants to always know that the iPhone, iPad, or iPod Touch you are using is actually a legitimate Apple product.

And in order for your Apple device to connect to the wireless network that it detects, it must first receive an authentication token from Apple servers verifying that your device is legitimate – and once that authentication token is received, you will then be able to jump on whatever wireless network is available.

I know, it’s kind of amazing to think that all of this happens before your iPhone or iPad connects to a wireless network, but it’s true.  And it only take s a split second for the authentication token to be received from Apple’s servers.

Now that you know Apple requires all devices to be “authenticated” before connecting to a wireless network, let’s talk about the “why” behind Apple doing this.

Anyone who’s looked at the “location services” of their iOS 6 device should immediately see the reasoning behind the authentication policy that Apple has on all of their devices.  I would say there are two main reasons for Apple’s authentication token:

1)  because Apple is very protective of their brand and they want to make sure that the devices that are calling themselves “Apple” are actually Apple products.

2)  Ads & profits.  How else can Apple provide a valuable advertising platform if they aren’t able to control and verify the exact location of your device.  Have you seen the location services section of your new iOS 6?

again… more on this article coming, so stay tuned…

Share This Post

Related Articles

  • Boss

    This is quite brilliant of apple, but why cant they connect to ipv4 , is the chip specially ment to connect to ipv6, I want to buy an ipod but idk now that this is happening

    • http://TabletCrunch.com/ Tablet Crunch

      They can, and do, connect to IPv4. And why that is, I have no idea. All I do know is that once we upgraded all of our wireless routers to be IPv6 compatible, we’ve had hundreds of iOS 6 devices on our network connect perfectly.

      Before, there was WiFi connectivity problems campus wide – and now there aren’t, nor has there been, since we’ve implemented our fix.

  • Ali

    Yes but apple didn’t fix ios attachment mail problem

  • AndroidUserFromNowOn

    Certainly not the case because 4S’s were connecting to iPV4 networks just fine before iOS6 so this strictly points to software. Good thoughts here but it’s just not the case. I’m a former Mac Genius for Apple and if I were to tell you that it’s all a conspiracy you would think I am crazy! Think about it a bit more on that front and it will really start to make sense. You can’t tell me that my AirPort card in my brand new MacBook Air isn’t more sophisticated than that of a WiFi antenna in an iPhone, yet IT has zero problems connecting to any Internet protocol router g/b/ or n.
    Sorry, not trying to insult you here or anything. I am just sick of Apple’s antics. They have become another huge corporation that is fleecing America!

    • http://TabletCrunch.com/ Tablet Crunch

      All I’m telling you is the indisputable fact that the iOS 6 devices we’ve seen that were having WiFi connectivity problems are no longer having problems after we implemented out fix.

      And all I’m also telling you is that when iOS 6 devices were having WiFi connectivity problems, it was IPv6 data packets that were dropping into our bit bucket. So we updated all of our wireless routers to be IPv6 compatible and now there are ZERO WiFi connectivity issues.

      What would you call that?

  • Pingback: IOS 6 wifi connectivity article.

  • theginjaninja

    Sorry mate but that is definately not the problem. If it was a hardware issue that only connected to IPv6 then the 4s or ipad2 would never have worked with older routers before the ios6 upgrade. therefore it is is a software issue with ios6 – probably no mistake wither, it’s Apple trying to get you to upgrade your hardware

    • http://TabletCrunch.com/ Tablet Crunch

      again… another person leaving a comment here that must have, just like me, seen the results of actually testing, analyzing, fixing, and observing the outcome of implemented fixes.

      Let me ask you, what has been your observation of implementing fixes for hundreds of iOS 6 devices?

  • Dazau

    Factually wrong. 192.168.1.1.1.1 is not an ipv6 address. Also how can an iphone connect to apple servers *before* it attaches to a wifi access point? It needs an ip address to connect to apple but does not get one until the access point connection is completed. You also dont explain that there is probably more that 422 million ipv4 devices that are currently connected to the net today because they use NAT. Not a credible story and not explained at all well. IOS 6 supports both ipv4 and ipv6 in what is called “dual stack” so your confusing explanation is just wrong.

    • http://TabletCrunch.com/ Tablet Crunch

      I don’t what you call factually right or wrong – I’ve seen the results of hundreds of iOS 6 devices continue to connect perfectly – where there were issues – since implementing the fixes that I’m referencing.

      I’m not a networking genius like you – I just know the results from the work we are doing. And to that, there is no “factual” debate.

  • tom

    “As soon as your Apple device DETECTS a wireless network, the very first
    thing it…does before connecting to
    that wireless network is send a data packet to Apple’s website”. How can an iDevice send something over a wireless network unless it’s connected ? What about secure networks that require a password before any device can connect ? You must just want your 15 minutes.

    • http://TabletCrunch.com/ Tablet Crunch

      I have no idea Tom, that’s why my name isn’t Steve Jobs. But please don’t tell me that just because YOU don’t see the rational behind something you immediately discredit it as not possible…

  • Brmorris

    I don’t think this is impacting many folks. I’m connecting to a recent Linksys router and it is connecting with IPv4. Most of the wifi issues are slowness or intermittent loss of packets moving, not a failure to connect (although I have read of a few folks with that problem). Read this for IPv6 info (it used hexadecimal, not 192.168.1.1.1.1).

    http://en.m.wikipedia.org/wiki/IPv6#section_5

    • http://TabletCrunch.com/ Tablet Crunch

      this isn’t impacting many folks at all, especially considering that by now there are probably hundreds of millions OS 6 devices upgraded without any problem.

      All I know to comment on are those iOS 6 devices that are experiencing WiFi connectivity issues – and when it comes to that pool of devices, the fix I keep references is indisputable. And if it doesn’t fix the problem, then the issues are deeper than just the iOS 6 upgrade.

      • notAnExpert

        I’m form Mexico and I had Wifi problems with my ipad 2, fortunately apple replaced ir with a new one. Now, I don’t think its a IPv6 Problem, here in México almost nobody have IPv6 adresses, so hundres of iPhones 4s, iPads etc.. will be working.
        I also don’t think that sending a packet before connecting to the wifi its possible, TCP/IP protocol works with layers, one of the main important one is the network layer, wich gives a path to send the packet base on the IP adress and the MAC adress. If you divice does not have ant IP adress it can not go over the network, its not able to connect to the internet, so it can not send packets. Imagine trying to send mail to someone without know the adress.

  • http://chealion.ca Micheal J.

    Authentication token to find out it’s a legitimate device? Call me exceptionally skeptical. They send a packet to determine if the wireless network in question is a captive network and requires a login and as such bring up a sheet allowing you to log in. (Instead of having to open Safari manually)

    I feel like I reading a piece by Daniel Eran Dilger…

    • http://TabletCrunch.com/ Tablet Crunch

      how about I’ll just call you “critical”…

      • http://chealion.ca Micheal J.

        That’d be accurate.

        Am waiting for the updates; I’m assuming the issue is caused by the fact that the iOS device can’t get a valid IPv6 address (handshake failure) it fails to use IPv4 correctly. (Mac OS X has had similar issues). Since you can’t disable IPv6 on an iPhone there’s no way for a user to get it to properly handle the fallback without a software update.

        Still would love to know more about the “authentication packet” as I’ve never heard of it before and really can’t find anything via Google.

        • http://TabletCrunch.com/ Tablet Crunch

          then consider yourself a more educated Apple fan then… Apple verifies every single device before it connects to a wireless network to ensure that your device is an authentic Apple product – thus “authentication token”.

          • http://chealion.ca Micheal J.

            Source? (Beyond the fact it’s physically impossible to connect to Apple without the internet connection you’re just about to make – but then we’re arguing the implementation and not the fact such a step is being taken)

          • http://TabletCrunch.com/ Tablet Crunch

            umm… wow, you are obviously much smarter than I am so if you could, tone it down a bit for us less gifted one like myself.

            What I’m saying is that, based on the observation, analysis, implementation, and confirmed results, there were iOS 6 connectivity problems on iPhone and iPad devices within our network – after upgrading 28 routers so they are IPv6 compatible, not a single problem.

            What does your research tell you?

            And just because you don’t know about something that I may possibly know doesn’t mean you have to be rude to me. It’s like people are ready to crucify me because I might actually be talking about something they either don’t know, don’t understand, or both.

          • http://chealion.ca Micheal J.

            Was not meant to be rude, overly brief maybe but not rude. I’m really trying to get to the bottom of something you said to ascertain what you’re actually meaning.

            Tone down how networks work? I’m really not following you there. Sorry.

            Asking for source was really just a straight up question, I can’t find anything to corroborate your statement about an authentication token. What you’ve said doesn’t fit Apple’s method for identifying captive networks or rapid DHCP. If Apple really is authenticating devices before they can be used I’d sure like to know about it.

          • http://TabletCrunch.com/ Tablet Crunch

            Really? What I’m saying doesn’t fit Apple’s method… Have you taken a look at the location services in iOS 6? I’d say that it’s EXACTLY in line with Apple’s methods.

            Again, everyone’s ready to crucify me (and discredit Tablet Crunch) because I’m possibly talking about something they don’t understand.

            Whatever…

          • http://chealion.ca Micheal J.

            … Method as in how a feature works. Your explanation thus far of an “authorization token” is lacking. I can’t understand if it jives with a misunderstanding of how the captive network feature works or a misunderstanding how Siri uses tokens to prevent unauthorized use.

            RE: Location Services. You mean the expanded options to turn off and see what apps are requesting access to your location? The 100s of apps I have installed that don’t use iAds. That you can turn ad tracking off (which is made to stop developer’s from doing it themselves using your UDID)?

            Well if I’m supposed to be crucifying you let me go find a hammer and nails because I forgot mine. The closest I came to piling on about the egregious technical explanations was to accurately compare your writing to Daniel Eran Dilger’s.

            I’m asking for technical details, you’re replying with misdirects and pleas to dumb down the facts. I’m not disputing you figured out that there is something to do with IPv6 and iOS 6 – but that’s going as deep as saying you can’t open the door because of the handle (the headline certainly makes it sounds like there will be an explanation). Is the handle broken, is it locked, or is it actually the deadbolt and replacing the whole handle/lock system fixed it. (Crappy Correlation != Causation example)

          • http://TabletCrunch.com/ Tablet Crunch

            how else do you want me to explain and verify that Apple does, and always has, had an authentication token with their all of their devices.

            It’s simple really – Apple wants to ensure that every device that calls itself an Apple device is actually a legitimate Apple device.

            Look at the problem (as an example) of Sprint iPhone 5′s bricking. Basically, you have Sprint with unlimited data packages that find no need to carry WiFi in their stores – why would they, they have unlimited 4G data. And so you have Phone 5′s leaving the Sprint store that have never connected to a WiFi network – which means they have never officially be authenticated by Apple.

            So you, the customer, walk out of Sprint with your new iPhone 5 > get home and turn it on > attempt to connect to the WiFi network at your house and BAM!!!!! Your iPhone 5 gets bricked.

            Why do you think that happens?

            Because that particular iPhone 5 left the Sprint store without ever official being authenticated. So as far as Apple knows, when you get home and try to connect to your WiFi network, that iPhone 5 is stolen, fake, not authentic, etc… whatever the “cause” it gets bricked.

            Now tell me – how could that even be possible unless Apple has an authentication protocol in place?

            And this is just an example where you can see the authentication token at work in a more visible fashion.

            Or you can look to the example that I’ve been talking about all along.

            Whatever you look at or research to verify what I’m talking about, there is no disputing the fact that Apple has a verification token > that verification token is failing on the iPhone 4s, iPhone 5, iPad 2, and iPad 3 that are running iOS 6 > and the reason is because Apple’s authentication token is requiring IPv6 protocol.

            If you have an iOS 6 device that doesn’t have WiFi connectivity problems, then I don’t know what to tell you…. congratulations maybe?

            I’m not an Apple engineer, nor am I Steve Jobs, so I’m not an expert on Apple authentication token. That certainly doesn’t discredit its existence, nor does it discredit the impact it’s having on WiFi connectivity issues with iOS 6.

            Quite the contrary – because our actually research, and the cold hard facts that we’ve gathered, point to exactly that being the problem.

            And to solidify our argument, when 28 wireless routers were upgraded to IPv6 protocol, all WiFi connectivity problems disappeared on iOS 6 devices.

          • http://chealion.ca Micheal J.

            We’re definitely not talking the same language. Sorry.

  • Pingback: Android vs iOS war: Android to get 1 billion activations a year – Northern Voices Online | www.linn.mobi

  • Smeghead

    Exposing the Author.. you know jack about IP addressing.
    IPv4 can address 4.3 billions; and in fact there are more than 4.3 billions of devices that have IP addresses.. IP is the standard for the whole internet, not just in the USA.
    192.168.1.1 is a very common IP address? Oh Rly.. if you are a router maybe.. 192.168.1.1 is a non routable IP range.
    you really should at the least try to understand what you are writing about..
    further, your article is so poorly written.
    1/10

    • http://TabletCrunch.com/ Tablet Crunch

      again, another person who’s done more research on the issue of iOS 6 wifi connectivity problems enlightening us with their profound insight and wisdom.

      • Amused

        He’s not saying anything about why iOS 6 has wifi problems. He’s commenting on patently false statements in the article.

        • http://TabletCrunch.com/ Tablet Crunch

          ok – then tell me why the U.S. government has now mandated IPv6 since January 2012?

          And aside from the actual number, the very same reason the U.S. government is mandating IPv6 is the same reason why Apple is covertly forcing the U.S. to get caught up to the rest of the world when it comes to wireless technology.

          And just because you don’t believe me, nor understand something I’m talking about…. does that mean it’s not true?

        • http://TabletCrunch.com/ Tablet Crunch

          forget to ask… what statements exactly are you calling “patently false” in this article?

    • http://TabletCrunch.com/ Tablet Crunch

      do you not agree that with the IPv4, we will eventually (sooner rather than later) run out of IP addresses? And that by upgrading to IPv6, we eliminate that problem?

      And if you do agree with that statement, would you not agree then that it would be beneficial for Apple to force, in whatever way they could possibly do it, manufacturers to upgrade their wireless routers to IPv6 protocol?

      And if you don’t agree with the above statements, then why did the U.S. government pass a law in Jan. 2012 that requires wireless device makers to implement IPv6?

      And if you still have parts of my article that you outright disagree with, then what are they exactly and why?

      • http://twitter.com/TOClarks Toronto Clarks

        In 2008 a law was passed that gov’t agencies must have IPv6 devices enabled in their network (it didn’t say turn off all IP v4 capability – a good idea to stop them buying old crap). Spet. 2012 all internet facing gov’t websites (DNS, mail servers, etc.) were mandated to offer these services over IPv6. Again nothing in law to say turn off IPv4. Many agencies missed that deadline. Most people don’t have several billion devices in their home or office. “196.168.1.1″ as noted is a private subnet, not routable over the internet (like the 10. class A network). What needs to be IPv6 enabled is the edge routers. An end point should not be trying to send traffic using an IPv6 protocol over an IPv4 network. I suppose if Apple chooses to eliminate the power supply and assume everyone changed their homes to DC power to accomodate them and ship them with the same plug the Apple supporters would be fine with that too?

  • Windtalker

    Wow, there is almost nothing in this article that is factually accurate. How does this author get to publish articles like this?

    • http://TabletCrunch.com/ Tablet Crunch

      really? how about you enlighten us then with your grand wisdom as to why the only verifiable fix to wifi connectivity issues associated with the iOS 6 upgrade on the iPhone 4s, iPhone 5, iPad 2, and iPad 3, is to update the firmware on your wireless router so that it’s IPv6 compatible.

      You must have done more research on a larger pool of iOS 6 devices, so I can’t wait to hear your profound wisdom on this subject.

    • http://TabletCrunch.com/ Tablet Crunch

      still waiting for your response as to what part of my article is (as you stated) not factually accurate

  • ranjix

    terrible article. First of all, the wifi issue is not necessarily that it doesn’t connect, but that it connects and drops the connection all the time. The explanation with ipv6 and ipv4 doesn’t hold.
    “And as I’ve pointed out the fix was to simply upgrade your wireless router to a firmware update that’s been released no later than the last 10 months”.. Simply upgrade the wireless router? Been with computers for some decades, and I can’t consider that “simple”. Is elaborate, needs preparation and care, and possibly work afterwards to reconnect the machines.
    Finally, the explanation with adding .1.1 at the end of 192.168.1.1 to get an ipv6 address is just precious.
    Whatever.

    • Jproos

      But 6 is 2 more than 4 so an ipv6 ip address MUST have 2 more octets than an ipv4 address, right?! ;-)

      Before joining a wifi network with an iDevice ithat device has to hear from Apples servers to find out if the device is legitimate? Seriously? I can’t even imagine how someone would even come to that conclusion.

      This article is just about the most laughable thing I’ve ever read online.

      Maybe it was meant as a laugh for those suffering from IOS 6′s wifi issues?

      • http://TabletCrunch.com/ Tablet Crunch

        the critics in the comments here are unbelievable – and I’m still waiting for someone to actually disprove what we’ve been able to prove through testing, implementing, observing, and measuring.

        Oh wait – that would actually require you to do something more than be a critic in blog comments…

        When your testing disproves what we’ve been able to prove, then let me know

        Otherwise, for everyone else reading this article, just go ahead and upgrade your wireless router, or buy a new one > reset your network settings on your iPhone > and enjoy the freedom from frustration and fast connectivity.

        If that didn’t work, then you are in the wrong place because your problem isn’t related to what’s being discussed here.

        • Amused

          I suspect that the general consensus is that making several of the statements you make in the article and actually figuring out why IOS 6 devices randomly stop passing packets via wifi are mutually exclusive.

          A little searching regarding this site completely clarifies my earlier question.

          adios muchachos

          • http://TabletCrunch.com/ Tablet Crunch

            oh wow… so because you just said what you said means that what I’m saying is not true??? adios

          • http://TabletCrunch.com/ Tablet Crunch

            besides researching my site, I think your time would be better spent researching the facts that I’ve stated in this article – would cause a much more intelligent and productive conversation to unfold

      • http://TabletCrunch.com/ Tablet Crunch

        and perhaps you should research a little bit deeper on the methodology of iOS and the relationship between a device and Apple severs.

        It’s not a conclusion that I’ve come to – it’s a fact that exists.

        What’s laughable is your position that just because someone is talking about something you clearly don’t understand – or have any knowledge about – then it’s just not true.

        Well… Apple’s authentication token is as true as the app store is verifying your account each time you download an app.

        Get over it > get researching it > and then come back and add something of value

    • Amused

      ipv6:ipv4 as 6:4. Comical. How could someone being paid to write such an article say the patently false statements contained in this article?

      • http://TabletCrunch.com/ Tablet Crunch

        1) I’m not paid to write in tablet crunch – it’s just my blog

        2) what’s the results of your research on how to fix the iOS 6 wifi connectivity issue

        Everyone here is so quick to discredit what I’m saying, yet ironically it’s been the only thing that has completely eliminated the WiFi connectivity problem for iOS 6 devices on our network.

        I’m not an Apple engineer, nor am I paid to write this stuff.

        I’m actually just trying to help people implement what we’ve observed as a fix to the WiFi connectivity problem.

        SO for the readers here at Tablet Crunch that are having WiFi connectivity problems since upgrading to iOS 6…. you can either engage in this babble of what’s true, not true, blah, blah, blah…

        Or you can implement the solution that we’ve presented so many times in both articles and videos and finally get back to fast WiFi connectivity on your iOS 6 device.

        Your choice…

  • William Swartzendruber

    I would disagree with you that the U.S. is trailing in IPv6 deployment. Comcast, our largest provider, has been enabling native IPv6 access in various service areas for the past six months. Just last month Verizon Wireless started offering IPv6 connectivity to not only 4G users, but also to 3G users who have 4G devices. AT&T has finished deploying 6rd and has it on their new routers. Google, a U.S. company, spearheaded IPv6 adoption across the world, demonstrating that it could be done on such a large scale. And Microsoft, another U.S. company, shipped the first consumer operating system with comprehensive IPv6 support, and that was in 2006. Oh and our government is almost switched over. Feel free to clarify.

    • http://TabletCrunch.com/ Tablet Crunch

      honestly, I’m not an expert in IPv6 and don’t really want to debate that issue.

      The truth is, Apple is forcing IPv6 integration across the board – users, wireless device manufacturers, ISP’s – with iOS 6. Which is why users are experiencing WiFi connectivity problems on IPv4 routers.

  • Columt

    Thanks a million Robert – your article has been most helpful
    to me.

    And come on you flamers – any errors around explanations of IPv6
    address formats is immaterial to Robert’s underlying theory.

    My current working theory is that if, after a reboot, the
    first time the iDevice attempts to connect to a wifi network it will only work reliably
    if that networks supports IPv6 (perhaps permitting whatever authentication may
    be required by apple). Happily, subsequent
    connections to non-IPv6 networks work fine.

  • Fendall O’Keefe

    The basic fact that Apple made this “upgrade” turning such a volume of Ipad customers hardware unusable when they travel is inexcusable.
    As a customer i spend the extra money for Apple products because of their reliability-this throws this out the window.
    I cannot travel for work and use this wondering if the WiFi router where i’m staying has been upgraded to IPv6.
    -i find it hard to believe that Apple cannot issue a fix so these work as the older devices.
    –IPad 2 will be up for sale

  • Fendall O’Keefe

    another example of why this is a bigger problem that could come back and bite Apple in the a@$#–here is a chat i had with my internet provider.
    –Nexus 7 here i come!

    is there a IPv6 update available for the wireless router?Give me a minute while I check the account information or details.
    Please give me a minute while I research on the issue.Thank you for your time.

    I see that there is no IPV6 update available for your wireless router.

  • Goggles

    I also have wifi problems after upgrading to ios6, and I have iphone4 (not 4s)? And several others. It is not only them with 4s and 5. How come, it does not get in tune with your article.

  • Anjali

    This article is just wrong. period.

    1/ causality versus correlation: how can you infer that a firmware update – which possibly brings IP V6 capability – is the only reason why the service works after the upgrade? why isn’t that something else that was bogus and fixed in the firmware?

    2/ How do you explain anyone can use an iOS device on a closed network without internet access without any problem, accessing local resources etc? looks like your mandatory magic token is not so mandatory after all…

    3/ How do you explain that in order to connect to the internet, the first thing needed is being connected to the internet? if you know anything about wifi, then you should know some networks will require hardware authentication first or other login/pwd capability. for example when you are in an Hotel, you have to pay to access the internet but if you connect to wifi you can see the hotel web page and a form where you can enter your account, room number, or credit card. When you are traveling you can see in airports or startbucks that limited wifi could work… How would this happen while clearly apple.com is out of reach?

    4/ to answer #3 – (and as part of my job in security) – I’ve run a simple packet trace of an iOS 6 only device (an iPhone 5) connecting on various networks, booting up and accessing the internet. My traces totally disprove your claim that IPv6 needs to be activated before it can connect to a network. It also shows what is sent to apple and what comes back… Why don’t you substantiate your claim with such an evidence. easy to do with simple tools. let me guess: either you don’t know how to do this or you would be embarrassed to justify your theory with those facts….

    5/ the most simple explanation for apple to reach out for a handshake appears to be to see if you are on a private network requiring a login page to be displayed. This is just common sense. Apple needs to know of a page that would always be there and answering a known response. all this happens in clear unencrypted traffic. if it can’t reach this – then means either your are on a captive portal or private network without internet reach and then the device tries to adapt by popping up the captive portal login or just do nothing and let you go on in your network…

    In summary your article does not bring a single evidence of what you claim, is at best showing a lack of understanding of basic IP and WiFi knowledge (which I could understand is your vulgarization attempt to make the article accessible for the masses).

    Reading at your answers, the conspirator theory you throw in there then appears to me just a mean to attract readers and create a misinformed debate – from which you make money through advertising & readership… this is pathetic. and so I won’t add more than this to the debate.

    if you want to prove your point, get traces from various types of network, go to Mac Donalds, go to Starbuck, go to an aiport, check at home with your DSL link on or off and at various companies. then report your findings as an engineer work.

  • Shinyleaf

    There’s actually an documented explaination for some of this in Apple’s iOS developer documentation. I’m going to try to explain this hopefully in a way even the most least technical people can understand.

    Token:

    There’s actually 2 tokens(?) involved, but neither of them are for the intentions of verifying legitimate devices as the author suggest. One of them is actually called “Apple Authentication Token”.

    Connectivity Token/Ping:

    The first ping(?) doesn’t have an actually ‘Apple’ name for it, but was introduced in iOS 4.0 and does something far less nefarious. It simply pings an Apple server to determine if the Wifi network access is reaching internet. There is no device identifying information. Why? To provide the auto-join/auto-login feature. When you’re at a Starbucks or some other internet wifi hotspot, you get a login or agreement page when you start using the browser?

    If the ping doesn’t get an answer back from Apple’s server, it knows that A) the device is connected to local WIfi router, but B) internet access is not working yet. It then assume you’re at one of these wifi hotspots (sometimes refer to as a captive network) and needs login. That’s how iOS knows to automatically pulls up a browser sheet for login even though you might not have Safari in the foreground.

    Apple Authentication Token:

    This token is released AFTER internet connection is established. It’s used authenticate create the connection to provide APNS (Apple Push Notification Service). The token ensure user specific push notifications are delivered to the actual addressed user, not someone else masquerading as such in a man-in-the-middle attack.

    (It’s about half way down the guide, titled “Token Generation and Dispersal”
    https://developer.apple.com/library/ios/#documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/ApplePushService/ApplePushService.html

    IPv6 (Pure speculation):

    I don’t know why the wifi issue is happening, nor do I know why having IPv6 compatible routers seems to fix it. Especially considering iOS started supporting IPv6 back on iOS 4.0.

    But it does remind me of a similar issue on Mac OS X that appeared a few years back. Macs on networks with non-iPv6 compatible routers were having issues with connectivity. The solution was the same: update router firmware to IPv6 compatible, or disable IPv6 all together until the next OS update. The networking stack in OS X will always try to use a IPv6 connection first, then fallback to IPv4 if it’s not available. It makes sense to try to use newer/better technology and fall back to the old.

  • Ron

    After getting an iPhone 5 I could no longer connect to my Netgear range extender. I upgraded the firmware, which indicated support for IPv6, and now I can connect with no issues. I think the author is right and thank him for steering me to the solution to my connection issue.

    • http://TabletCrunch.com/ Tablet Crunch

      WOW… thank you so much! I actually think you are my first believer – maybe my second…

  • anonymouse

    You are a complete tool!

  • http://twitter.com/mickburkejnr Michael Burke Jnr

    Has this utter clown been employed by Apple’s marketing department??? What a load of old crap. Seriously, as an IT admin I’ve had 5 devices have issues on my network because of something APPLE HAS FAILED TO DO!!!! You may require all your idiot users (and you have to be an idiot to buy an out of date, underpowered handset for £500+) to upgrade or put up with changes you enforce upon them, but do not expect IT admins to change the way their networks run. They should “just work”, as Mr.Jobs said years ago.

  • Pingback: iOS 6 WiFi Problems Continue To Swirl, iOS 6.0.2 Update On It's Way | Tablet Crunch

  • Bill h

    I would believe the information you are giving if my iPad 1 wasn’t having the same issue. We have 6 iOS devices, all having same issue, yet, and I hate to say this, our 2 pc’s don’t have this issue. Neither does our Mac book pro. Any ideas as to why this is happening to all iOS devices would be greatly welcomed.

  • Andrea

    – My comment mysteriously disappeared, no problem, I’ll repost –

    Like everyone else commenting, I have to say that it this article is so blatantly wrong it’s ridiculous. The author clearly has no idea what is going on and merely correlates his chance success with an ultimate solution.

    The ‘token’ he refers to does not exist – period.

    The only communication between iDevices and Apple is that when iOS connects to a WiFi network, the first thing it does is attempt to access http://www.apple.com/library/test/success.html. If it receives the expected ‘Success’ text, the phone knows it has internet access. However, if it receives anything else, the phone can safely assume there is a ‘captive portal’ (fancy name for ‘login page’ as you’d find in many WiFi hotspots at airports, Starbucks, hotels, etc), so it brings up that login page allowing you to log in…. that’s all there is to it.

    Part of the confusion in this article probably stems from the fact that, on the day iOS 6 was available for download, the /library/test/Success.html page which I mentioned above was broken (someone at Apple deleted it from their servers by mistake or something), so the phones did not receive the expected ‘Success’ text. This led the phones to believe they were on a ‘captive portal’-enabled WiFi hotspot….. THIS WAS FIXED WITHIN A DAY! I REPEAT, THIS PROBLEM HAS SINCE BEEN FIXED! Most importantly, this is not related to IPv6 in any way, no matter what the article above says.

    The problem with IPv6 is another one – well it’s not really a ‘problem’ but more an indicator of the state of IPv6 in general.

    First of all, IPv6 is not US-centric, it’s global. IPv4 and IPv6 are the postal system of the internet. They are addresses to find stuff, nothing else. To use a very crude analogy, IPv4 is your standard mailing address, which is old and relatively inaccurate, while IPv6 is GPS, which can pinpoint your location down to a meter or so, even if you’re in the same postal (IPv4) address.

    IPv6 is something which is being rolled out through the internet very slowly. It’s not something which appeared overnight. The standard was defined in 1995, FFS! Since the change cannot happen overnight, most devices nowadays (Windows Vista, 7, 8, Mac OS X) run what is known as ‘dual-stack’, which basically means they support IPv4 and IPv6 simultaneously.

    Apple iOS only supported IPv4 until iOS v5. With iOS v6, Apple added a ‘dual-stack’, which allowed iDevices to communicate via IPv4 and IPv6 simultaneously. If an app requested access to a server with an IPv6 address, it would work, while if another app requested access to a server with an IPv4 address, it would work too… that’s the idea of a dual-stack.

    NOW HERE’S THE PROBLEM…

    Since IPv6 is not as prominent as IPv4 yet, most routers which support IPv6 are badly configured/not configured. Similarly, many ISPs (internet providers) are experimenting with IPv6 but don’t really support it very well. But iDevices are quite dumb. If they see an IPv6 network on their local network (ie. your home or office router announces that it supports IPv6), the iDevice will allow apps such as Facebook and Maps to use IPv6 if they want. Problem is, IPv6 is in a kinda-working-kinda-broken state right now, so the apps fail. When the apps fail, you think it’s an iOS issue. When you think it’s an iOS issue, you blame Apple, or you write a ridiculous article like the one above.

    …AND THE SOLUTION

    So the solution is simple. You either:

    1) Turn off IPv6 support on your router

    2) Make sure IPv6 is configured and working correctly on your router/network. You can use http://test-ipv6.com/ to see if IPv6 works on your network.

  • Pingback: iPad/iPhone iOS 6 problems on IPv6 networks | Indri Online

  • Pingback: North Carolina

  • Pingback: scam web hosting

© 2013 Tablet Crunch. All rights reserved. Site Admin · Entries RSS · Comments RSS