OSPF stuck in 2-way state

Ondrej Zajicek santiago at crfreenet.org
Tue Oct 8 11:34:16 CEST 2019


On Tue, Oct 08, 2019 at 07:53:53AM +0000, Kenth Eriksson wrote:
> On Tue, 2019-10-08 at 06:45 +0000, Kenth Eriksson wrote:
> > On Mon, 2019-10-07 at 18:34 +0200, Ondrej Zajicek wrote:
> > > On Mon, Oct 07, 2019 at 02:38:13PM +0000, Kenth Eriksson wrote:
> > > > > The prio change is user driven, the user changed from prio 0 to 5 and
> > > > > then re-configured. So now bird has prio 5 and quagga 0. Initially both
> > > > > ends had prio 0.
> > > > > 
> > > > Shouldn't the interface state machine be kicked when interface priority
> > > > is changed? E.g. from ospf_iface_reconfigure, invoke ospf_iface_sm with
> > > > state ISM_NEICH?
> > > 
> > > See commit fa1e0ba35416561bda3708ec808d24641dd8995f (fixed in 2.0.5)
> > > 
> > That fix is included in 2.0.5 but not in 2.0.6. Did you revert the fix
> > after that? 
> > 
> I noticed now that the fix is included in your gitlab version of 2.0.6.
> Did you by any chance move the 2.0.6 tag?   

If i remember correctly, we mistakenly released v2.0.6 tag pointing to some
older release (2.0.4?), then fixed it.

Proper 2.0.6 release commit is 5235c3f78da15826b0654ba68dc7a897faa42c98 .

What commit do you use? You can also check NEWS to see last version.

-- 
Ondrej Santiago Zajicek


More information about the Bird-users mailing list