I forgot to add, we are running 600 ap's on 12 controllers. Before the
start of next semester we will be adding a location appliance and
another 150 ap's and a few more controllers.
Phill Solomon
University of Melbourne
On 04/12/2008, at 18:35, Phill Solomon [EMAIL PROTECTED]
wrote:
We
Not sure what you mean by the prolong crash, but when we were running 4.1.x
and older code, we had random crashes, sometimes multiple controllers would
crash at the same time. Turns out there was a bug in the ssh code on the
controllers. Turned off ssh and no more problems (controllers were
Seven WiSMs running 4.2.112 without any known problems.
-jcw
-
John Watters UA: OIT 205-348-3992
-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:[EMAIL PROTECTED] On Behalf Of Leo Song
Sent: Wednesday,
8 WiSMs running on 4.2.130. No major issues.
Hector Rios
Louisiana State University
We have 4 WiSMs running 4.2.112 for the better part of a year with no
crashes at all. Our APs, about 800 total, are a mix of 1020s, 1230s, and
b/g/n only 1252s.
-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:[EMAIL PROTECTED] On Behalf Of Leo Song
We have been using the 3.3.2.x code line for a while now. We have not
enabled any of the advanced ARM 2.0 features yet. We are also
experiencing some weird issues with Macs on the N APs. Every once in a
while our MacBook Pros will throw up an alert that says Your Wireless
LAN has been
Hi Leo,
We run 4.2.130 in 3 4404 controllers. What are the symptoms of your crash
bug? Does the WiSM restart itself? or just hang there without forwarding
any traffic?
Manoj A.
American U.
Leo Song [EMAIL PROTECTED]
Sent by: The EDUCAUSE Wireless Issues Constituent Group Listserv
We were running 5.0 code and were having problems related to Rogue Detection.
One device would crash every 10 minutes, another every 3 hours and our other
two devices were okay. We disabled rogue detection and didn't have any further
crashing problems. When 5.1.151.0 came out we upgraded and
I might add that Cisco - in response to our crashing TAC - recommended we use
the latest Boot Software from the 4.2 code after installing the 5.1.151.0 code.
I notice that 5.2.157 code and boot software are out now. I hesitate to
upgrade, but would hope you could use the same version of code
What model Macbook Pro are you seeing this on?
I am using an early 2008 model, Currently connected to an AP 125, on
the N channel. I have not seen that sort of error message before.
-Brett
Brett Safford
Associate VoIP Network Engineer
Brandeis University
Work: 781-736-4607 / Cell:
I do know that it is standard (but concerning) practice to take the MIC
timer from 60 seconds down to zero to overcome clients that trigger the
countermeasure and thus cause what amounts to a DDOS- is sort of a
damned if you do, damned if you don't situation.
-Lee
Lee H. Badman
Wireless/Network
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lee H Badman wrote:
I do know that it is standard (but concerning) practice to take the MIC
timer from 60 seconds down to zero to overcome clients that trigger the
countermeasure and thus cause what amounts to a DDOS- is sort of a
damned if you
Sounds like TKIP countermeasures kicking in. A man-in-the-middle attack was
detected.
Bruce T. Johnson | Network Engineer | Partners Healthcare
Network Engineering | 617.726.9662 | Pager: 31633 | [EMAIL PROTECTED]
-Original Message-
From: The EDUCAUSE Wireless Issues Constituent
Has anyone seen or know of how this client-based TKIP notification manifests on
Cisco controllers?
Bruce T. Johnson | Network Engineer | Partners Healthcare
Network Engineering | 617.726.9662 | Pager: 31633 | [EMAIL PROTECTED]
-Original Message-
From: The EDUCAUSE Wireless Issues
From my understanding, is the latter.
Lee
Lee H. Badman
Wireless/Network Engineer
Information Technology and Services
Syracuse University
315 443-3003
-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:[EMAIL PROTECTED] On Behalf Of Joshua Wright
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After triggering countermeasures, WLC's will generate the following log
entry:
The AP '00:0b:85:67:6b:b0' received a WPA MIC error on protocol '1' from
Station '00:13:02:8d:f6:41'. Counter measures have been activated and
traffic has been suspended
And we have seen that dated NIC drivers and other conditions can also
trigger MIC errors on occasion- adding unreliability and confusion to
the process.
Lee H. Badman
Wireless/Network Engineer
Information Technology and Services
Syracuse University
315 443-3003
-Original Message-
From:
17 matches
Mail list logo