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
