Hi Neale, Yes, the fix is working. :-)
-nagp On Tue, May 30, 2017 at 2:39 PM, Neale Ranns (nranns) <nra...@cisco.com> wrote: > > > HiNagp, > > > > Does this work for you? > > https://gerrit.fd.io/r/#/c/6918/ > > > > /neale > > > > *From: *<vpp-dev-boun...@lists.fd.io> on behalf of "Neale Ranns (nranns)" > <nra...@cisco.com> > *Date: *Tuesday, 30 May 2017 at 09:28 > *To: *Nagaprabhanjan Bellaru <nagp.li...@gmail.com>, vpp-dev < > vpp-dev@lists.fd.io> > *Subject: *Re: [vpp-dev] VPP crashes with "ip probe-neibhbor <intf> > <addr>" for a /31 subnet neighbor > > > > > > Hi Nagp, > > > > It’s not expected. > > > > /neale > > > > *From: *<vpp-dev-boun...@lists.fd.io> on behalf of Nagaprabhanjan Bellaru > <nagp.li...@gmail.com> > *Date: *Monday, 29 May 2017 at 17:43 > *To: *vpp-dev <vpp-dev@lists.fd.io> > *Subject: *[vpp-dev] VPP crashes with "ip probe-neibhbor <intf> <addr>" > for a /31 subnet neighbor > > > > Hi, > > VPP in the latest builds crashes with the probe-neighbor command for a /31 > neighbor. > > That is, if I have configured 10.2.2.4/31 on an interface and probe > 10.2.2.5, VPP crashes at adj_get() because in the > ip4_add_del_interface_route function, the neighbor_adj_index is not set for > a /31 route (it is treated as a special case). > > Is this expected? > > Thanks, > > -nagp > >
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
