[Olsr-dev] does the current Debian olsrd.conf work with a mesh?

Hans-Christoph Steiner (spam-protected)
Fri Jun 29 03:18:26 CEST 2012

I think that's a good idea in the long run, but I won'y have time to
make that happen before the Debian/Wheezy freeze (June 30th).


On 06/28/2012 03:26 PM, Henning Rogge wrote:
> Whats about making a default based on ipv6? This would make it easy to
> prevent address collisions by the starting script.
> Henning
> Am 28.06.2012 21:20 schrieb "Hans-Christoph Steiner" <
> (spam-protected)>:
>> On 06/28/2012 03:06 PM, Daniel Nitzpon wrote:
>>> Am 28.06.2012 20:38, schrieb Hans-Christoph Steiner:
>>>> On 06/28/2012 02:34 PM, Markus Kittenberger wrote:
>>>>>> As for wireless hardware with bad ad-hoc support, this script isn't
>>>>>> going to make things worse for them.
>>>>> not for them, but for others! (-;
>>>> How?
>>> AKAIK most mesh networks tend to have the problem that it's too easy to
>>> connect to them rather than too difficult.
>>> We often have "black holes" resulting from HNA or firewall
>>> misconfiguration, that attract all traffic e.g. going out to the
>>> internet but then drop the packets instead of forwarding them.
>>> In similar ways double use of IP adresses, malfunctioning drivers, too
>>> high tx power settings etc. can render a mesh network unusable in
>> practice.
>>> The problem is in general that a user can ruin the network for all the
>>> others, in the worst case without even noticing anything himself. If you
>>> don't have any contact details of this user then, you're f**ed.
>>> I like the idea of having out-of-the-box connectivity to local meshes a
>>> lot, but this is definitely something that (if doable at all) needs a
>>> much more holistic approach than sensible olsrd.conf defaults.
>> Thanks, that was a useful description.  I think I'll go back to my
>> original idea with is and make the default setup have sensible defaults
>> in olsrd.conf then use these settings for the adhoc setup:
>> SSID: olsr.org
>> BSSID: cc:cc:cc:cc:cc:cc
>> channel: 7
>> ip address: 172.29.x.x with x being the last digits of the MAC
>> netmask
>> Ip4Broadcast
>> LinkQualityFishEye 1
>> LinkQualityAlgorithm "etx_ff"
>> This will let people easily start a mesh with whoever is nearby, but
>> make it harder for them to inadvertently connect to a mesh and mess it
>> up.  Do the above settings make sense?  I think "Ip4Broadcast
>>" and the use of InterfaceDefaults are the only changes
>> from the previous olsrd.conf that was included, besides text formatting.
>> .hc
>> --
>> Olsr-dev mailing list
>> (spam-protected)
>> https://lists.olsr.org/mailman/listinfo/olsr-dev

More information about the Olsr-dev mailing list