- More porn sneaks onto the iPhone
- 'Swatting' case shows need to ban caller-ID spoofing
- Why the iPhone can't be "killed"
- Nortel enterprise chief wants to bring back Bay
- US sets final emergency responder wireless pilot
The Wi-Fi connection on Apple’s recently released iPhone seems to be the source of a big headache for network administrators at Duke University.
The built-in 802.11b/g adapters on several iPhones periodically flood sections of the Durham, N.C., school’s pervasive wireless LAN with MAC address requests, temporarily knocking out anywhere from a dozen to 30 wireless access points at a time. The campus network staff is talking with Cisco, the main WLAN provider, and have opened a help desk ticket with Apple. But so far, the precise cause of the problem remains unknown. (UPDATE: Readers speculate on the cause)
“Because of the time of year for us, it’s not a severe problem,” says Kevin Miller, assistant director, communications infrastructure, with Duke’s Office of Information Technology. “But from late August through May, our wireless net is critical. My concern is how many students will be coming back in August with iPhones? It’s a pretty big annoyance, right now, with 20-30 access points signaling they’re down, and then coming back up a few minutes later. But in late August, this would be devastating.”
That’s because the misbehaving iPhones flood the access points with up to 18,000 address requests per second, nearly 10Mbps of bandwidth, and monopolizing the AP’s airtime.
The access points show up as “out of service.” For 10-15 minutes, there’s no way to communicate with them, Miller says. “When the problem occurs, we see dozens of access points in that condition,” Miller says. The network team began capturing wireless traffic for analysis and that’s when they discovered that the offending devices were iPhones. Right now, Miller says, there are about 150 of the Apple devices registered on the campus WLAN.
The requests are for what is, at least for Duke’s network, an invalid router address. Devices use the Address Resolution Protocol (ARP) to request the MAC address of the destination node, for which it already has the IP address. When it doesn’t get an answer, the iPhone just keeps asking.
“I’m not exactly sure where the ‘bad’ router address is coming from,” Miller says. One possibility: each offending iPhone may have been first connected to a home wireless router or gateway, and it may automatically and repeatedly be trying to reconnect to it again when something happens to the iPhone’s initial connection on the Duke WLAN.
Comments (117)
Probably irrelevant butBy Anonymous on March 24, 2008, 10:31 pmIt's basically ridiculous to try to troubleshoot someone's network when you don't have the first clue what equipment they are even running, but if nothing else this...
Reply | Read entire comment
Cisco WirelessBy Anonymous on November 28, 2007, 8:52 pmCisco has widespread issues with their microcell architechture Wireless Lan Gear. In typical Cisco fashion, what they sell and what their wireless LAN solutions...
Reply | Read entire comment
Cisco NetworkBy Anonymous on July 24, 2007, 11:30 amWe have a large Cisco LWAPP deployment with 6 WiSM controllers and over 1000 active AP's and a few users with iPhones and have yet to see any issues. And in reply...
Reply | Read entire comment
Cisco responsibleBy Anonymous on July 24, 2007, 8:27 amWe used to have a Cisco Wireless network until we found that the Cisco Controller model had issues dealing with Multicast traffic especially the way that Cisco recommends...
Reply | Read entire comment
...but correctBy Gerrit DeWitt on July 23, 2007, 11:09 pmApparently I'm not only mentally deficient, but I'm correct: http://www.dukenews.duke.edu/2007/07/cisco_apple.html --Gerrit
Reply | Read entire comment
View all comments