From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [45.249.212.189]) by dpdk.org (Postfix) with ESMTP id 8E31C2B91 for ; Wed, 7 Jun 2017 17:26:15 +0200 (CEST) Received: from 172.30.72.53 (EHLO NKGEML413-HUB.china.huawei.com) ([172.30.72.53]) by dggrg03-dlp.huawei.com (MOS 4.4.6-GA FastPath queued) with ESMTP id AOZ51306; Wed, 07 Jun 2017 23:26:08 +0800 (CST) Received: from FRAEML704-CAH.china.huawei.com (10.206.14.35) by NKGEML413-HUB.china.huawei.com (10.98.56.74) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 7 Jun 2017 23:26:07 +0800 Received: from FRAEML521-MBX.china.huawei.com ([169.254.1.104]) by FRAEML704-CAH.china.huawei.com ([10.206.14.35]) with mapi id 14.03.0301.000; Wed, 7 Jun 2017 17:26:02 +0200 From: "Avi Cohen (A)" To: "dpdk-ovs@lists.01.org" , "ovs-discuss@openvswitch.org" , "users@dpdk.org" Thread-Topic: OVS-DPDK - missing TNL_POP rule in flow table Thread-Index: AdLfolynhvbhK9RvRs27VPl4uL6+qA== Date: Wed, 7 Jun 2017 15:26:02 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.200.202.183] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.59381B11.0281, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.104, so=2014-11-16 11:51:01, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: bda5394316f746255dc75374cd93d1c8 Subject: [dpdk-users] OVS-DPDK - missing TNL_POP rule in flow table X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jun 2017 15:26:21 -0000 Hi All, After some investigations , thanks to - Chandran Sugesh - I want to be mor= e specific/targeted : The general problem is that VXLAN packet transmitted from ovs-dpdk-A is re= ceived @ovs-dpdk-B but not send to vxlan0 for decap because TNL_POP rule = is missing from the flow-table. Can someone tell me why this rule is missing ? Here is the dp flow-dump and vsctl-show - as you can see only TNL_PUSH rul= e exist but no TNL_POP Device B flow-dump from non-dpdk interfaces: recirc_id(0),in_port(4),eth(src=3D02:fb:9e:ce:f2:0d,dst=3D02:d7:d1:26:84:e5= ),eth_type(0x0800),ipv4(frag=3Dno), packets:1886, bytes:279128, used:0.801s= , actions:5 recirc_id(0),in_port(3),eth(src=3Dc6:96:20:43:ee:ab,dst=3Dfa:fc:41:d0:c5:2b= ),eth_type(0x0800),ipv4(tos=3D0/0x3,frag=3Dno), packets:1886, bytes:184828,= used:0.801s, actions:1,tnl_push(tnl_port(2),header(size=3D50,type=3D4,eth(= dst=3D02:d7:d1:26:84:e5,src=3D02:fb:9e:ce:f2:0d,dl_type=3D0x0800),ipv4(src= =3D172.31.100.44,dst=3D172.31.100.80,proto=3D17,tos=3D0,ttl=3D64,frag=3D0x4= 000),udp(src=3D0,dst=3D4789,csum=3D0x0),vxlan(flags=3D0x8000000,vni=3D0x3e8= )),out_port(4)) recirc_id(0),in_port(4),eth(src=3D02:fb:9e:ce:f2:0d,dst=3Dff:ff:ff:ff:ff:ff= ),eth_type(0x0806),arp(sip=3D172.31.100.44,tip=3D172.31.100.1,op=3D1/0xff),= packets:5, bytes:210, used:9.988s, actions:5 flow-dump from pmd on cpu core: 7 recirc_id(0),in_port(5),eth(src=3D02:d7:d1:26:84:e5,dst=3D02:fb:9e:ce:f2:0d= ),eth_type(0x8100),vlan(vid=3D2047,pcp=3D0),encap(eth_type(0x0800),ipv4(fra= g=3Dno)), packets:1898, bytes:288496, used:0.415s, actions:4 recirc_id(0),in_port(5),eth(src=3D02:97:78:a7:a9:2d,dst=3D02:fb:9e:ce:f2:0d= ),eth_type(0x8100),vlan(vid=3D2047,pcp=3D0),encap(eth_type(0x0806),arp(sip= =3D172.31.100.1,op=3D2/0xff,sha=3D02:97:78:a7:a9:2d)), packets:5, bytes:300= , used:9.988s, actions:4 ovs-appctl dpctl/show netdev@ovs-netdev: lookups: hit:6919 missed:141 lost:0 flows: 6 port 0: ovs-netdev (tap) port 1: br-int (tap) port 2: vxlan_sys_4789 (vxlan) port 3: veth0 port 4: br-phy (tap) port 5: dpdk0 (dpdk: configured_rx_queues=3D1, configured_tx_queues=3D4, m= tu=3D9000, requested_rx_queues=3D1, requested_tx_queues=3D33) =20 ovs-vsctl show 8cdae740-9eb3-4b79-ad6f-bca0652c5d54 Bridge br-int fail_mode: standalone Port "vxlan0" Interface "vxlan0" type: vxlan options: {remote_ip=3D"172.31.100.80"} Port "veth0" Interface "veth0" Port br-int Interface br-int type: internal Bridge br-phy fail_mode: standalone Port "dpdk0" Interface "dpdk0" type: dpdk options: {dpdk-devargs=3D"0000:00:03.0"} Port br-phy Interface br-phy type: internal Best Regards avi