From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp5.epfl.ch (smtp5.epfl.ch [128.178.224.8]) by dpdk.org (Postfix) with ESMTP id 558B78DB5 for ; Tue, 10 Nov 2015 15:46:41 +0100 (CET) Received: (qmail 15197 invoked by uid 107); 10 Nov 2015 14:46:38 -0000 X-Virus-Scanned: ClamAV Received: from vpn-253-033.epfl.ch (HELO [128.179.253.33]) (128.179.253.33) by mail.epfl.ch (AngelmatoPhylax SMTP proxy) with ESMTP; Tue, 10 Nov 2015 15:46:38 +0100 To: users@dpdk.org References: <563CBFE3.5080804@epfl.ch> <563CC1D6.3030703@epfl.ch> From: Arseniy Zaostrovnykh Message-ID: <5642034D.8070406@epfl.ch> Date: Tue, 10 Nov 2015 15:46:37 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <563CC1D6.3030703@epfl.ch> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] Why packet_type is zero? X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Nov 2015 14:46:41 -0000 Is the pcap driver obsolete? L3fwd example(http://dpdk.org/doc/guides/sample_app_ug/l3_forward.html) check the mbuf field packet_type, and in the zero case (which is a default value, as far as I know) it does nothing. At the same time, only few drivers even mention this field: dpdk-2.1.0 $ grep packet_type drivers -Rl drivers/net/enic/enic_main.c drivers/net/e1000/igb_rxtx.c drivers/net/ixgbe/ixgbe_rxtx.c drivers/net/mlx4/mlx4.c drivers/net/i40e/i40e_rxtx.c drivers/net/mpipe/mpipe_tilegx.c drivers/net/vmxnet3/vmxnet3_rxtx.c drivers/net/fm10k/fm10k_rxtx.c drivers/net/cxgbe/sge.c And a PCap driver (drivers/net/pcap/rte_eth_pcap.c) specifically, does not alter the field, so L3fwd application drops all packets. On 06.11.2015 16:05, Arseniy Zaostrovnykh wrote: > Forgot to mention: > I tried KNI (first detaching eth1 and eth2 from the kernel) and pcap > PMD drivers, with: > dpdk-node $ sudo examples/l3fwd/build/app/l3fwd -c 0x01 -n 2 > --vdev=eth_pcap0,iface=eth2 --vdev=eth_pcap1,iface=eth1 -p 0x03 > --config="(0,0,0),(1,0,0)" > The sysptoms are identical. > > On 06.11.2015 15:57, Arseniy Zaostrovnykh wrote: >> Hello, >> >> I have the following setup of VirtualBox machines on a single host: >> node2: >> eth0: VBox NAT, connecting to the host internet >> eth1: 192.168.1.12/24 >> and additional route for 192.168.0.0/16 -> gateway 192.168.1.11 >> >> dpdk-node: >> eth0: VBox NaT, connecting to the host internet >> eth1: 192.168.1.11/24 >> eth2: 192.168.2.11/24 >> >> Now I run >> node2 $ ping 192.168.2.13 >> so, following the route, it sends the ping ICMP messages to >> 192.168.1.11 (dpdk-node). >> >> On the dpdk-node I run l3fwd: >> dpdk-node $ sudo examples/l3fwd/build/app/l3fwd -c 0x01 -n 2 -- >> -p 0x03 --config="(0,0,0),(1,0,0)" >> with APP_LOOKUP_METHOD = APP_LOOKUP_EXACT_MATCH, and with some >> debug-printfs. In particular I printf >> m->packet_type in the beginning of the l3fwd_simple_forward function. >> >> Question: >> Why does it prints 0? What is a possible causes? >> >> P.S. my DPDK version is 2.1.0; The printf is executed on each ping >> message; tcpdump shows no other traffic in this internal network. >> > -- Respectfully, Arseniy.