From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) by dpdk.org (Postfix) with ESMTP id 983E5568A for ; Tue, 16 Aug 2016 18:18:30 +0200 (CEST) Received: by mail-pa0-f46.google.com with SMTP id ti13so27787624pac.0 for ; Tue, 16 Aug 2016 09:18:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=VhnOdMOkeEXrSd+HSncJQ95c5sPxvSahCHGBp002RD0=; b=X7mN9Qe2Ju+Z5Va3Ua3e4g+xa3/Ci2g+PkH14R9REyHRiciYCqlF9pWt0fwEV5X/nR Y28DwB7ieHERPiym53KbG33uItEcgjdXaU1T1EuOZhIIgco4olEdlufKVD4ogw0vG2Va jTsI1d61dSLKsbvtPizWvJ9GXV+g8LJftNX8jPa8qG/Zp2gf3q6Wo+oyRZtEATim+sTo Oi8R29UgCWmM7M5vWJKGjfSrMsrBuenfNKUYIyRE+yTrKSIjlCbiXC9Cn7Mj6Vlu9cQz 42qmWtMif5vG+Yag8r4rwSg588HnvAoxyfu3XP71C7xE4TU8WPJBLENAzCSf1FB28UdT bh7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=VhnOdMOkeEXrSd+HSncJQ95c5sPxvSahCHGBp002RD0=; b=ThDm9fP8NblHAsY5BCpRNLO4lx5lYMG+oUdCes/EBl3wI6qh5hUuGZFiLFdwoRCVHJ kgvTkUSPKSSLIki4+k8sstJs4ZrqngAw0hWA9OabX+OHCIJfnRcsTXW0NG6/pJb7kPUW 7kFuReATix/nTYdYGC7puF1ouAzyN99tD1WLXavk5Tk3Ix3feCSnPx7L+/81DYfFm1im ETETMx7EJwnwpMyZ2l5Ni6bnxMTobqhaApBWIsxHQgfAeIuO2fIcFifVAe+QEpbOQTV0 psY98sXoSQiPRJNv0W0KfMN0gr4sS6o7Gb6EX9PFEgNJLOIJkWHcJ3sK7H/yTQ4jzbeu Jw+w== X-Gm-Message-State: AEkoouvSq+XS1Za2ec8iWyiNNJORXNNIL7do8qx6LxLtnIZkPMoH58tNALdj+NrQ670pTQ== X-Received: by 10.66.100.230 with SMTP id fb6mr2796413pab.107.1471364309942; Tue, 16 Aug 2016 09:18:29 -0700 (PDT) Received: from xeon-e3 (static-50-53-69-251.bvtn.or.frontiernet.net. [50.53.69.251]) by smtp.gmail.com with ESMTPSA id bx9sm40608518pab.17.2016.08.16.09.18.29 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 16 Aug 2016 09:18:29 -0700 (PDT) Date: Tue, 16 Aug 2016 09:18:41 -0700 From: Stephen Hemminger To: Raja Jayapal Cc: Nishant Verma , "users@dpdk.org" , Nagaratna Patagar Message-ID: <20160816091841.1e649dee@xeon-e3> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-users] arp behaviour on dpdk 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, 16 Aug 2016 16:18:30 -0000 On Tue, 16 Aug 2016 12:10:50 +0530 Raja Jayapal wrote: > Hi Nishant, >=20 > Please find attachment for the pcap file. >=20 > Thanks, > Raja >=20 > -----Nishant Verma wrote: ----- > To: Raja Jayapal > From: Nishant Verma > Date: 08/13/2016 02:42AM > Cc: "users@dpdk.org" , Nagaratna Patagar > Subject: Re: [dpdk-users] arp behaviour on dpdk >=20 > Hi Raja, >=20 > What i understand is that Br1(linux machine) is getting ARP request but n= ot sending ARP Response?=20 > If this is the case, it means either packet is not liked by Br1 hence dro= pped or some how capture is not right. >=20 > Can you share pcap file,=C2=A0 captured at Br1. >=20 >=20 >=20 > On Thu, Aug 11, 2016 at 3:02 AM, Raja Jayapal wrot= e: > Hi All, > =20 > I am running dpdk on KVM and would like to understand the arp behaviour = on dpdk ports. > The topology is as below. > =20 > br0(192.168.100.10)----> vnet0 -----> dpdk(NIC1- e1000)------->dpdk(NIC2= -e1000)------>vnet1----->br1(192.168.100.20) > =20 > I am sending ARP packet from br0 using PackETH tool destined to br1. > I have=C2=A0 edited the dpdk l2fwd code in such a way that , the destina= tion is broadcast address(ffff). > In br1 , i can see the arp resquest, but the host bridge is not respondi= ng for the arp request. > =20 > In br1: > =3D=3D=3D=3D=3D > tcpdump: verbose output suppressed, use -v or -vv for full protocol deco= de > listening on br1, link-type EN10MB (Ethernet), capture size 65535 bytes > 12:21:15.459667 ARP, Request who-has 192.168.100.20 (00:0a:e7:2c:44:2b (= oui Unknown)) tell 192.168.100.10, length 46 > 12:21:15.651610 ARP, Request who-has 192.168.100.20 (00:0a:e7:2c:44:2b (= oui Unknown)) tell 192.168.100.10, length 46 > 12:21:15.867692 ARP, Request who-has 192.168.100.20 (00:0a:e7:2c:44:2b (= oui Unknown)) tell 192.168.100.10, length 46 > =20 > In l2fwd application example also, the arp packets are getting received = on the adjacent ports, but the arp reply has not been sent back from br1. > =20 > Could you please let me know how to make the host(br1) to reply the arp = request. The host kernel has a number of checks to prevent ARP spoofing. Most likely your packet is invalid by one of these checks. Linux ARP does not keep many statistics, so that doesn't help. Look at the arp_ignore sysctl flag and read kernel source for net/ipv4/arp.= c function arp_process to see what is going on. If you are completely stuck build a cu= stom kernel and instrument kernel with printk's there.