Ben Miller of Sniff WiFi comments:
I defend Apple a lot. When Network World wrongly accused the original iPhone of flooding Duke University’s network, I defended Apple. (It was later found to be a Cisco problem.) When a health care provider I was doing some work for blamed SIP-enabled iPhones for a VoIP problem, I eventually found out that the APs were to blame. (The APs were failing to respond to WiFi frames tagged as “Background” QoS.) Time and time networking folks blame device makers like Apple, and time and time again the problem ends up being the network.
There are times, however, when it really is Apple’s fault. When the network is operating just fine. This is one of those times. The problem is that I just don’t know why.
An interesting issue that Ben has uncovered with Apple devices and wireless performance. With so many iDevices on our networks now, how will Apple respond?
- Flexible NFV with Array Networks - August 7, 2017
- Cloud onRamp – Making The Cloud More Local For Your Users - July 26, 2017
- Feeling Your Flow with Plixer - July 19, 2017
- What Are ASICs? A Human Example - July 11, 2017
- Migrating to Healthcare Cloud Apps With Acadia and Viptela - June 5, 2017
- FutureWAN – The SD-WAN Education You Need - May 26, 2017
- Linksys and the Resurgence of the SMB - May 8, 2017
- Review – Docker Networking Cookbook - February 13, 2017
- The Future of SD-WAN Is Now! - January 10, 2017
- How Kindred Healthcare Uses SD-WAN to Secure Patient Data - December 2, 2016