[Commotion-dev] nailing down the default mesh network

[Hans-Christoph Steiner]

I like the idea that Paul outlines about letting communications, as long as it
doesn't cause problems.  It sounds like Jeremy is saying it can cause
problems, like if two meshes with different LinkQualityAlgorithms are on the
same channel/BSSID, the olsrds might feed each other bad info and corrupt the
other meshes.  Is that what you're thinking Jeremy?

.hc

On 05/02/2013 07:34 PM, Jeremy Lakeman wrote:
> Serval may be forgiving, but if your olsr config doesn't match, it may lead
> to undefined behaviour....
> 
> 
> 
> On Fri, May 3, 2013 at 8:10 AM, Paul Gardner-Stephen <paul at servalproject.org
>> wrote:
> 
>> Hello,
>>
>> While it is true that all needs to match to get multi-hop connectivity
>> through the mesh, if BSSID + channel match (or even channel is +/- 2) then
>> single-hop traffic will be possible between nodes of different meshes,
>> which can still be helpful and transfer/share useful information.  Rhizome
>> could certainly use this kind of connection to transfer data.
>>
>> Changing the BSSID doesn't reduce the interference of colocated meshes, it
>> just stops the packets from being visible to each other.  To my mind
>> forcing separation of traffic like this is counter-productive to the goals
>> of distributed communications.  In short, I prefer the "if in doubt, allow
>> communications" approach.
>>
>> So I agree with the doctor that the BSSID should not change.
>>
>> Paul.
>>
>>
>> On Fri, May 3, 2013 at 2:05 AM, Hans-Christoph Steiner <
>> hans at guardianproject.info> wrote:
>>
>>>
>>>
>>> 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
>>>
>>>
>>> _______________________________________________
>>> Commotion-dev mailing list
>>> Commotion-dev at lists.chambana.net
>>> https://lists.chambana.net/mailman/listinfo/commotion-dev
>>>
>>>
>>
>> _______________________________________________
>> Commotion-dev mailing list
>> Commotion-dev at lists.chambana.net
>> https://lists.chambana.net/mailman/listinfo/commotion-dev
>>
>>
>