TKIP Michael MIC problems

cisco

    Sponsored Links

    Next

  • 1. Is a Cisco router good enough to prevent intrusions or do I need a PIX as well?
    The above question is not for a business per-se but for home use.. I've got an 1841 router that I'll have running and was curious about whether or not it will suffice to work both as a router and also a firewall of sorts.. I see lots of information on the PIX firewall/VPN devices and while I have no current need for VPN services now, I'm curious if the firewall features on these devices are that much better than what a plain router is capable of.. Ultimately, I'd like something that will provide for more protection than what I'd normally get with a consumer based product (e.g. netgear,linksys,etc).. Thanks!
  • 2. cant ping aironet
    Two vlans on the ap: vlan1 (native) and vlan4. Bridge wirless to vlan1. The ap is not addressed in vlan1 (int bvi1, no ip address). An ethernet subinterface has been created, assigned to vlan4 and addressed. Communication to the subinterface address fails. The switch port to which the ap is connected to is properly configured (encap dot1q, mode trunk). My intention is to provide out-of-band management. I'm really a bit stumped at this point. switch interface FastEthernet0/18 switchport trunk encapsulation dot1q switchport mode trunk no ip address interface Vlan4 ip address 192.168.1.2 255.255.255.0 ap interface FastEthernet0.4 encapsulation dot1Q 4 ip address 192.168.1.21 255.255.255.0
  • 3. Problems using the extended ping command
    When I try to use the extended ping command and specify a source IP address I am receiving an 'invalid source' error. I have tried many different combinations but with no joy, it does, however, work if I specify an iterface (such as serial 0). I've also tried this on my 2611 router with the same results, even if I type '?' at the 'source address' prompt I still receive an eror message - does anyone have any ideas? TIA, Jase EAGLE2#ping Protocol [ip]: Target IP address: 192.168.1.2 Repeat count [5]: Datagram size [100]: Timeout in seconds [2]: Extended commands [n]: y Source address or interface: 192.168.3.2 % Invalid source Source address or interface: 10.0.0.1 % Invalid source Source address or interface: serial 0 Type of service [0]: Set DF bit in IP header? [no]: EAGLE2 uptime is 24 minutes System restarted by reload System image file is "flash:c2500-d-l_120-11.bin" cisco 2500 (68030) processor (revision L) with 6144K/2048K bytes of memory. Processor board ID 06110204, with hardware revision 00000000 Bridging software. X.25 software, Version 3.0.0. Basic Rate ISDN software, Version 1.1. 1 Token Ring/IEEE 802.5 interface(s) 2 Serial network interface(s) 1 ISDN Basic Rate interface(s) 32K bytes of non-volatile configuration memory. 8192K bytes of processor board System flash (Read ONLY) Configuration register is 0x2102

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 54 guest