Hi
The version of compat-wireless are:
In nanostation 5:
root@OpenWrt:/# cat /sys/module/compat/parameters/compat_version
compat-wireless-2012-07-13
In nanostation m5:
root@OpenWrt:/# cat /sys/module/compat/parameters/compat_version
compat-wireless-2011-11-29
I do not know how to see directly the beacons, can I use iw phy o some similar?
But when I use the comand:
iw dev meshif station dump
in nanostation 5 throws:
root@OpenWrt:/# iw dev meshif station dump
Station 00:27:22:84:7f:5f (on meshif)
inactive time: 470 ms
rx bytes: 33133
rx packets: 1000
tx bytes: 608
tx packets: 9
tx retries: 0
tx failed: 0
signal: -49 dBm
signal avg: -48 dBm
tx bitrate: 6.0 MBit/s
rx bitrate: 6.0 MBit/s
mesh llid: 46561
mesh plid: 36503
mesh plink: ESTAB
authorized: yes
authenticated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
and in nanostation m5:
root@OpenWrt:/# iw dev meshif station dump
Station 00:27:22:52:78:d0 (on meshif)
inactive time: 210 ms
rx bytes: 187417
rx packets: 4625
tx bytes: 419
tx packets: 7
tx retries: 0
tx failed: 0
signal: -28 dBm
signal avg: -31 dBm
tx bitrate: 6.0 MBit/s
rx bitrate: 6.0 MBit/s
mesh llid: 47795
mesh plid: 13998
mesh plink: ESTAB
si it seems that they are using the same bit rate, can it be?
It is weird cause this info:
authorized: yes
authenticated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
is not present on the information throwed by the station dump command.
could it be that a problem with versions?
should i try with another version of openwrt and kmod-ath5k?
Thanks you very much for the hints
Regards
Esteban
2012/8/16 Thomas Pedersen <[email protected]>:
> Hi Esteban,
>
> On Thu, Aug 16, 2012 at 07:56:49PM -0500, Esteban Municio wrote:
>> I am working in a rural development project in Peru
>
> Cool!
>
>> and we are having some problems implementing the mesh with 802.11s.
>
> Not cool :(
>
>> The nanostation5 have installed openWRT Bleeding Edge, r33006 and the
>> nanostation M5 have installed Backfire (10.03.x Snapshot, r32751)
>
> Which version of compat-wireless are you running?
>
>> When I configure the mesh, I see from the nanostation m5 only other
>> nanostation m5 nodes, but neither nanostation 5 nodes...
>> And from the nanostation 5, I only see the nanostation 5 nodes...
>> So I can make ping between the nodes of the mesh formed by the same device
>> type
>>
>> I am using the same channel 161 for all the nodes.The only difference
>> is that nanostation5 only have 80211a and nanostation m5 have 80211a
>> and 80211n. The drivers of nanostation 5 are ath5k and of the
>> nanostationm5 are ath9k.
>
> In recent kernels, o11s will determine its own BSSBasicRateSet based on
> the phy supported rates and refuse to peer if peer candidates are
> advertising a different BSSBasicRateSet. The mandatory PHY rates should
> be chosen by default, but perhaps there is some bug or the 5 and m5s are
> on different sides of this version divide. Can you please inspect the 5
> and m5 beacons and report back if these match?
>
>> The configuration they have is:
>>
>> Code:
>> ifconfig wlan0 down
>> iw dev wlan0 interface add meshif type mp
>> iw dev meshif set channel 161
>> ifconfig meshif inet 192.168.3.81 netmask 255.255.255.0
>> ifconfig meshif up
>> iw dev meshif mesh join netmesh
>
> This looks fine.
>
>> What is happening? have I configure it differently?
>
> No, they've proably configured themselves differently :). A patchset
> allowing you to configure the BSSBasicRateSet through nl80211 and iw is
> still in the works.
>
> Thomas
> _______________________________________________
> Devel mailing list
> [email protected]
> http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
--
Esteban
_______________________________________________
Devel mailing list
[email protected]
http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
