[Olsr-users] Optimal OLSR config file settings

[Randy Buck]

Thanks Markus.

Randy

On Tue, Feb 9, 2010 at 2:11 PM, Markus Kittenberger <
(spam-protected)> wrote:

> first question: which olsr verion(s) are u using?
>

Sorry I should have included this before: 0.5.6-r7



> i doubt that the hellos are the packets you loose,.. (they go only 1 hop)
>
> tcs/hnas/mids are more likely,..
>

Whatever packets are getting lost are indeed going only one hop.  I set up
tcpdump to monitor UDP packets on port 698 going out machine A to machine
B.  I filtered it such that I only saw packets from machine A on both
machines.  The result was, some packets going out A aren't getting to B.


> there is an compile time paramet in olsrd, that can show the validity times
> of all topology dat in the txtinfo-plugin,..
>
> i recommend that you have a look at this, to find out what information
> times out regulary, then you know where you have to change your settings
>

How is information timing out going to help?


>
> to activate this change follwing in lib/txtinfo/src/olsrd_txtinfo.h
> /* uncomment this to include VTime values into Link/Topology command */
> /* #define ACTIVATE_VTIME_TXTINFO */
>
> Looking into this.



> regards Markus
>
> On Tue, Feb 9, 2010 at 8:59 PM, Randy Buck <(spam-protected)>wrote:
>
>> Dear list (impersonal, yet true),
>>
>> We have been working with OLSR for some time now and have come up with the
>> following problem:
>>
>> OLSR loses routes when traffic other than the OLSR packets is on the
>> network.  Our OLSR packets (UDP port 698) are being prioritized over all
>> other traffic; this doesn't help.  We suspect the OLSR packets are colliding
>> with other packets in the air.
>>
>> With this in mind, we experimented with changing the HelloInterval to a
>> really short time (0.5 sec) and the HelloValidityTime correspondingly (5
>> sec).  We had the equation HelloValidityTime = HelloInterval * LQWindowSize
>> in mind when setting these values.  We assume the LQ window size is 10.  As
>> a side note, we know that LQ window size has been replaced by other
>> settings, but don't know how it has been changed or to what it has been
>> changed to.  If anyone can shed light on that, we would appreciate it. The
>> idea here is that if we send more packets in a shorter time, while we will
>> still lose packets once in a while, more will get through in the long run.
>>
>> Getting back to the problem, we are wondering if there are known "optimal"
>> settings for these types of fields in the config file.  We would like to
>> overcome the fact that some OLSR packets will be dropped due to things like
>> the hidden node problem.
>>
>> Thanks,
>>
>> Randy Buck
>>
>> --
>> Olsr-users mailing list
>> (spam-protected)
>> http://lists.olsr.org/mailman/listinfo/olsr-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20100209/a845bb47/attachment.html>