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

2019-04-23 Thread Joakim Tjernlund
On Tue, 2019-04-23 at 19:33 +0200, Ondrej Zajicek wrote: > > On Tue, Apr 23, 2019 at 12:40:04PM +, Joakim Tjernlund wrote: > > > I think the standard just does not consider the case of 'unnumbered' > > > link with both local and remote address but without subnet and assumes > > > 'real'

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

2019-04-23 Thread Ondrej Zajicek
On Tue, Apr 23, 2019 at 12:40:04PM +, Joakim Tjernlund wrote: > > I think the standard just does not consider the case of 'unnumbered' > > link with both local and remote address but without subnet and assumes > > 'real' unnumbered PtP link with no local IP address associated with > > the

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

2019-04-23 Thread Joakim Tjernlund
On Tue, 2019-04-23 at 14:09 +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 Tue, Apr 23, 2019 at 10:28:46AM +, Kenth Eriksson

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

2019-04-23 Thread Ondrej Zajicek
On Tue, Apr 23, 2019 at 10:28:46AM +, Kenth Eriksson wrote: > > The second case is more complex. In OSPFv2, it always does not > > propagate > > /32 local addresses and it propagates /32 peer addresses only if > > configured as stub. In OSPFv3, this is not implemented and neither > > local > >

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

2019-04-23 Thread Kenth Eriksson
On Thu, 2019-04-18 at 13:55 +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 Mon, Apr 15, 2019 at 12:56:24PM +, Kenth Eriksson