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

[Teco Boot]

Here, the link local is on the tunnel, right? Unexpected things can happen. Can we be sure both ends have same MTU? What is the effect if they are different?

If you mean we should circumvent fragmentation, I fully agree.

Happy Christmas,
Teco



> Op 24 dec. 2014, om 23:32 heeft Henning Rogge <(spam-protected)> het volgende geschreven:
> 
> PMTUD for link local multicast?
> 
> Henning
> 
> Am 24.12.2014 15:41 schrieb "Teco Boot" <(spam-protected) <mailto:(spam-protected)>>:
> DF=1 and no PMTUD makes no sense.
> Having a function that circumvent fragments is great. But set DF and discard PTB messages is wrong.
> 
> If both sides of a link have different MTU, there could still be a problem.
> 
> Teco
> 
> > Op 24 dec. 2014, om 12:48 heeft Henning Rogge <(spam-protected) <mailto:(spam-protected)>> het volgende geschreven:
> >
> > On Wed, Dec 24, 2014 at 10:46 AM, Jernej Kos <(spam-protected) <mailto:(spam-protected)>> wrote:
> >> Hello!
> >>
> >> The absence of HELLOs led me to investigate the MTUs more closely and it
> >> now seems that there is actually some issue with MTU discovery on the
> >> broker side -- nodes configure the correct MTU towards the broker, but
> >> the broker sometimes fails to configure correct MTU towards the nodes.
> >>
> >> So this may be the cause of the problem and not OLSR as HELLOs from the
> >> server might then be dropped as being too large when received at the
> >> node. Will report back when I determine what is causing this.
> >
> > Yes, I could see this becoming a problem.
> >
> > olsrd uses the advertised MTU to make the packets as small as
> > necessary and mark them as "do not fragment"... if the MTU is wrong,
> > the packets might be dropped.
> >
> > Henning Rogge
> >
> > --
> > Olsr-users mailing list
> > (spam-protected) <mailto:(spam-protected)>
> > https://lists.olsr.org/mailman/listinfo/olsr-users <https://lists.olsr.org/mailman/listinfo/olsr-users>
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20141225/236f2a4c/attachment.html>