From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lane, Todd
Sent: Thursday, November 29, 2012 5:33 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] interesting design recommendation from ..
gt;>
Date: Thursday, November 29, 2012 3:36 PM
To: EDUCAUSE Listserv
mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>>
Subject: Re: [WIRELESS-LAN] interesting design recommendation from ..
Mike,
This is what we’re being told by Aruba.
“WEP / TKIP will be unsupported starting in a future rel
Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Mike King
Sent: Wednesday, November 28, 2012 9:54 AM
To:
WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU<mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>
Subject: Re: [WIRELESS-LAN] interesting design recommendation from
I agree with Lee
The challenge is to create physically small cells to support throughput
requirements. If the APs are in an open room with nothing between them -
the management system is killing itself trying to adjust for co-channel
interference. Cisco RRM will shut them down to the lowest power
S-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
4) 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 soo
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
You never know what people are going to do so all you can do is take the
protocol to the limit in high density areas. They might try to fire up
video conferencing via wireless or tell everyone on the class to down load
a file to their laptops. There could be a major event and everyone whips
out t
___
>
> __ __
>
> *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
&g
without authority.
>
> ** **
>
> -- jg
>
> ** **
>
> *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:
> WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] *On Behalf Of *Lee H Badman
> *Sent:* Wednesday, November 28, 2012 9:28 AM
> *To:* WIRELESS-LAN@LIST
2012 9:28 AM
To: 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 ex
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
Subject: [WIRELESS-LAN] interesting design recommendation from ..
We currently have a mix of Cisco (legacy) and Aruba
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 flappin
13 matches
Mail list logo
