[Olsr-dev] does the current Debian olsrd.conf work with a mesh?
Fri Jun 29 19:29:38 CEST 2012
On 06/29/2012 01:06 PM, Teco Boot wrote:
> Your diagrams are almost useless. It is just a nice presentation of near SSIDs, it's channels and signal strengths. Utilization is not displayed.
Yes, if I was basing my decision off those two diagrams, that would be
useless. I am basing my experience of 10 years of surveys mostly around
NYC, but other places as well.
> Echoing others: don't use other channels than 1, 6 and 11. Otherwise, you will have interference with two "neighbor channels", instead of one.
Where I am, everywhere you go, you are going to overlap at least two
other signals, no matter which channel you choose.
> On BSSID: take the SSID, hash, flip same bits and you are fine.
> SSID: olsr.org
> SHA1: 6cece83d9271d5141f20fd563ae1986249acc1c4
> Take last 6 octets: 98.62.49.ac.c1.c4
> Set I/G-bit to 0, local bit to 1 (xxxx xx10): 9a.62.49.ac.c1.c4
The point of using ee:ee:ee:ee:ee:ee or 02:ca:ff:ee:ba:be is to clearly
show that this is a static, manually chosen BSSID. 9a.62.49.ac.c1.c4
does not show that.
The grand plan is to always use an algorithm to generate the BSSID from
the SSID and channel. I'll post our idea in a separate post.
> Op 29 jun. 2012, om 18:22 heeft Hans-Christoph Steiner het volgende geschreven:
>> On Jun 29, 2012, at 11:51 AM, Markus Kittenberger wrote:
>>>> Also i'd like to join Daniel in asking why channel 7?
>>> Maybe I'm biased by being in NYC, but whenever I do a scan, there are lots of APs on 1, 6, and, 11
>>> so 7 is not free too, as in 2.4ghz range channels are overlapping!
>> After looking at lots of graphs around the city that look like the ones attached, other channels besides 1,6,11 start to look quite appealing:
>> Olsr-dev mailing list
More information about the Olsr-dev