2009-11-24 22:38:36

by Simon Perreault

[permalink] [raw]
Subject: Hardware for 802.11s

Hello,

I want to run 802.11s.

I tried a pair of Linksys WRT54GL v1.1 (Broadcom 5352) with the b43 driver,
kernel 2.6.30.9, OpenWRT trunk (r18526). Doesn't work. I don't see anything in
"iw ... station dump".
Side question: is this expected behaviour?

Can anyone recommend something I can buy on which 802.11s will work? I couldn't
Google anyone saying e.g. "I used the ACME Router 1.0 and it worked."

Thanks,
Simon
--
DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server --> http://numb.viagenie.ca
vCard 4.0 --> http://www.vcarddav.org


2009-11-24 22:56:16

by Pat Erley

[permalink] [raw]
Subject: Re: Hardware for 802.11s

Simon Perreault wrote:
> Hello,
>
> I want to run 802.11s.
>
> I tried a pair of Linksys WRT54GL v1.1 (Broadcom 5352) with the b43 driver,
> kernel 2.6.30.9, OpenWRT trunk (r18526). Doesn't work. I don't see anything in
> "iw ... station dump".
> Side question: is this expected behaviour?
>
> Can anyone recommend something I can buy on which 802.11s will work? I couldn't
> Google anyone saying e.g. "I used the ACME Router 1.0 and it worked."

I don't have time tonight, but I believe you can make b43 work by triggering a
scan after bringing the interface up. I know I've made b43 work in the past.

Pat Erley




2009-11-26 20:24:30

by Simon Perreault

[permalink] [raw]
Subject: Re: Hardware for 802.11s

