I think the operative words there are "recent client" --- we have many departments that purchase network-attached devices (scanners, utility monitors, touchpanels, etc.) that are expected to last for 7-10 years (or longer). Within the state budgeting system, there is no ability to amortize equipment or build up a life-cycle/refresh reserve (all unused dollars at the end of each fiscal year are reverted to the state treasury) - as such, it's all based on ability to get one time new-equipment funds -- hence the "last for 7-10 years (or longer)" environment.
Makes life interesting ...... -- jg / UNC From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Osborne, Bruce W Sent: Wednesday, November 28, 2012 11:14 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] interesting design recommendation from ...... Mike, Here at Liberty University, we only support WPA2-Enterprise and an open SSID that only permits non-802.1X devices registered by the user. We place some restrictions on the open network to encourage the use of the WPA2-Enterprise network. The sole exception is a hidden WEP network for some old Cisco wireless phones. Once they are retired, that network will disappear. When we supported WPA2-Personal, we only allowed AES encryption with no issues at all. Why allow TKIP, except for migration to AES? I have not seen any recent client that does not support WPA2, except for these old Cisco phones on a non-Cisco wireless network. Bruce Osborne Network Engineer IT Network Services (434) 592-4229 LIBERTY UNIVERSITY Training Champions for Christ since 1971 From: Mike King [mailto:m...@mpking.com] Sent: Wednesday, November 28, 2012 9:54 AM Subject: Re: interesting design recommendation from ...... Unfortunately James, I don't see support for WEP / TKIP going away anytime soon. WEP was broken in August of 2001. That was 11 years ago. WPA2 has been available since June 2004. That was 7 years ago. WPA with TKIP was "Only" published as a temporary measure, until WPA2 was ratified, and was supposed to cease being used when WPA2 was published. Yea, that didn't happen. No vendor want's to lose a sale because they weren't backward compatible. Only you (the operator of the network) has the power to draw the line in the sand, and say we will only support WPA2. (Let me know how that works out, since I would love to try that) Mike On Wed, Nov 28, 2012 at 9:42 AM, Gogan, James P <go...@email.unc.edu<mailto:go...@email.unc.edu>> wrote: We continue to see 75% or more of our user population hanging on with 2.4 devices ..... frustrating..... have to continue to engineer for the bulk of users being 2.4 for the foreseeable future. And while I'm venting - we're STILL having a hell of a time getting all of the departments that utilize utility monitoring devices, ticket scanners, classroom touch panels, etc. that ONLY support WEP and/or TKIP to upgrade their devices. In some cases, the response has been "we'll upgrade if you pay for it"; we keep telling them they're going to be screwed when the vendors drop support for those protocols. Oh, well - such is life with responsibility without authority. -- jg From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU<mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>] On Behalf Of Lee H Badman Sent: Wednesday, November 28, 2012 9:28 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU<mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> Subject: Re: [WIRELESS-LAN] interesting design recommendation from ...... Seems like there should be a bit more to the discussion... power levels, designing for 5 GHz and disable a 2.4 GHz radio or three along the way if too many, etc- expected % of clients expected in 5 vs 2.4 versus just a number of clients, etc. -Lee From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Gogan, James P Sent: Wednesday, November 28, 2012 9:23 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU<mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> Subject: [WIRELESS-LAN] interesting design recommendation from ...... We currently have a mix of Cisco (legacy) and Aruba (last two years) APs (although we're good at keeping any given building single brand, as much as possible). We've generally gone with an engineering rule of thumb of 20-30 clients per access point. We've noticed issues with channel flapping and inadequate load balancing on our Aruba APs in large classrooms where we have, based on our client per AP engineering, large numbers of APs. After an on-site visit from an Aruba engineer, his comment was that we have TOO MANY APs in our classrooms and high density areas. His recommendation (using the Aruba AP135s) was that we design based on 80 clients per AP (minimum 50, average 80, max 100), and to design based on 50 clients per AP for the older AP125s. I'd be curious to know what others think about that recommendation -- seems pretty significantly different from everything we've been told and designed for in the past. (BTW, the engineer also noted that he's not a sales guy and the sales guys would suggest differently -- figures). Thoughts? -- Jim Gogan ITS-Networking Univ of North Carolina at Chapel Hill ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.