[Olsr-users] Multicast trafic over speedest and most reliable link,

[Henning Rogge]

Hi,

start with increasing the Hello/TC Interval and Validity time.

Henning

On Thu, May 5, 2016 at 1:15 PM, Taner Kurtulus <(spam-protected)> wrote:
> Ferry Thank you for advise, however we need a mash network at those speeds.
>
> Any ideas are welcomed.
>
> Regards
>
>
> On Thursday, 5 May 2016, Ferry Huberts <(spam-protected)> wrote:
>>
>>
>>
>> On 05/05/16 08:03, Taner Kurtulus wrote:
>>>
>>> Hi Henning,
>>>
>>> Thank you for the very fast response. So, now we will consider
>>> implementing our own multicast routing plugin.
>>>
>>> Before implementation we need more information about OLSRv2 and OLSR w/
>>> EXT.
>>>
>>>
>>> Is OLSRv2 has a plugin like BMF, even  as a dump flooder ?
>>>
>>>
>>>
>>> As I mentioned at my previous post we have two networks with different
>>> characteristics.  We couldn’t find best timeout values for HELLO, TC …
>>> messages.  OLSRv1 packets fills all network.
>>>
>>>
>>>
>>> Could you advise us configuration values for following networks for
>>> OLSRv1 with BMF
>>>
>>>
>>>
>>> 2 Kbps shared by 10 nodes
>>>
>>> 4 Kbps shared by 10 nodes
>>>
>>> 16 Kbps shared by 20 nodes
>>>
>>> 64 Kbps shared by 20 nodes
>>
>>
>>
>> These bandwidth are very low, I wouldn't advise running a mesh over those
>> kinds of networks.
>>
>>>
>>>
>>>
>>> Thanks in advance,
>>>
>>> Best Regards
>>>
>>>
>>>
>>>
>>> On Wed, May 4, 2016 at 4:15 PM, Henning Rogge <(spam-protected)
>>> <mailto:(spam-protected)>> wrote:
>>>
>>>     Hi,
>>>
>>>     both Olsrd and Olsrd2 are unicast routing protocols... BMF is just a
>>>     dumb flooder... olsrd2 contains no multicast forwarding at all.
>>>
>>>     You could get all the link metric topology data from olsrd/olsrd2,
>>> but
>>>     you would have to do the work yourself (the forwarding).
>>>
>>>     Henning Rogge
>>>
>>>     On Wed, May 4, 2016 at 2:06 PM, Taner Kurtulus <(spam-protected)
>>>     <mailto:(spam-protected)>> wrote:
>>>     > Hi All,
>>>     >
>>>     > We are planning to use OLSRv2 in order to decide best route for
>>>     multicast
>>>     > trafic. Best route can be described as over links which has
>>>     highest speed
>>>     > and link quality. Each OLSRv2 deamon will have at least two
>>>     interface, one
>>>     > has large capacity other has long link coverage with low speed.
>>>     >
>>>     > if we first link goes out of coverage, the other link should be
>>>     selected for
>>>     > routes.
>>>     >
>>>     > Is it possible to handle that scenario with OLSRv2 ? Or Do we need
>>>     to use
>>>     > OLSRv1 with BMF plugin. In that case link seed metric cannot be
>>>     used :( Am I
>>>     > right ?
>>>     >
>>>     > Thanks,
>>>     >
>>>     > Regards,
>>>     >
>>>     > --
>>>     > Olsr-users mailing list
>>>     > (spam-protected) <mailto:(spam-protected)>
>>>     > https://lists.olsr.org/mailman/listinfo/olsr-users
>>>
>>>
>>>
>>>
>>
>> --
>> Ferry Huberts