From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id 79597C866 for ; Mon, 22 Jun 2015 04:40:10 +0200 (CEST) Received: from [192.168.1.160] (99-34-229-174.lightspeed.sntcca.sbcglobal.net [99.34.229.174]) by mail.mhcomputing.net (Postfix) with ESMTPSA id 7B33280C003; Sun, 21 Jun 2015 19:37:33 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Matthew Hall In-Reply-To: Date: Sun, 21 Jun 2015 19:40:06 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <1083FAEE-6E00-4B35-9626-20EBAE6F21F2@mhcomputing.net> References: To: Daeyoung Kim X-Mailer: Apple Mail (2.1878.6) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] DPDK packet capture question X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jun 2015 02:40:10 -0000 On Jun 21, 2015, at 5:09 PM, Daeyoung Kim wrote: > I am a newbie to DPDK. Welcome! > I'm making a packet capture program from the l3fwd > sample application. When I tested my program in a virtual environment, = it > worked. But in a real world, it does not work correctly. This topology is kind of complicated. I recommend beginning with just a single port sending ARPs, pings, etc. = It takes a lot of careful work to get everything right. Switches are going to drop some packets from different ports depending = on the MAC addresses they learn from the traffic. So if there is a switch, when beginning it is good to enable a mirror = mode on two systems communicating, and sending the mirror to the DPDK = port that is listening. Or use some kind of cheap 100BaseT network tap = (Gigabit-plus active taps are very expensive, and not needed for simple = uses like this anyway, as you don't usually send heavy traffic when just = debugging). There is also a promiscuous flag in DPDK which you usually end up = needing to set if you are doing special-purpose stuff... rte_eth_promiscuous_enable(port_id) Good luck, happy hacking! Matthew.