Re: [ovs-discuss] Way to distinguish different packets rather than parsing a packet?

2019-01-14 Thread Ben Pfaff
The Ethertype and IP protocol are in different layers. Parsing the Ethertype does not determine the IP protocol. On Tue, Jan 15, 2019 at 01:46:04PM +0800, Krish wrote: > Thanks Ben for the response. > > I just want to distinguish it for some testing purposes. > > Can you please explain a bit

Re: [ovs-discuss] Way to distinguish different packets rather than parsing a packet?

2019-01-14 Thread Krish
Thanks Ben for the response. I just want to distinguish it for some testing purposes. Can you please explain a bit about the following behavior? I want to get the **ip_proto** from a packet. In dp_netdev_input__**, * *ip_proto** is always 0. But when I debugged *miniflow_extract*,

Re: [ovs-discuss] Way to distinguish different packets rather than parsing a packet?

2019-01-10 Thread Ben Pfaff
On Thu, Jan 10, 2019 at 02:34:47PM +0800, Krish wrote: > Is there any other way to distinguish different types of packets/flows when > they enter dp_netdev_input__ and processed further(EMC,fastpath etc)? > > As of now, I have to *flow_extract* the packets using *struct flow flow*: > > if

[ovs-discuss] Way to distinguish different packets rather than parsing a packet?

2019-01-09 Thread Krish
Is there any other way to distinguish different types of packets/flows when they enter dp_netdev_input__ and processed further(EMC,fastpath etc)? As of now, I have to *flow_extract* the packets using *struct flow flow*: if (flow.nw_proto == IPPROTO_TCP && l4_size >= TCP_HEADER_LEN) I want to