Re: [ovs-discuss] [SFC NSH] Update "eth_dst" for original packet after decap nsh encapsulation packet.

Hi Ben, thank for your I am sorry because I didn't show the encapsulation command. In this case, original packet is encapsulated 2 times, with nsh and ethernet headers. Here is the flow: table=0, n_packets=0, n_bytes=0, priority=30,tcp,in_port="tap09d8de0e-20",nw_src=10.10.0.111,nw_dst=

Re: [ovs-discuss] Inserting and using the compiled OVS kernel modules

Issue has just been solved, sorry for the avalanche of questions :) The solution was the following: I have created a directory for the new module: # mkdir /lib/modules/$(uname -r)/kernel/net/openvswitch2.10.0 Copy the compiled module(s) of the new openvswitch found in /lib/modules/$(uname

Re: [ovs-discuss] [SFC NSH] Update "eth_dst" for original packet after decap nsh encapsulation packet.

On Fri, Jan 11, 2019 at 04:26:03AM +0900, Hoàng Công Phước wrote: > Hi experts, > > I am trying to update "eth_dst" for original packet after decap nsh > encapsulation packet. Here is my command about it: > > $ sudo ovs-ofctl add-flow br-int "table=10, priority=1, dl_vlan=4, >

[ovs-discuss] [SFC NSH] Update "eth_dst" for original packet after decap nsh encapsulation packet.

Hi experts, I am trying to update "eth_dst" for original packet after decap nsh encapsulation packet. Here is my command about it: $ sudo ovs-ofctl add-flow br-int "table=10, priority=1, dl_vlan=4, dl_dst=fa:16:3e:05:3a:12, dl_type=0x894f, nsh_mdtype=1, nsh_spi=0x33, nsh_si=254,

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

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

Re: [ovs-discuss] Inserting and using the compiled OVS kernel modules

On 1/10/2019 3:37 AM, Levente Csikor wrote: Issue has just been solved, sorry for the avalanche of questions :) The solution was the following: I have created a directory for the new module: # mkdir /lib/modules/$(uname -r)/kernel/net/openvswitch2.10.0 Copy the compiled module(s) of the new

Re: [ovs-discuss] Cannot Add Meter in OVS 2.10.2

On 1/10/2019 12:34 AM, Ramzah Rehman wrote: Thank you so much. I was able to add meter now following this link . To build the Linux kernel module, I had to configure with --with-linux argument.

Re: [ovs-discuss] Cannot Add Meter in OVS 2.10.2

On 1/9/2019 10:41 PM, Ramzah Rehman wrote: I made sure while building that I use the module that was built from OVS sources by creating a config file as shown in Building section here: http://docs.openvswitch.org/en/latest/intro/install/general/ What else should I do to use the module from

Re: [ovs-discuss] Iperf3 measurement problems through OVS

Please share the result of ovs-ofctl dump-flows on each switch. Also, can you ping from one server to another? Best Regards, Ramzah Rehman On Mon, Oct 22, 2018 at 11:14 PM Zsolt Vági wrote: > Dear OVS Community! > > I work the following setup: on my server I run 5 VMs, 3 of which runs an >

Re: [ovs-discuss] Cannot Add Meter in OVS 2.10.2

Thank you so much. I was able to add meter now following this link . To build the Linux kernel module, I had to configure with --with-linux argument. Also, I had to delete the kernel's build-in