On Fri, May 28, 2021 at 10:32:06AM -0500, Matthew Smith via lists.fd.io wrote:
> Hi Mike,
>
> The first problem you mentioned (packets matching a route are not sent when
> the next hop has not been resolved at the time the route is added) is
> likely fixed by this patch:
>
> e2353a7f6 linux-cp:
On Fri, May 28, 2021 at 1:59 AM Mike Beattie wrote:
>
> # vppctl lcp default netns dataplane
>
> As the netlink listener doesn't appear to be re-created in that netns
> dynamically.
>
I can confirm that changing the default netns after startup of VPP does not
work, and your diagnosis is correct;
Hi Mike,
The first problem you mentioned (packets matching a route are not sent when
the next hop has not been resolved at the time the route is added) is
likely fixed by this patch:
e2353a7f6 linux-cp: Add delegate to adjacencies
It was merged after fd77f8c00, so you would either need to
On Thu, May 27, 2021 at 11:36:02AM +0200, Pim van Pelt wrote:
> Hoi Nate,
>
> further to what Andrew suggested, there are a few more hints I can offer:
>
> Then you should be able to consume the IPv4 and IPv6 DFZ in your router. I
> tested extensively with FRR and Bird2, and so far had good
