DPDK usage discussions
 help / color / mirror / Atom feed
From: Nishant Verma <vnish11@gmail.com>
To: Raja Jayapal <raja.jayapal@tcs.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
	Nagaratna Patagar <nagaratna.patagar@tcs.com>
Subject: Re: [dpdk-users] arp behaviour on dpdk
Date: Fri, 12 Aug 2016 17:12:27 -0400	[thread overview]
Message-ID: <CAHhCjUFFVBfNNRJObCmCFxF7RQvo+1gxBMgs65WbTeUHzxARNQ@mail.gmail.com> (raw)
In-Reply-To: <OFB7BD4DAE.0037F717-ON6525800C.0025A3D8-6525800C.0026B8CA@tcs.com>

Hi Raja,

What i understand is that Br1(linux machine) is getting ARP request but not
sending ARP Response?
If this is the case, it means either packet is not liked by Br1 hence
dropped or some how capture is not right.

Can you share pcap file,  captured at Br1.



On Thu, Aug 11, 2016 at 3:02 AM, Raja Jayapal <raja.jayapal@tcs.com> wrote:

> Hi All,
>
> I am running dpdk on KVM and would like to understand the arp behaviour on
> dpdk ports.
> The topology is as below.
>
> br0(192.168.100.10)----> vnet0 -----> dpdk(NIC1-
> e1000)------->dpdk(NIC2-e1000)------>vnet1----->br1(192.168.100.20)
>
> I am sending ARP packet from br0 using PackETH tool destined to br1.
> I have  edited the dpdk l2fwd code in such a way that , the destination is
> broadcast address(ffff).
> In br1 , i can see the arp resquest, but the host bridge is not responding
> for the arp request.
>
> In br1:
> =====
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> 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
>
> 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.
>
> Could you please let me know how to make the host(br1) to reply the arp
> request.
>
> Thanks,
> Raja
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
>


-- 
Rgds,
Nishant

  reply	other threads:[~2016-08-12 21:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11  7:02 Raja Jayapal
2016-08-12 21:12 ` Nishant Verma [this message]
2016-08-16  6:40 ` Raja Jayapal
2016-08-16 16:18   ` Stephen Hemminger
2016-08-16 18:48     ` Nishant Verma

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHhCjUFFVBfNNRJObCmCFxF7RQvo+1gxBMgs65WbTeUHzxARNQ@mail.gmail.com \
    --to=vnish11@gmail.com \
    --cc=nagaratna.patagar@tcs.com \
    --cc=raja.jayapal@tcs.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).