Mesh mode broken since 2.6.34-rc1

[Javier Cardona]

Hi Nick,

The commit that broke the mesh seems to be:

commit 8404080568613d93ad7cf0a16dfb68459b42a264
Author: Johannes Berg <johannes at sipsolutions.net>
Date:   Mon Feb 15 12:46:39 2010 +0200

    mac80211: reject unhandled action frames

    802.11-2007 7.3.1.11 mandates that we need to
    reject action frames we don't handle by setting
    the 0x80 bit in the category and returning them
    to the sender, so do that. In AP mode, hostapd
    is responsible for this.

    Additionally, drop completely malformed action
    frames or ones that should've been encrypted as
    unusable, userspace shouldn't see those.

    Signed-off-by: Johannes Berg <johannes at sipsolutions.net>
    Signed-off-by: Jouni Malinen <jouni.malinen at atheros.com>
    Signed-off-by: John W. Linville <linville at tuxdriver.com>

After that commit we observe invalid action category codes (0x9e) in
response to valid peer link open action frames (0x1e) and so no peer
links are established.  We don't have a fix at this time.

Cheers,

Javier


2010/3/24 Javier Cardona <javier at cozybit.com>:
> Nick,
>
> 2010/3/24 Ледовских Николай Валерьевич <nledovskih at mail.ru>:
>> Mesh mode does not work any more. I have some x86 MPs with 2.6.33.1, which work fine.
>> But there are establishment problems with 2.6.34-rc1.
>> The peering status changes between LISTEN, OPN_SNT and HOLDING, but does not reach ESTAB.
>
> Yes, confirmed on our testbed that wireless-testing commit
> 60b341b778cc2929df16c0a504c91621b3c6a4ad is good.  We'll investigate.
>
> Thanks,
>
> Javier
>
>
> --
> Javier Cardona
> cozybit Inc.
> http://www.cozybit.com
>



-- 
Javier Cardona
cozybit Inc.
http://www.cozybit.com