Hello Justin, Thank you for reply. On Mon, Jun 24, 2019 at 5:39 PM Justin Pettit <[email protected]> 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 <[email protected]> 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 > > [email protected] > > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > >
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
