<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>Op 29 jun. 2012, om 20:50 heeft Markus Kittenberger het volgende geschreven:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br><br><div class="gmail_quote">On Fri, Jun 29, 2012 at 8:40 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">
<div style="word-wrap:break-word"><div class="im"><br><div><div>On Jun 29, 2012, at 2:34 PM, Markus Kittenberger wrote:</div><br><blockquote type="cite"><br><br><div class="gmail_quote">On Fri, Jun 29, 2012 at 8:25 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">
<div style="word-wrap:break-word"><div><div><br><div><div>On Jun 29, 2012, at 1:57 PM, Markus Kittenberger wrote:</div><br><blockquote type="cite"><br><br><div class="gmail_quote">On Fri, Jun 29, 2012 at 7:29 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>
Here's our idea for a standard algorithm for generating a static BSSID<br>
based on the SSID and the channel. Aaron suggested using the channel<br>
directly in the BSSID to lower the risk of conflicts. Basically,<br>
networks with the same BSSID on different channels will work, </blockquote><div>yes but many devices will actually connect to each other on such a setup.</div><div>of course with quite bad reception as the channel is wrong,</div>
<div><br></div><div>(in the lab with afair some bulelts this worked up to an offset of 15mhz!)</div><div><br></div><div>-> use different BSSID</div><div><br></div><div>Markus</div></div>
</blockquote></div><br></div></div><div>Do you have a suggestion how to do this in an algorithm? </div></div></blockquote><div>just encode the channel into the bssid<br><br><div>btw i just meant do not use the same bssid for different channels,..</div>
<div>(which is what aaron suggested to avoid conflicts) and which you comemnted, with "basically it would work"</div><div><br></div><div>so i felt it might be a good idea, to tell what kind of conflicts/issues you get with the same BSSID.</div>
<div><br></div><div>this btw is also a reason to NOT use the same CA:FE BA:BE bssid for different channels</div></div></div>
</blockquote><br></div></div><div>I'm confused. The proposal I sent already includes the channel in two bytes of the generated BSSID. Am I missing something?</div></div></blockquote><div>sry for casuing another confusion,..<br>
<br></div><div>i was not commetning on your bssid proposal, but on the statement that using the same bssid on different channels would work,..</div><div><br></div><div>as yes it works, but not really as one would expect,..</div>
<div><br></div><div>as most people do not expect that one router on channel 1 can (quite well) exchange data with another router on channel 2</div><div>or will have an very high ETX link in olsrd to another router on channel 3,..</div></div></blockquote><div><br></div><div>Users expect that nodes with same SSID do communicate.</div><div>I understand the bad link with neighbor channels.</div><div><br></div><div>Define SSID "olsr-(channel)", then the BSSID hash. Everybody happy...</div><div><br></div><div>Teco</div><div><br></div><br><blockquote type="cite"><div class="gmail_quote"><div>thats all,..</div><div><br></div><div>Markus</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><span class="HOEnZb"><div>
<br></div><div style="color:rgb(136,136,136)">.hc</div><br></span></div></blockquote></div><br>
-- <br>Olsr-dev mailing list<br><a href="mailto:Olsr-dev@lists.olsr.org">Olsr-dev@lists.olsr.org</a><br>https://lists.olsr.org/mailman/listinfo/olsr-dev</blockquote></div><br></body></html>