Ok so what's the fix? There are others of us out here with Cisco Wireless LAN Controllers expecting a bomb to drop when someone comes on campus with an iPhone.
Does someone want to share?
Re: UPDATE: Cisco confirms its network caused Duke’s iPhone flooding.
Latest wireless headlines from Network World:
Latest 802.11 standards: Too little too late?
Two "iGadgets" enhance music experience
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary 
[1,407]
Women 4 times more likely than men to cough up personal info [589]
Japan's 10 funniest tech-related commercials [Videos] [407]
Throwing away a promo CD is "unauthorized distribution"? [1,265]
Adults too quick to dismiss educational video games [682]
Attack of the iPhone clones [Slideshow] [578]
10 things IT needs to know about AJAX [1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow] [409]
|
|
Its just like Cisco to
Its just like Cisco to divide and conquer, and keep everyone else suffering in the dark about their wireless product's issues. Take RRM 1.0 and its well-known DCA "ripple-effect." They could have saved everyone a lot of pain by coming out and stating the possible impact of this feature (assuming they tested it thoroughly - oh sorry, that's what the user community is for). Hopefully this will cause a groundswell of public clamor for the truth that they will share with the rest of us.
It's ARP, what about the
It's ARP, what about the issue that was reported here back in January, 2006
Cisco/Duke Issue
Cisco Systems has a specific process they follow to address bugs and code anomolies. Part of that process includes public announcements including workarounds, permanent fixed code builds and releases as well as a comprehensive explanation of the issue and potential implications.
It would be irresponsible of cisco to first post the comprehensive explanation of the issue thus putting their customers at risk of an exploit based on the vulnerability/bug/anomoly that was discovered.
I want to know what the deal is as much as everyone else, but they have to follow their process regardless of hype surrounding a specific bug.
World Domination
This story is fraught with irony and is thus newsworthy. I think Cisco purposely hosed the iPhone just to make a point to Apple. Recall all the licensing issues they went through with the Black Castled Kings of networking? It was settled a few months later but I think this was just a reminder from Johnnie-boy for Jobs to mind his Ps and Qs and they are the ones actually controlling the iPhone. Hahaha
All right everyone SLOW DOWN
Why is everyone so quick to judge on this issue? Just because 1 idiot went screaming "the sky is falling" does everyone else assume that this is going to happen to their network? I learned a long time ago from a great tech that an event that happens once isn't worth troubleshooting. Just replace/fix the item and move on. If it happens a second time, then get to work figuring out what happened, but one isolated case out of how many other networks where iPhones are behaving perfectly isn't worth looking at.
Tell you what - next time someone reports the exact same issue, then let's consider it news.
I think the problem runs deeper
I believe Cisco is taking the fall on this issue. I agree with those asking, "So what's the fix?". I'd like to see the real technical issues. Duke is NOT alone in experiencing the problem, other corporate networks are having similar problems; they're just not speaking up.
I am going to guess this is "fix" is a blocking of Apple's use of certain (unannounced of course)protocols. Cisco only fault is in not blocking them earlier..just in case. That's my analysis! As the Cisco ad running on this page says..."welcome to the human network"
Unannounced protocols, What?
I am going to guess this is "fix" is a blocking of Apple's use of certain (unannounced of course)protocols.
AH, yes...the "unannounced protocols" is the problem. I guess Apple cooked up that protocol while filming the fake moon landing in Area 51 with Santa Claus. Great theory, einstein. Hey, your tin foil hat could use another layer.
I am going to guess this is
I am going to guess this is "fix" is a blocking of Apple's use of certain (unannounced of course)protocols. Cisco only fault is in not blocking them earlier..just in case. That's my analysis! As the Cisco ad running on this page says..."welcome to the human network"
Right...
Your so-called "analysis" is based on what FACTS???
The anti-Apple crowd certainly can't seem to resist taking their digs, even when the available facts don't agree with them.
Not saying is couldn't be an Apple screw-up too, but all the information we have says it's Cisco's fault. Period. Anything else is plain SPECULATION.
???
I am going to guess this is "fix" is a blocking of Apple's use of certain (unannounced of course)protocols.
Dude, you must have missed the chapter on ARP resolution in your Junior MCSE book cause you are CON-FUSED about how networks operate.
But seriously, I don't think Apple has created any new layer 2 or 3 protocols for the iPhone.
If Cisco does not want to
If Cisco does not want to take responsibility for end-stations, they will take the blame, since end-stations are part of the wireless network. Something as big as the iPhone should have prompted some interoperability testing, but I believe all wireless infrastructure vendors are turning a blind eye (or ear) towards wireless end-stations, and vice-versa. WLANs are still maturing, many standards offering greater stability are not ready yet, yet vendors are vying for market-share in lieu of these standards, forming individual alliances or not. Until than, issues like this will continue.