Slashdot Mirror
Duke Wireless Problem Caused by Cisco, not iPhone
jpallas writes "Following up to a previous Slashdot story, it now turns out that the widely reported problems with Duke University's wireless network were not caused by Apple's iPhone. The problem was actually with their Cisco network. Duke's Chief Information Officer praises the work of their technical staff. Does that include the assistant director for communications infrastructure who was quoted as saying, "I don't believe it's a Cisco problem in any way, shape, or form?""
go back and read the slashdot article on the subject when this first came out. Dozen of slashdot guys were reporting that cisco routers and WAP's have a flaw that would enable just such a solution and that you had to patch the routers with a patch that Cisco already had made.
Cisco makes some solid equipment, but when they let flaky stuff loose it's really flaky. It is also not something you announce to the world first, without throughly checking out your own equipment first, especially when the iPhone was working perfectly fine with tens of thousands of other access points around the country.
i thought once I was found, but it was only a dream.
Juniper for routers. Extreme for Network Switches. Juniper/Netscreen, Fortinet, or even Checkpoint for firewalls. Intruvert for IDP. Aventail for VPN. Aruba for Wireless.
Even a Vyatta or other OSS router is as good as or better than all but the biggest, and most horribly expensive, Ciscos.
But you knew that, because you couldn't point to any evidence that refuted my opinion that Cisco has more than just market share in common with MS.