The "known" weak IV ranges for both 64 and 128-Bit may not be enough to filter. There are may be other ranges that have not been discovered. So putting weak IV filter is a band-aid solution. I do not think Cisco would ever use it. As stated by NDOSHI, Cisco TKIP and MIC features are far better solution. Please read my articles about TKIP in: http://wlanresearch.com/LEAPVPN.htm
It is indeed a band-aid and it is a nice layer to add to defense in depth. TKIP and MIC are ceratinly valuable. I am already familiar with them.
The reason for my question was to find out how high the WEP cracking risk is to cisco devices with WEP enabled and not using TKIP or MIC. Based on what I have learned so far the various techinques available to crack WEP keys will fail with Cisco gear due to apparent weak iv filtering. It is not an advertised or supported feature but none the less it appears to be in use on Cisco wireless gear. They would be foolish not to implement it. Evidence also indicates several competitors have adopted weak iv filtering.
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
This is the start of a display filter cross reference between Wireshark and OmniPeek.
The 1st installment is a table of advanced filters. More filters will be added as time allows.
It is a living doc, so check back for changes every so often
Please feel ...
I have created a Powershell script to automatically add a Wireless Guest User on Cisco WLCs. (tested on 2500 Series)
The script should be completely self explanatory.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...