From: Stephen Hemminger <stephen@networkplumber.org>
To: Raja Jayapal <raja.jayapal@tcs.com>
Cc: Nishant Verma <vnish11@gmail.com>,
"users@dpdk.org" <users@dpdk.org>,
Nagaratna Patagar <nagaratna.patagar@tcs.com>
Subject: Re: [dpdk-users] arp behaviour on dpdk
Date: Tue, 16 Aug 2016 09:18:41 -0700 [thread overview]
Message-ID: <20160816091841.1e649dee@xeon-e3> (raw)
In-Reply-To: <OFE50302C9.4FDCC38B-ON65258011.0024B27E-65258011.0024B29E@tcs.com>
On Tue, 16 Aug 2016 12:10:50 +0530
Raja Jayapal <raja.jayapal@tcs.com> wrote:
> Hi Nishant,
>
> Please find attachment for the pcap file.
>
> Thanks,
> Raja
>
> -----Nishant Verma <vnish11@gmail.com> wrote: -----
> To: Raja Jayapal <raja.jayapal@tcs.com>
> From: Nishant Verma <vnish11@gmail.com>
> Date: 08/13/2016 02:42AM
> Cc: "users@dpdk.org" <users@dpdk.org>, Nagaratna Patagar <nagaratna.patagar@tcs.com>
> Subject: Re: [dpdk-users] arp behaviour on dpdk
>
> 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.
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 custom
kernel and instrument kernel with printk's there.
next prev parent reply other threads:[~2016-08-16 16:18 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
2016-08-16 6:40 ` Raja Jayapal
2016-08-16 16:18 ` Stephen Hemminger [this message]
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=20160816091841.1e649dee@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=nagaratna.patagar@tcs.com \
--cc=raja.jayapal@tcs.com \
--cc=users@dpdk.org \
--cc=vnish11@gmail.com \
/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).