Re: [ovs-discuss] OFPACT_DEC_TTL in kernel space

2019-06-25 Thread Justin Pettit
> On Jun 25, 2019, at 2:02 PM, Sagar A wrote: > >> 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 diffe

Re: [ovs-discuss] OFPACT_DEC_TTL in kernel space

2019-06-25 Thread Sagar A
Hello Justin, Thank you for reply. On Mon, Jun 24, 2019 at 5:39 PM Justin Pettit 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, i

Re: [ovs-discuss] OFPACT_DEC_TTL in kernel space

2019-06-24 Thread Justin Pettit
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, fo

[ovs-discuss] OFPACT_DEC_TTL in kernel space

2019-06-24 Thread Sagar A
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