<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 29, 2012, at 1:49 PM, Markus Kittenberger wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Fri, Jun 29, 2012 at 7:06 PM, Hans-Christoph Steiner <span dir="ltr"><<a href="mailto:hans@guardianproject.info" target="_blank">hans@guardianproject.info</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
IMHO, why would I blindly follow rules when I have actual, real world<br>
data that clearly demonstrates the problems with those rules?<br></blockquote><div>which are? </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
That wikipedia page shows the theory quite nicely, but it does not take<br>
into account so many real world factors.</blockquote><div>which are?</div><div><br></div><div>likely that too many people that think they are smarter than all others? </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It shows a picture of a clean<br>
room lab environment,</blockquote><div>read it again,.. </div><div><br></div><div>no this is no lab setup it just a chart showing the idea behind recommending this channels. </div><div><br></div><div>which btw are the optimum usage of the band!</div>
<div><br></div><div>and any user that uses another channel reduces the overall throughput in the band!</div><div><br></div><div>and as your scans showed that most networks in your region are actually on 1,6,11, the only ermaining thing to do, is choose the least used out of the 3.</div>
<div><br></div><div>and even if u measure e.g. real world data throughput on each channel, and find e.g. 8 to be the best, you (in 99 of 100 cases) still should not use any channel except 1, 6, 11 (-; </div><div><br></div>
<div>and especially not as a default for others!</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> where you have complete control over all of the<br>
radio waves in the 2.4GHz band.<br>
<br>
Working with radio waves means understanding the theory, but always<br>
basing decisions on real world measurement.</blockquote><div> </div><div>and a simple ssid scan is real world measurement, that helps you understanding what?? </div><div><br></div><div><div>btw to remind you:<br>this discussion was afair about what would be a wise default,..</div>
<div><br></div><div>which again is 1, 6, or 11</div><div><br></div><div>and btw why did you ask this question, if they only answer you want to hear is 7?</div></div><div><br></div><div>Markus</div></div>
</blockquote></div><br><div>Ug... sorry, this whole discussion has turned a bit silly. My aim was to provide quick snapshots to illustrate the idea I had in mind, to take the discussion beyond a wikipedia page that shows that wifi channels overlap. I would love to see more data to support the 1,6,11 only rule. I'm not convinced that is applicable in all situations. Many yes, all no. If you find this discussion pointless, feel free to ignore me.</div><div><br></div><div>Setting the channel to 7 is a minor experiment related to this. I am doing this in the Debian package because AFAIK, there is no current default working setup in the Debian package, and adding some optional settings won't mess with existing setups. It is quite unlikely that the network specified in the Debian package will ever get very widespread. But I do think that it will get more people interested and involved in mesh if it is really easy for them to get started.</div><div><br></div><div>.hc</div></body></html>