[Commotion-dev] nailing down the default mesh network

[Hans-Christoph Steiner]

On 05/02/2013 10:40 AM, The Doctor wrote:
> On 05/01/2013 04:17 PM, Hans-Christoph Steiner wrote:
> 
>> As for the BSSID, I think we should probably use a unique BSSID to 
>> prevent collisions with other mesh networks.  02:ca:ff:ee:ba:be is 
>> used by a number of other meshes.  It really could be any valid 
>> adhoc BSSID like 02:02:02:02:02:02
> 
> If you change the BSSID, you will break interoperability with other
> projects.  Please do not do that.

For true interoperability, the whole mesh profile needs to match:

SSID
BSSID
channel
IP scheme
LinkQualityAlgorithm

The problem with 02:CA:FF:EE:BA:BE for the default BSSID for a lot of
different, incompatible meshes.  For example, Freifunk and Funkfeuer use that
BSSID for some of there OLSR meshes, but since those OLSR meshes use the
LinkQualityAlgorithm etx_ff and commotionwireless.net uses the incompatibile
etx_ffeth, even if they have the same BSSID can channel, they will be separate
meshes.

As far as I understand it, the traffic from the incompatible mesh will then
just be interference.

.hc

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 939 bytes
Desc: OpenPGP digital signature
URL: <http://lists.chambana.net/pipermail/commotion-dev/attachments/20130502/bfcc82ac/attachment.sig>