Re: [vpp-dev] Capturing Packets with Particular Ethertypes

2017-07-28 Thread Luke, Chris
Anyone can edit the wiki, hint hint :)

Chris.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Alessio Silvestro
Sent: Friday, July 28, 2017 14:13
To: John Lo (loj) <l...@cisco.com>
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Capturing Packets with Particular Ethertypes

Thanks, that was the issue.

It would be nice to have such information in the wiki page.

It would help people to work with VPP :)

Alessio

On Thu, Jul 27, 2017 at 8:58 PM, John Lo (loj) 
<l...@cisco.com<mailto:l...@cisco.com>> wrote:
Hi Alessio,

The mechanism you are using to handle ethertype works only when the interface 
is in L3 mode which is the default, unless an interface is set to L2 bridging 
(or xconnect) mode. When an interface is in L2 mode, VPP will always get into 
l2-input mode to forward ethernet packet based on ethernet header and not care 
about ethertype of the packet. From your description, the interface appear to 
be in L2 mode.

Regards,
John

From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> 
[mailto:vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io>] On 
Behalf Of Alessio Silvestro
Sent: Thursday, July 27, 2017 12:16 PM
To: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
Subject: [vpp-dev] Capturing Packets with Particular Ethertypes

Dear all,

I am trying to capture packets with a particular Ethertype.

Let's say I want the ethertype 0x2323.

I first define the new protocol type in vpp/srv/vnet/ethernet/types.def

ethernet_type (0x2323, MY_PROTOCOL)
Thus, I created and registered a new node "my_node".

In the init function of my_node I call the function:

ethernet_register_input_type (vm, MY_PROTOCOL ,my_node.index);


I compile and run vpp. When I send the packet with the new ethertype, my node 
is not invoked.

In particular, the result of show trace tells me that the packet is arriving at 
the interface.The new procotol is recognized but the chain of node is 
dpdk-input -> ethernet-input -> l2-input -> l2-output -> 
TenGigabitEthernet7/0/1-output.

The wiki page 
(https://wiki.fd.io/view/VPP/Modifying_The_Packet_Processing_Directed_Graph) 
does not mention anything else.

Do you have an idea where could be the problem or what is missing?

Thanks.

Best regards,
Alessio


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Capturing Packets with Particular Ethertypes

2017-07-28 Thread Alessio Silvestro
Thanks, that was the issue.

It would be nice to have such information in the wiki page.

It would help people to work with VPP :)

Alessio

On Thu, Jul 27, 2017 at 8:58 PM, John Lo (loj)  wrote:

> Hi Alessio,
>
>
>
> The mechanism you are using to handle ethertype works only when the
> interface is in L3 mode which is the default, unless an interface is set to
> L2 bridging (or xconnect) mode. When an interface is in L2 mode, VPP will
> always get into l2-input mode to forward ethernet packet based on ethernet
> header and not care about ethertype of the packet. From your description,
> the interface appear to be in L2 mode.
>
>
>
> Regards,
>
> John
>
>
>
> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
> Behalf Of *Alessio Silvestro
> *Sent:* Thursday, July 27, 2017 12:16 PM
> *To:* vpp-dev@lists.fd.io
> *Subject:* [vpp-dev] Capturing Packets with Particular Ethertypes
>
>
>
> Dear all,
>
>
>
> I am trying to capture packets with a particular Ethertype.
>
>
>
> Let's say I want the ethertype 0x2323.
>
>
>
> I first define the new protocol type in vpp/srv/vnet/ethernet/types.def
>
>
>
> ethernet_type (0x2323, MY_PROTOCOL)
>
> Thus, I created and registered a new node "my_node".
>
>
>
> In the init function of my_node I call the function:
>
>
>
> ethernet_register_input_type (vm, MY_PROTOCOL ,my_node.index);
>
>
>
>
>
> I compile and run vpp. When I send the packet with the new ethertype, my
> node is not invoked.
>
>
>
> In particular, the result of show trace tells me that the packet is
> arriving at the interface.The new procotol is recognized but the chain of
> node is dpdk-input -> ethernet-input -> l2-input -> l2-output
> -> TenGigabitEthernet7/0/1-output.
>
>
>
> The wiki page (https://wiki.fd.io/view/VPP/Modifying_The_Packet_
> Processing_Directed_Graph) does not mention anything else.
>
>
>
> Do you have an idea where could be the problem or what is missing?
>
>
>
> Thanks.
>
>
>
> Best regards,
>
> Alessio
>
>
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Capturing Packets with Particular Ethertypes

2017-07-27 Thread John Lo (loj)
Hi Alessio,

The mechanism you are using to handle ethertype works only when the interface 
is in L3 mode which is the default, unless an interface is set to L2 bridging 
(or xconnect) mode. When an interface is in L2 mode, VPP will always get into 
l2-input mode to forward ethernet packet based on ethernet header and not care 
about ethertype of the packet. From your description, the interface appear to 
be in L2 mode.

Regards,
John

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Alessio Silvestro
Sent: Thursday, July 27, 2017 12:16 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Capturing Packets with Particular Ethertypes

Dear all,

I am trying to capture packets with a particular Ethertype.

Let's say I want the ethertype 0x2323.

I first define the new protocol type in vpp/srv/vnet/ethernet/types.def

ethernet_type (0x2323, MY_PROTOCOL)
Thus, I created and registered a new node "my_node".

In the init function of my_node I call the function:

ethernet_register_input_type (vm, MY_PROTOCOL ,my_node.index);


I compile and run vpp. When I send the packet with the new ethertype, my node 
is not invoked.

In particular, the result of show trace tells me that the packet is arriving at 
the interface.The new procotol is recognized but the chain of node is 
dpdk-input -> ethernet-input -> l2-input -> l2-output -> 
TenGigabitEthernet7/0/1-output.

The wiki page 
(https://wiki.fd.io/view/VPP/Modifying_The_Packet_Processing_Directed_Graph) 
does not mention anything else.

Do you have an idea where could be the problem or what is missing?

Thanks.

Best regards,
Alessio

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev