From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: zhuyj <zyjzyj2000@gmail.com>,
netdev@vger.kernel.org, stefan.costandache@windriver.com,
alexandre.dietsch@windriver.com, yue.tao@windriver.com,
clinton.slabbert@windriver.com
Cc: eulfsam <ulf.samuelsson@ericsson.com>,
"David S. Miller" <davem@davemloft.net>,
WANG Cong <xiyou.wangcong@gmail.com>
Subject: Re: [PATCH 1/1] neighbour: Support broadcast ARP in neighbor PROPE state
Date: Thu, 05 Feb 2015 15:12:24 +0300 [thread overview]
Message-ID: <54D35E28.8010802@cogentembedded.com> (raw)
In-Reply-To: <1423120837-28102-1-git-send-email-zyjzyj2000@gmail.com>
Hello.
On 2/5/2015 10:20 AM, zhuyj wrote:
> From: eulfsam <ulf.samuelsson@ericsson.com>
> When the neighbor statemachine is in PROBE state, it will normally send
State machine.
> a number of unicast ARP requests (number defined in "ucast_probes" entry
> in the proc file system, default=3) and if no reply is received, it will
> change state to FAILED.
> Enabling CONFIG_ARP_PROBE_BCAST, will make the statemachine try to send
Likewise.
> broadcast ARP requests, and only enter FAILED state if the broadcast ARP
> requests did not receive a reply.
> Enabling CONFIG_ARP_PROBE_BCAST, makes the IPv4 ARP behaviour more
> similar to the IPv6 Neighbor Discovery protocol, and is neccessary,
Necessary.
> if the other end only responds to broadcast ARPs.
> CC: David S. Miller <davem@davemloft.net>
> CC: WANG Cong <xiyou.wangcong@gmail.com>
> Signed-off-by: eulfsam <ulf.samuelsson@ericsson.com>
> Signed-off-by: zhuyj <zyjzyj2000@gmail.com>
Need real names here.
[...]
> diff --git a/net/ipv4/Kconfig b/net/ipv4/Kconfig
> index bd29016..4d13edb 100644
> --- a/net/ipv4/Kconfig
> +++ b/net/ipv4/Kconfig
> @@ -259,6 +259,23 @@ config IP_PIMSM_V2
> gated-5). This routing protocol is not used widely, so say N unless
> you want to play with it.
>
> +config ARP_PROBE_BCAST
> + bool "IP: ARP send broadcast ARP, if probing using unicast fails"
> + default y
> + ---help---
> + When the neighbor statemachine is in PROBE state, it will
State machine.
> + normally send a number of unicast ARP requests
> + (number defined in "ucast_probes" entry in the proc file system, default=3)
> + and if no reply is received, it will change state to FAILED.
> +
> + Saying Y here, will make the statemachine try to send broadcast ARP
Likewise.
> + requests, and only enter FAILED state if the broadcast ARP requests did not
> + receive a reply.
> +
> + Enabling this, makes the IPv4 ARP behaviour more similar to the IPv6
> + Neighbor Discovery protocol, and is neccessary, if the other end
Necessary.
[...]
WBR, Sergei
next prev parent reply other threads:[~2015-02-05 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 7:20 [PATCH 1/1] neighbour: Support broadcast ARP in neighbor PROPE state zhuyj
2015-02-05 12:12 ` Sergei Shtylyov [this message]
2015-02-07 6:46 ` Cong Wang
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=54D35E28.8010802@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=alexandre.dietsch@windriver.com \
--cc=clinton.slabbert@windriver.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=stefan.costandache@windriver.com \
--cc=ulf.samuelsson@ericsson.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yue.tao@windriver.com \
--cc=zyjzyj2000@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).