Apparently it is fixed in a few different trains:
http://blogs.cisco.com/tag/802-11w/
Pete Morrissey
-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Curtis K. Larsen
Sent: Wednesday, October 24, 201
It's machine-dependent, and not global in nature. There's no extra charge for
that.
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Mike King
Sent: Wednesday, October 24, 2012 3:43 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
You know Lee,
There is an email from you on August 30th saying your're not seeing this
problem. Go Figure.
Danny, here's the info from the list archive:
Just as an FYI for those running Cisco, I noticed today that 7.0.235.3 was
released on Sep 11 2012 for both 4400 series and 5508 series contro
Great - we got the bootloader, and I'll talk with my teammates about
upgrading the WLC code to 7.0.235 as well. Ugh!
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Robert Owens
Sent: Wednesday, October 24, 2012 2:44 PM
T
We were in the same predicament with WISM 1s. There is a new code release
7.0.235 that has the fix available from Cisco. Also has an updated Boot
Loader. No such luck with earlier releases.
Robert Owens
Kansas State University
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[ma
According to the bug notes here:
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCua29504
...It says it is fixed in 7.0.230.15.
Thanks,
-Curtis
On 10/24/2012 01:31 PM, Danny Eaton wrote:
Any idea how this would be negated with controllers runn
Any idea how this would be negated with controllers running 7.0.230.0, as we
do not have WiSM-2's, and therefore cannot go to the 7.2.x code.
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lee H Badman
Sent: Wednesday, Oc
I have just verified this- controller update to recommended version does indeed
bring compatibility with Win 8 standard native driver and eliminates the need
to go driver shopping for each machine.
Thanks, Robert.
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELES
If You are in the Cisco Controller based world. There is an update that
needs to be applied to your controllers. We did that this last weekend and
now are able to authenticate with the few Windows 8 test machines we have
with latest drivers. Has to do with an incompatibility with 802.11w that
is r
Seeing lots of upgraded Win 8 machines that fail on 802.1x with stock Win 8
driver, need to roll back to Win 7 driver or go to Intel, Broadcom, etc for a
driver that works.
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[WIRELESS-LAN@LISTSERV.EDU
We started using XpressConnect this year and haven't had any issues with
Windows 8 Costumer Preview. It was actually the test bed I used to configure
XpressConnect. I also just tested a PC on our domain with Xpressconnect and
it seemed to work just fine. As for the drivers I am unaware of any
We've not gotten XpressConnect to work happily with Windows 8 yet, so I'm
interested in this as well.Have sent an email to Cloudpath Support on this,
but I'm guessing all Windows 8 questions are awaiting the official Friday
release.
-- Jim Gogan / UNC-Chapel Hill
From: The EDUCAUSE Wireles
I'm curious if anyone has gotten Windows 8 devices configured for 1x, using
Xpressconnect. I realize there are lots of issues with
Windows 8 drivers that make this complicated, so I'm just wondering how it is
working when the drivers are capable.
Thanks,
Pete Morrissey
**
Participation
13 matches
Mail list logo
