BIRDv2 OSPF: Stub for loopback potentially broken: Invalid Prefix in LSA

[Kenth Eriksson]

On Mon, 2019-04-15 at 14:27 +0200, Ondrej Zajicek wrote:
> On Mon, Apr 15, 2019 at 12:21:12PM +0000, Kenth Eriksson wrote:
> > On Fri, 2019-04-12 at 14:24 +0200, Ondrej Zajicek wrote:
> > > CAUTION: This email originated from outside of the organization.
> > > Do
> > > not click links or open attachments unless you recognize the
> > > sender
> > > and know the content is safe.
> > > 
> > > 
> > > On Thu, Apr 11, 2019 at 08:38:44PM +0200, bauen1 wrote:
> > > > Hello,
> > > > 
> > > > I've been playing around with BIRD and OSPF for a while now and
> > > > ran
> > > > across an error I don't quite understand, while trying to get
> > > > BIRD
> > > > to
> > > > advertise ip addresses on the loopback interface on a debian 10
> > > > server.
> > > 
> > > Fixed by attached patch.
> > > 
> > 
> > Does this bug only apply to /32 addresses when running IPv4 over
> > OSPFv3? Or is it also relevant for OSPFv2? 
> 
> Only to IPv4 over OSPFv3.
> 
> > Does OSPFv3 (RFC5340 / RFC5838) handle unnumbered (/32) differently
> > from OSPFv2? 
> 
> Not in a significant way.
> 

So a /32 shall be implicitly re-distributed in the OSPF area both for
OSPFv2 and OSPFv3? I think that differs from how Quagga did it for
unnumbered interfaces.