Apple iOS® versions 4.1 - 6.1 exhibit a bug which can cause the iOS device to disrupt service for other devices on the same network from time to time.
A detailed description of the issue is at iOS 4.1 - 6.1 Allows DHCP Lease to Expire, Keeps Using IP Address .
The following workarounds may be used to prevent an affected device from exhibiting this bug.
Follow this procedure for iOS 4.1 - iOS 4.3.x. (Devices running iOS 5.0 and later will be unable to use this procedure; scroll down for a different procedure appropriate for iOS 5.0 and later.)
Using this setting to turn off "Push" support for mail, contacts, and calendar accounts will override any per-account settings at: Settings -> Mail, Contacts, Calendar -> Fetch New Data ->Advanced.
You may still choose to set a schedule for periodically fetching such data, using the lower portion of the Settings -> Mail, Contacts, Calendar -> Fetch New Data screen.
Typically, iOS devices with a built-in camera support FaceTime.
The Settings -> Notifications category appears if your device presently has any applications installed which support Apple Push Notification Service.
It would be inconvenient (and easy to forget) to check for the appearance of the Settings -> Notifications category every time you install an application in the future. So if the category doesn't appear presently, install one of those applications now (Facebook, for example), just to force the Settings -> Notifications category to appear. Once the category appears, configure Settings -> Notifications to Off. Leave that application (or any single application that uses Apple Push Notification Service) installed "forever", so the device retains the Settings -> Notifications -> Off configuration.
For example, it may display an alert that says: Turn on Push Notifications to Allow "ApplicationName" to Receive Sounds, Alerts and Badges along with a button to Cancel and a Settings button that launches the Settings application and enters the Settings -> Notifications screen.
Despite frequent alerts of this nature, you will need to remember to not turn on Notifications.
To avoid encountering that issue, ensure you always keep installed at least one application that supports Apple Push Notification Service.
We recognize that this workaround represents some inconvenience to the customer. Short of a fix from Apple, it's the best approach we know of to allow these customers the opportunity to use their devices on the campus network.
This workaround involves disabling various services on the device. Naturally, any services or applications which rely on any of those features will be affected.
Why is this Workaround Effective?
The DHCP client software in iOS 4.1 - 4.3.5 can exhibit the issue when the following conditions are met simultaneously: the device is not attached to a power source, the device is attached to a Wi-Fi network, the device is asleep, and the device is not running any application which uses the operating system's multitasking API to stream audio from the network while the application is in the background, and there is no active cellular interface carrying cellular data.
This workaround is effective because it results in the device choosing to disconnect from the Wi-Fi network (typically about 10-15 seconds after the device goes to sleep) when the circumstances above are met.
This procedure works around the bug for iOS 5.0 - 6.1. (We do not recommend this procedure for devices running iOS 4.1 - 4.3.x; scroll up for a different procedure we recommend for those versions.)
Note that although the bug was not fixed in iOS 5.0, other changes starting with iOS 5.0 cause the bug to appear less often, effectively hiding the bug for DHCP lease times of an hour or more. And changes in iOS 5.1 effectively hide the bug for DHCP lease times of thirty minutes or more. As DHCP leases at Princeton are presently an hour or more, no devices at Princeton running iOS 5.0 or later should need to use this workaround.
Turn off the Wi-Fi interface. Do so using: Settings -> Wi-Fi -> On/Off.
After you have turned off the W-iFi interface, you may choose to put the device to sleep (press and release the Sleep/Wake button, or close the cover on an iPad2).
When you next wake the device and unlock it, you will need to turn on the Wi-Fi interface (Settings -> Wi-Fi -> On/Off) before you may resume using Wi-Fi.
Turn off the device (press and hold the Sleep/Wake button for a few seconds until the red slider appears, then drag the slider).
We do mean "turn off the device," not "put the device to sleep." (Just pressing and then releasing the Sleep/Wake button puts the device to sleep; it does not turn off the device.)
When you next wish to use the device, you will need to turn the device on. Do so by pressing and holding the Sleep/Wake button until the Apple logo appears.
Take no action; don't even press the Sleep/Wake button (or close the cover on an iPad2) to put the device to sleep.
This will result in the device remaining awake and unlocked.
You may find choice this inconvenient because the screen will continue to accept input, perhaps resulting in unintended operation of the device while the device is being transported or held.
The non-sleeping device will draw more power than it would had the device been asleep; the battery will need to be recharged sooner.
Plug the device into a power source before you put the device to sleep. Keep it plugged in (at least until you later wake the device or turn the device off).
You need not select the same choice every time you finish working with the device. For example, you might normally select choice A or choice B, only relying on choice C when you forget to take any action.
When the device is not attached to a power source, you must not simply put the device to sleep (e.g., by pressing and releasing the Sleep/Wake button, or by closing the cover on an iPad2) without first turning off the Wi-Fi interface. Putting the device to sleep while leaving the Wi-Fi interface on can lead to the device exhibiting the DHCP client bug.
This workaround relies you carrying this procedure assiduously every time you finish using the device. If you sometimes neglect to do, the device may exhibit the bug during those times.
We recognize that this workaround is inconvenient. Short of a fix from Apple, it's the only workaround we are aware of (for these versions of iOS).
The DHCP client software can malfunction when a number of conditions are met simultaneously. Some (not all) of the conditions include: the device is not attached to a power source, the device is attached to a Wi-Fi network, the device is asleep.
This workaround is effective because it doesn't permit the device to remain attached to Wi-Fi when the device is asleep without a power source.
We published this document on November 30 2010.
We updated this document on December 6 2010 to reflect the interaction between Apple's "Find iPhone" app (a.k.a. "Find My iPad," "Find My iPhone," "Find My iPod)") and the device's decision to remain associated to Wi-Fi when sleeping.
We updated this document on March 15 2011 to reflect Apple's release of iOS 4.3, updated it again on April 1 2011 to reflect Apple's release of iOS 4.3.1, updated it again on April 24 2011 to reflect Apple's release of iOS 4.3.2, updated it again on May 16 2011 to reflect Apple's release of iOS 4.3.3, updated it again on July 15 2011 to reflect Apple's release of iOS 4.3.4, and updated it again on July 25 2011 to reflect Apple's release of iOS 4.3.5.
We revised this document on October 12 2011 to reflect Apple's release of iOS 5.0. The release did not change the workaround for iOS 4.1 - 4.3.x. However, because iOS 5.0 eliminated the ability to turn off "Notifications" (Apple Push Notification Service), the workaround for iOS 4.1 - 4.3.x was not feasible for iOS 5.0. To address this, we added a different workaround for iOS 5.0. Although the new workaround for iOS 5.0 will also work for iOS 4.1 - 4.3.x, we continue to recommend the older workaround for iOS 4.1 - 4.3.x. This is because the workaround for iOS 5.0 is less convenient and more failure prone; it requires the customer to take additional action every time s/he finishes using the device. We also noted that although the bug was not fixed in iOS 5.0, other changes in iOS 5.0 caused the bug to appear less often, effectively hiding the bug for DHCP lease times of an hour or more. As DHCP leases at Princeton are presently an hour or more, few devices running iOS 5.0 should need to use this workaround.
We updated this document on December 2 2011 to reflect Apple's release of iOS 5.0.1; on March 26 2012 to reflect Apple's release of iOS 5.1; on May 7 2012 to reflect Apple's release of iOS 5.1.1; on September 19 2012 to reflect Apple's release of iOS 6.0; on November 4 2012 to reflect Apple's release of iOS 6.0.1, and on February 4 2013 to reflect Apple's release of iOS 6.1,