TKIP Michael MIC problems

cisco

    Sponsored Links

    Next

  • 1. San Francisco city network locked down
    SAN FRANCISCO CITY SYSTEM ENGINEER LOCKS OUT ADMINS Various news sources report that an employee of the city of San Francisco's IT department had the only administration access into a FiberWAN system powered by Cisco equipment. He received poor performance reviews at work and was accused of abusing his access. He was ordered to leave work on July 9th, 2008. After being "let go", the city realized that they did not have access into their systems and demanded that the former employee hand over his account passwords. The individual provided false information and was arrested for four felony counts of computer tampering. Bail was sent at $5,000,000. The mayor of the city met with him the following week and the former employee provided account access information to allow other administrators back into the system. While the system continued to function, administrator access was denied to anyone else until the mayor regainged access for the IT staff. The public defender's office stated that they would withdraw their representation due to a conflict of interest.
  • 2. 2600 series router using SDM
    Cisco 2615XM router with SDM 2.4.1 I'm trying to get PC's on a LAN to access a default gateway adsl router so they can surf the internet but I'm stuck at the Cisco 2615XM router Here is my setup: small LAN of PC's all connected by cables to a hub, all ip's set on 192.168.1.xx Cisco 2615XM router also connected to the hub on Fastethernet port 0/1, set as as 192.168.1.70, set as LAN Cisco 2651XM Fastethernet port 0/0, DHCP set port to 192.168.1.64 set as WAN, connected by cable to Cisco wireless access point (configured as a universal workgroup bridge). The Cisco access point ip is 192.168.1.66 and it is connected wirelessly to a non-cisco adsl router on the internet (default gateway 192.168.1.254). I'm trying to get the PC's on the LAN to access the default gateway router so they can surf the internet but I'm stuck at the 2615XM router. The PC can see both FastEthernet ports but I can't get the PC to see the Cisco access point on 192.168.1.66. In SDM/Interfaces and Connections I did Test Connection but the test fails at Checking Exit Interface, the recommended actions say: 'Select User-Specified option or add host specific/network specific/default route through this interface and retest connection'. I'm not sure where I'm supposed to go in SDM to do this, I've tried different things but fail to create the route so if anyone can help me put the right settings into SDM that'd be great. Thanks for any help.
  • 3. 1721 Maximum memory SDRAM
    I have a 1721 with 32MB onboard. It will handle up to 128MB. If I put in a 128MB SDRAM will this work? IE will the extra memory be ignored? There are 96MB SDRAM's available but they are somewhat pricy. Also can I use the same memory that is used in the 1751, 1751-V, 1760, 1760-V, 2610XM, 2611XM, 2620XM, 2621XM, 2650XM and 2651XM group? PS the specs seem to be SDRAM, Non-ECC, PC133, 100-pin, 3.3V DC, Time/Speed: 7.5 ns The reason I ask is that Advanced Enterprise Services seems to need 128MB. thanks

TKIP Michael MIC problems

Postby Fernando Enriquez » Sat, 02 Jul 2005 06:27:51 GMT

Hi everyone:

We've set up a complex installation for one client based on 40 Cisco 
1200 & 1100 APs working as parent-repeater (we have some branches with 
parent-repeater-repeater). We've deployed LEAP on APs and clients both. 
Everything is working fine until any client changes from one AP to 
another. When it starts to transmit traffic it gets blocked because of 
MIC encryption error. The situation remains for a few minutes, when 
suddenly encryption works again.

To minimize impact we have enables key-rotation every 20 seconds but the 
problem remains and users aro not able to work properly.

To validate users we have installed freeradius with leap support. Radius 
log shows that authentication is working fine (no errors)

This is a log excerpt of what happens when client 0040.96a7.c594 
desassociates from AP 192.168.4.207 and associates to AP 192.168.4.200




Re: TKIP Michael MIC problems

Postby Uli Link » Sat, 02 Jul 2005 17:50:48 GMT

Fernando Enriquez schrieb:

It's a feature to block a station after a number of MIC failures.
But this should not happen with allowed, legitimate stations.


What's the fw and driver version of your clients?

For the 350 series the very first fw supporting WPA with TKIP was 5.30.17.

What's the config of your APs? What's the IOS version on you APs?
The 350 series does not work with cipher set to TKIP+WEP (migration mode)

Tip: set up one low traffic AP as WDS, this will allow fast secure roaming.
For 350 clients I prefer CCKM over WPA, you can allow both on a SSID.

-- 
Uli


Re: TKIP Michael MIC problems

