[j-nsp] ospfv3 - JUNOS sends zero mtu in dbd -> stuck in ExStart

[Volker D. Pallas]

Hi Daniel,

thank you for your reply.
I've read the RFC now and you're right. I opened a bug report with quagga regarding this issue:
https://bugzilla.quagga.net/show_bug.cgi?id=602
OSPFv3 on quagga seems to be a bit buggy in general, I'm still waiting for a fix of another
problem (bug #600).

Thanks again and
have a good night,

Volker

On 06/16/10 08:49, Daniel Roesen wrote:
 > On Wed, Jun 16, 2010 at 03:39:47AM +0200, Volker D. Pallas wrote:
 >> I'm having an issue with an OSPFv3 neighborship between Linux/quagga
 >> (0.99.16) and JUNOS (10.1R2.8 on SRX-100) via a standard "ip"-tunnel:
 >> the dbd info sent by JUNOS always contains "mtu 0", which quagga does
 >> not like at all. This keeps my neighborship in ExStart.
 >
 > According to the OSPFv3 spec (RFC2740), JUNOS is correct in sending
 > MTU 0 on a tunnel interface:
 >
 > Interface MTU
 >        The size in bytes of the largest IPv6 datagram that can be sent
 >        out the    associated interface, without fragmentation.  The MTUs
 >        of common Internet link  types can be found in Table 7-1    of
 >        [Ref12]. Interface MTU should be set to 0 in Database Description
 >        packets sent over virtual links.
 >
[...]
 > I'd say Quagga is wrong to expect anything else than MTU 0 on a
 > tunnel type interface...
 >
 > Best regards,
 > Daniel
 >