[Olsr-users] OLSR routing issue with highly connected node

[Henning Rogge]

olsrd already looks at the MTU value of an interface and should not
send packets large enough that they must be fragmented. If that
doesn't work its a bug.

Henning

On Mon, Dec 22, 2014 at 8:44 AM, Teco Boot <(spam-protected)> wrote:
> Can we unset the DF flag, so olsrd can use IP fragmentation if something goes wrong keeping UDP packets <= MTU?
>
> Teco
>
>
>> Op 22 dec. 2014, om 08:33 heeft Henning Rogge <(spam-protected)> het volgende geschreven:
>>
>> Can you do a look into the txtinfo output of the node?
>>
>> Is the 1-hop/2-hop neighbor table okay?
>>
>> I assume that the problem is somewhere in the Hello
>> generation/processing but I would like to be sure before going onto a
>> wild hunt.
>>
>> Henning Rogge
>>
>> On Mon, Dec 22, 2014 at 8:31 AM, Jernej Kos <(spam-protected)> wrote:
>>> Hello!
>>>
>>> On 21. 12. 2014 22:04, Henning Rogge wrote:
>>>> So you are using the normal (unmodified) olsrd code and just have
>>>> links which might (or might not) have a lower MTU?
>>>
>>> We are using the unmodified olsrd code, version 0.6.7.1. VPN links have
>>> different MTU values because our VPN tunnels perform PMTU discovery and
>>> adapt the tunnel MTU accordingly.
>>>
>>> To handle this on the server side, we use one bridge per MTU value (so
>>> VPN clients with the same MTU are all on the same bridge). And then we
>>> have all the bridges configured in olsrd as interfaces.
>>>
>>>
>>> Jernej
>>>
>>
>> --
>> Olsr-users mailing list
>> (spam-protected)
>> https://lists.olsr.org/mailman/listinfo/olsr-users
>