"received packet without ExtIV flag" repeating messages

Bug #105235 reported by Patrick J. LoPresti
8
Affects Status Importance Assigned to Milestone
ieee80211 (Ubuntu)
Invalid
Undecided
Unassigned
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

I recently upgraded to Feisty beta on my Dell Latitude D610. Network driver is ipw2200.

My WPA network connection seems to work, but every 1-3 seconds the following kernel message is logged:

  CCMP: received packet without ExtIV flag from xx:xx:xx:xx:xx:xx

...where the MAC address is my wireless access point (a Linksys WRT54GS running dd-wrt).

The connection does seem to be working, but I am wondering what these messages are trying to convey and what I should do about them.

Revision history for this message
Christian Kujau (christiank) wrote :

I just wanted to add a "me too"

 * Ubuntu Feisty, iBook G4 (powerpc)
 * uname -a
    Linux foobar-g4 2.6.20-15-powerpc #3 Sun Apr 15 06:45:49 UTC 2007 ppc GNU/Linux
 * 0001:10:12.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)
 * using bcm43xx as the kernel module, "wext" as WPA driver
 * AP is a Netgear WPN802v2

CCMP: received packet without ExtIV flag from 00:14:6c:7c:dc:9a
TKIP: replay detected: STA=00:18:4d:89:c9:8e previous TSC 000000000000 received TSC 000000000000

Note: 00:18:4d:89:c9:8e is the HW address from the AP, I could not find out the origin of the first HW address (this is different than the report from Patrick)

Any thoughts?

Thanks,
Christian.

Revision history for this message
hackel (hackel) wrote :

I too am getting this, and like Christian, I do not know the source of the MAC address sending out the bad packets. (I do not get his TKIP line) It concerns me a great deal, since I'm getting this on my laptop, NOT on my access point! I've searched the logs on my AP and can't find any mention of that MAC address. Where could it be coming from? Could it be originating from the internet? I didn't think that would trigger a CCMP error. If anyone has any ideas on this issue, I would really appreciate it!

Revision history for this message
Caroline Ford (secretlondon) wrote :

This isn't the ieee80211 module

Changed in ieee80211:
status: New → Invalid
Revision history for this message
Christian Kujau (christiank) wrote :

Since I've upgraded to Gutsy, I don't see these messages any more. As the messages did not seem to harm functionality, and others might use Gutsy too, I'd probably like to see this bug closed...

Thanks,
Christian.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 or 9.04?

Changed in ipw2100:
status: New → Incomplete
Revision history for this message
Christian Kujau (christiank) wrote :

I don't think it is. Error logging got revised in mainline

commit aeb998c124786e8c7fbd6eab347230469e911872
Author: Larry Finger <email address hidden>
Date: Mon Apr 9 11:24:41 2007 -0500

    [PATCH] ieee80211-crypt: Make some TKIP and CCMP error logging conditional

    There are messages arising from ieee80211_crypt that spam the logs
    of casual users. These are changed to be logged only if the user
    specifically requests the IEEE80211_DEBUG_DROP messages. In either
    case, the error/drop count is incremented.

    Signed-off-by: Larry Finger <email address hidden>
    Signed-off-by: John W. Linville <email address hidden>

And IEEE80211_DEBUG_DROP is not set in Hardy, I doubt it's set in later versions.

$ grep IEEE80211_DEBUG /boot/config-2.6.24-22-xen
# CONFIG_IEEE80211_DEBUG is not set

Revision history for this message
Andres Mujica (andres.mujica) wrote :

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.