From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-f171.google.com (mail-qc0-f171.google.com [209.85.216.171]) by dpdk.org (Postfix) with ESMTP id 079FE2F4 for ; Thu, 23 Jan 2014 09:44:13 +0100 (CET) Received: by mail-qc0-f171.google.com with SMTP id n7so2094650qcx.30 for ; Thu, 23 Jan 2014 00:45:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=bq3zxqWcxwEA6tS506eOBejqc1QXsAZ2UDFA/vKqFWI=; b=PkKrUJfihMXgxnYD+KbBCosgDPQObOlAaXMK+XF4jIg/2GXO2NvPLErLQsX/y/emat EtoYWpQq7AUp5+l3H6Qvey2j6Pk4XxmB59br45eANrbJkdbBCJfMt9dxwnQRWd7H4x4K MdSuQz/OsiPzws+V+iG15/IlUGhKtVMUyLrKuq6nTr4H8DGJ25kgj7EbaW4facRFtazM TIZSGcw67wvTt1AvAGd3WdIOBXoHwnVQ5BJsXvoI+7/zX9ZjM3pc42nhZmr5+3+rWt9e WvWnF+RYaaGWsH9zVHEfpeby0Nri6Ila1ZtmnJcexmgP+UbMA6TNoUk8yGB4zpjlGWYq otHg== X-Gm-Message-State: ALoCoQk7g/5zs/Q3NaXEVXu/yJ2I0X9IzfDdrcOIZtzTPrvm0sgQjrRJNWSFxD93PtDKI9iZYa/9 MIME-Version: 1.0 X-Received: by 10.224.14.129 with SMTP id g1mr9798589qaa.42.1390466730654; Thu, 23 Jan 2014 00:45:30 -0800 (PST) Received: by 10.140.28.162 with HTTP; Thu, 23 Jan 2014 00:45:30 -0800 (PST) X-Originating-IP: [109.64.22.48] In-Reply-To: References: Date: Thu, 23 Jan 2014 10:45:30 +0200 Message-ID: From: Daniel Kaminsky To: James Yu Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Passing VLAN traffic via l2fwd 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: Thu, 23 Jan 2014 08:44:14 -0000 Hi James, Did you try a non-tagged traffic? I suspect this is the limitation of the l2fwd or the requirements of Spirent. From my experience with Ixia, the L2 forward device must implement the ARP protocol (at least a subset of it). Also, notice that the l2fwd example sets the destination MAC address to "02:00:00:00:00:xx" which the Spirent might doesn't like. Daniel On Thu, Jan 23, 2014 at 7:08 AM, James Yu wrote: > I could not pass tagged traffic through the l2fwd program running inside a > CentOS VM. The l2fwd program reported sending out all the packets received > from one port to the other port. But the outside Spirent tester could not > receive a packet at all. I am wondering maybe the tagged packets are > dropped somewhere in the rte_em_pmd or in the DPDK library. Anyone knows > how to pass/send VLAN traffic through the DPDK ? > > With tagged SR-IOV ports, Spirent and guest VM CentOS could ping each other > without using DPDK. Once I used DPDK 1.3.1r2, I encountered issues with > sending out tagged packets out of DPDK to the host. > > I have done the following: > > On RHEL6.1 host > 1. setup the VLAN using "ip link set eth2 vf 0 vlan 3" for port 1 and "ip > link set eth3 vf 0 vlan 3" for port 2 > [root@cent64x64-137189 ~]# ip link show eth2 > 96: eth2: mtu 1500 qdisc mq state UP qlen > 1000 > link/ether 90:e2:ba:2e:af:f0 brd ff:ff:ff:ff:ff:ff > vf 0 MAC 52:54:00:f9:9a:90, vlan 3 > [root@cent64x64-137189 ~]# ip link show eth3 > 98: eth3: mtu 1500 qdisc mq state UP qlen > 1000 > link/ether 90:e2:ba:2e:af:f1 brd ff:ff:ff:ff:ff:ff > vf 0 MAC 52:54:00:30:37:98, vlan 3 > > 2. virsh configure SR-IOV hostdev > > > >
function='0x0'/> > >
function='0x0'/> > > > > >
function='0x1'/> > >
function='0x0'/> > > > [root@cent64x64-137189 ~]# lspci |grep Eth > 1a:00.0 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ > Network Connection (rev 01) > 1a:00.1 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ > Network Connection (rev 01) > 1a:10.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller > Virtual Function (rev 01) > 1a:10.1 Ethernet controller: Intel Corporation 82599 Ethernet Controller > Virtual Function (rev 01) > > > On guest VM > 1. check all the ports are started up and check their corresponding port > type. Use the two SR-IOV ports with device type as ixgbevf for l2fwd > [root@VirtualADX ~]# lspci |grep Eth > 00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet > Controller (rev 03) > 00:07.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet > Controller (rev 03) > 00:08.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller > Virtual Function (rev 01) > 00:09.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller > Virtual Function (rev 01) > 00:0a.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet > Controller (rev 03) > > 2. run this command: > /root/l2fwd -c 3 -n 1 -b 000:00:03.0 -b 000:00:07.0 -b > 000:00:0a.0 -- -q 1 -p 3 > > Although the l2fwd forwards all received tagged packets, the Spirent > tester did not receive any packet at all. >