[ovs-dev] [PATCH v2 6/7] actions: Make "next" action able to jump from egress to ingress pipeline.
Ben Pfaff
blp at ovn.org
Sat Jan 21 19:10:55 UTC 2017
On Fri, Jan 20, 2017 at 04:59:57PM -0800, Mickey Spiegel wrote:
> On Fri, Jan 20, 2017 at 2:48 PM, Ben Pfaff <blp at ovn.org> wrote:
>
> > This feature is useful for centralized gateways.
> >
> > Signed-off-by: Ben Pfaff <blp at ovn.org>
> >
>
> Acked-by: Mickey Spiegel <mickeys.dev at gmail.com>
>
> I think there is some missing functionality in ovn-trace.c.
> It looks to me like ovn-trace.c assumes that "next" actions
> always go to the next table, i.e. it ignores "(3)" or
> "(pipeline=ingress, table=3)". For my particular usage,
> egress loopback will only happen after NAT, so the trace
> will never reach the "next(pipeline=ingress, table=0)"
> action.
Ouch. Thanks for spotting that. There is an existing bug here in
ovn-trace, which should be fixed and backported, in addition to
overlooking the new feature in next. I'll add a new bug fix patch at
the beginning of the series, as well as revising this one.
More information about the dev
mailing list