need help

[YanBo]

On Thu, Sep 11, 2008 at 7:00 PM, Moritz Grauel
<grauel at informatik.hu-berlin.de> wrote:
> Hello,
>
> I am a student at the Humboldt University Berlin, Germany. I am
> trying to get 802.11s running in our wireless testbed, but I am
> experiencing a few problems.
>
> Our testbed consists of mipsel based netgear routers with atheros
> AR5213A based wifi-cards. I had no trouble compiling the drivers and
> the userspace tools.
>
> I can create mesh-devices, but the devices seem inactive. I am trying
> the following (based on the todo) on six different nodes, that can
> all see each other:
>
> $ #create device
> $ iw dev wmaster0 interface add mesh type mp mesh_id 42
>
> $ ifconfig -a | grep mesh
> mesh      Link encap:Ethernet  HWaddr 00:0F:B5:97:37:5C
>
> $ #set channel
> $ /usr/sbin/iwconfig mesh channel 1
>
> $ # assign ip
> $ ifconfig mesh 10.0.0.63
>
> $ iw dev mesh station dump
>
> $ ifconfig mesh up
>
> $ iw dev mesh station dump
>
> It seems, that the devices are not sending anything. But I have no
> idea why. dmesg does not show anything. If I create a monitor device
> with iw, it receives lots of packets - the mesh-devices receive nothing.
>
> If I try to create mpath next_hops, I get an error:
>
> $ iw dev mesh mpath set 00:0F:B5:97:36:54 next_hop 00:0F:B5:97:36:53
> nl80211 error -2
>
>
> Can someone please give me any advice or tips, how to get 802.11s
> working? I have no clue, what I am doing wrong and I need help.
>


If you don't apply this patch
http://marc.info/?l=linux-wireless&m=121739858214351&w=2 to ath5k
driver, the ath5k will not send mesh beacon after wake up, and hence
they can't find each other,  but after apply this  patch the ath5k
driver will lead to crash after work a while, as far as I know Andrey
Yurovsky was working for figure it out. don't know if this problem was
fixed so far. anywhere if worth to try this patch if you want the
ath5k full support 11s.

Yanbo