Postby Fernando Enriquez » Wed, 06 Jul 2005 00:15:49 GMT

I updated FW on clients and APs both to latest versiones a couple of
weeks ago but problem persists.



Cipher is pure TKIP, not migration mode.



I will try WDS to see if using this the roaming gets smoother. I will
tell you.



Thanks a lot for your interest





Similar Threads:

1.TKIP MIC failures

Hey

Ive got a few AP1200's that Ive just deployed. Most only have 1 or 2
associations right now as Im ramping it up for production.

Ive got 1 client an IBM laptop with an Intel 2200BG card that keeps
causing these errors on the AP.

%DOT11-4-TKIP_MIC_FAILURE_REPORT: Received TKIP Michael MIC failure
report from the station 000e.3568.a238 on the packet (TSC=0x0)
encrypted and protected by pairwise key.

I see these 1 every few minutes, sometimes it will happen more often
and then the radio interface is put on hold and all my WPA clients are
disassociated. All WPA clients diassociated is bad.

%DOT11-3-TKIP_MIC_FAILURE_REPEATED: Two TKIP Michael MIC failures were
detected within 0 seconds on Dot11Radio0 interface. The interface will
be put on MIC failure hold state for next 60 seconds.


So I read some about these messages and they point to someone attackign
my AP but these are being generated by MAC Addrs that are friendly.

Heres the rundown on my setup,  Cisco AP1200's IOS 12.3(2)JA configed
for WPA \TKIP  with a MS IAS RADIUS server backend.

Anyone ever see these errors before ?  Thanks

Timo

2.WPA/TKIP with AP1200

Hi gurus

I'm trying to configure an Windows XP SP1 supplicant with Patch Q815485 
with my laptop HP Nx7010. Initially I work with EAP-TLS + WPA TKIP & 
AP1200, it seems to work fine but after a few seconds the connection is 
broken and supplicant doesn't reconnect with the AP.
HAve you found this issue ?

Can you help me?

Thanks

Manel

3.Cisco ACS 3.3 and Windows 2003 IAS using EAP-TLS and TKIP

I was wondering has anyone every setup using Cisco ACS 3.3 (Radius)
with Windows 2003 IAS to authenicate with PKI cards for wireless and if
so what sets should I follow.  TIA

4.TKIP vs Broadcast Key Rotation

In some of the Cisco documentation, they state that broadcast key rotation
(BKR) "is an excellent alternative to TKIP if your wireless LAN supports
wireless client devices that are not Cisco devices or that cannot be
upgraded to the latest firmware for Cisco client devices."

I don't really understand how this is true. If BKR is only rotating the keys
for broadcast frames, then the user's session (unicast) key isn't touched
by this mechanism, right? So, the classic WEP cracking vulnerabilities
still apply, right?

Must be something I'm missing here... who can enlighten me?

Thanks,
Mike

5.Security of Cisco TKIP implementation on older products

Hello
I am still using Cisco AIR-352 with 12.3(8) IOS as access point, to provide 
connectivity on my wlan ad 802.11b speeds, with WPA-PSK TKIP security.

I have on a site, two AIR-BR352 point to point links at about 4km.
The bridges BR350 uses Wep128 security, and I know that it is unsecure.
On the config pages, I have enable MIC and TKIP settings.

So in the end I have these options enabled:
WEP 128
CISCO MIC
TKIP

This is the extract from cisco's documentations about the two options.


# Message Integrity Check (MIC) -- MIC is an additional WEP security feature 
that prevents attacks on encrypted packets called bit-flip attacks. The MIC, 
implemented on both the access point and all associated client devices, adds 
a few bytes to each packet to make the packets tamperproof.

# Temporal Key Integrity Protocol (TKIP) -- TKIP, also known as WEP key 
hashing, is an additional WEP security feature that defends against an 
attack on WEP in which the intruder uses an unencrypted segment called the 
initialization vector (IV) in encrypted packets to calculate the WEP key.

In the end, these bridges are in WEP128, but are they vulnerable to the 
common wep flaws (IV vector, and vulnerable to airsnort's scans)  ?

To be secure, I use a GRE+IPSEC (at the moment using DES encryption, later I 
will use AES128) tunnel between the two sites connected via the wifi 
bridge, to be more secure.



 

6. Cisco WLC - WPA MIC Errors.....all AP's same syptoms

7. IP phone i2004 audio mic level is low

8. 2 line headset with common mic?



Return to cisco

 

Who is online

Users browsing this forum: No registered users and 40 guest