[Commotion-dev] static BSSID?

Jeremy Lakeman Jeremy.Lakeman at gmail.com
Sat May 12 02:06:12 UTC 2012


I propose that the BSSID is generated as a hash of the SSID. This way
each mesh network will have a unique, but static BSSID without needing
the user to know it.

On Sat, May 12, 2012 at 3:33 AM, Hans-Christoph Steiner
<hans at guardianproject.info> wrote:
>
> The trickiest thing for the user of the OlsrMeshTether app remains the ad-hoc network associating.  If a bunch of phones are starting up at the same time, they can easily start associating with themselves in clusters.  Then there is multiple meshes that can't talk to each other.
>
> It seems a simple solution to this is to just hard-code the BSSID for Commotion in general as a default, then allow people to change this if they really want to.  I propose using CC:CC:CC:CC:CC:CC as the static BSSID.
>
> Is there any reason why we wouldn't want to use a static BSSID as the default?
>
> .hc
> _______________________________________________
> Commotion-dev mailing list
> Commotion-dev at lists.chambana.net
> http://lists.chambana.net/mailman/listinfo/commotion-dev
>



More information about the Commotion-dev mailing list