[ovs-discuss] OFPACT_DEC_TTL in kernel space

[Sagar A]

Hello Justin,

Thank you for reply.
On Mon, Jun 24, 2019 at 5:39 PM Justin Pettit <jpettit at ovn.org> wrote:

> We try to implement the minimum interface that we can in the kernel.
> Usually the TTL doesn't change across a flow, so matching on a particular
> TTL value and setting a new value isn't a problem.  Plus, it allows us
> flexibility to stack multiple OpenFlow decrements (useful for logical
> routers, for example) to become a single modify action in the kernel.
>
> Is there a particular use-case that requires decrement?
>

I have rule which wants to match on 'dst_ip' only. Since, code is touching
'ttl', it becomes a match condition. For flows with same 'dst_ip' and
different ttls, result in different flows instead of having only one flow
with 'dst_ip' as match condition. Any suggestion to solve the problem?


>
> --Justin
>
>
> > On Jun 24, 2019, at 5:06 PM, Sagar A <ssadev42 at gmail.com> wrote:
> >
> > Hello,
> >
> > I see that there is an action OFPACT_DEC_TTL in user space, but not in
> kernel space for OVS. Is there a reason why kernel space action is not
> implemented? If one has to implement the kernel space action
> OFPACT_DEC_TTL, what will be the approach? The reason I want to have kernel
> space action OFPACT_DEC_TTL is that to avoid 'ttl' as the match condition
> in flow.
> >
> > Thank you.
> > _______________________________________________
> > discuss mailing list
> > discuss at openvswitch.org
> > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20190625/28e5b3a5/attachment.html>