Andrey Yurovsky wrote, on 2009-11-25 10:35:
> Can you please use a sniffer on the channel you
> picked (it's channel 1 by default) and confirm that you see mesh
> beacons from your devices once you "ifconfig up"?

We just tried this and did not see *anything*.

Thanks,
Simon
--
DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server --> http://numb.viagenie.ca
vCard 4.0 --> http://www.vcarddav.org

2009-11-25 15:36:55

by Pat Erley

[permalink] [raw]
Subject: Re: Hardware for 802.11s

On Wed, 25 Nov 2009 10:34:48 -0500, Simon Perreault
<[email protected]> wrote:
> Rui Paulo wrote, on 2009-11-25 09:45:
>> Try iwlist mesh0 scanning.
>
> The output of that looks very much like that of "iw dev mesh0 scan" with
> different formatting.
>
> It doesn't help. "iw dev mesh0 station dump" is still empty.

Did you do that on both ends? What is the full procedure you're using to
set up the mesh interfaces on the nodes?

Pat Erley

2009-11-25 15:35:22

by Andrey Yurovsky

[permalink] [raw]
Subject: Re: Hardware for 802.11s

On Tue, Nov 24, 2009 at 2:56 PM, Pat Erley <[email protected]> wrote:
> Simon Perreault wrote:
>> Hello,
>>
>> I want to run 802.11s.
>>
>> I tried a pair of Linksys WRT54GL v1.1 (Broadcom 5352) with the b43 driver,
>> kernel 2.6.30.9, OpenWRT trunk (r18526). Doesn't work. I don't see anything in
>> "iw ... station dump".
>> Side question: is this expected behaviour?
>>
>> Can anyone recommend something I can buy on which 802.11s will work? I couldn't
>> Google anyone saying e.g. "I used the ACME Router 1.0 and it worked."
>
> I don't have time tonight, but I believe you can make b43 work by triggering a
> scan after bringing the interface up. ?I know I've made b43 work in the past.

The scanning workaround is needed to deal with bugs in the ath9k and
rt2x00 drivers, however there was no problem with b43 last time I
checked. The station dump should show you output provided that you
have more than one mesh node within range, with the same mesh ID, and
on the same channel. Can you please use a sniffer on the channel you
picked (it's channel 1 by default) and confirm that you see mesh
beacons from your devices once you "ifconfig up"? Thanks,

-Andrey

2009-11-25 15:43:37

by Simon Perreault

[permalink] [raw]
Subject: Re: Hardware for 802.11s

[email protected] wrote, on 2009-11-25 10:36:
>> The output of that looks very much like that of "iw dev mesh0 scan" with
>> different formatting.
>>
>> It doesn't help. "iw dev mesh0 station dump" is still empty.
>
> Did you do that on both ends?

Yes.

> What is the full procedure you're using to
> set up the mesh interfaces on the nodes?

<boot 1st WRT54GL>
<boot 2nd WRT54GL>

On 1st:
# iw phy0 interface add mesh0 type mp mesh_id mesh
# ifconfig mesh0 up
# ifconfig mesh0 10.0.0.1

On 2nd:
# iw phy0 interface add mesh0 type mp mesh_id mesh
# ifconfig mesh0 up
# ifconfig mesh0 10.0.0.2

The next step is sniffing the 802.11 packets, as Andrey Yurovsky suggested. I'll
keep you posted.

Thanks,
Simon
--
DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server --> http://numb.viagenie.ca
vCard 4.0 --> http://www.vcarddav.org

2009-11-25 13:49:57

by Simon Perreault

[permalink] [raw]
Subject: Re: Hardware for 802.11s

Thanks for your reply.

Pat Erley wrote, on 2009-11-24 17:56:
> I don't have time tonight, but I believe you can make b43 work by triggering a
> scan after bringing the interface up. I know I've made b43 work in the past.

What do you mean, "triggering a scan"? What command line does that translate into?

I've tried all variations of "iw ... scan ..." I could think of and eventually I
got this:

root@OpenWrt-2:~# iw dev mesh0 station dump
Station 00:21:29:8a:e6:01 (on mesh0)
inactive time: 811216 ms
rx bytes: 546
rx packets: 13
tx bytes: 334
tx packets: 5
signal: -6 dBm
tx bitrate: 1.0 MBit/s
mesh llid: 0
mesh plid: 0
mesh plink: LISTEN

Yay, a blip!!!

But the other WRT54GL still shows nothing, and of course I still can't ping.

Thanks,
Simon
--
DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server --> http://numb.viagenie.ca
vCard 4.0 --> http://www.vcarddav.org

2009-11-25 15:34:42

by Simon Perreault

[permalink] [raw]
Subject: Re: Hardware for 802.11s

Rui Paulo wrote, on 2009-11-25 09:45:
> Try iwlist mesh0 scanning.

The output of that looks very much like that of "iw dev mesh0 scan" with
different formatting.

It doesn't help. "iw dev mesh0 station dump" is still empty.

Thanks,
Simon
--
DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server --> http://numb.viagenie.ca
vCard 4.0 --> http://www.vcarddav.org

2009-11-25 14:45:37

by Rui Paulo

[permalink] [raw]
Subject: Re: Hardware for 802.11s

On 25 Nov 2009, at 13:50, Simon Perreault wrote:

> Thanks for your reply.
>
> Pat Erley wrote, on 2009-11-24 17:56:
>> I don't have time tonight, but I believe you can make b43 work by
>> triggering a
>> scan after bringing the interface up. I know I've made b43 work in
>> the past.
>
> What do you mean, "triggering a scan"? What command line does that
> translate into?

Try iwlist mesh0 scanning.

--
Rui Paulo


2009-12-01 19:40:12

by Andrey Yurovsky

[permalink] [raw]
Subject: Re: Hardware for 802.11s

On Thu, Nov 26, 2009 at 12:24 PM, Simon Perreault
<[email protected]> wrote:
> Andrey Yurovsky wrote, on 2009-11-25 10:35:
>> Can you please use a sniffer on the channel you
>> picked (it's channel 1 by default) and confirm that you see mesh
>> beacons from your devices once you "ifconfig up"?
>
> We just tried this and did not see *anything*.

Sorry for the late reply but I just tried a b43 card (PCMCIA in my
case, FW 410.2160, BCM4318) and mesh is working fine, and I do see
beacons when I "ifconfig up". This is with today's wireless-testing.

-Andrey