netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Yanjun <Yanjun.Zhu@windriver.com>
To: <brian.haley@hp.com>, <davem@davemloft.net>,
	<alexandre.dietsch@windriver.com>,
	<clinton.slabbert@windriver.com>, <kuznet@ms2.inr.ac.ru>,
	<jmorris@namei.org>, <kaber@trash.net>, <netdev@vger.kernel.org>,
	<ulf.samuelsson@ericsson.com>
Subject: [PATCH V2 0/1] neighbour: Support broadcast ARP in neighbor PROPE state
Date: Thu, 12 Mar 2015 14:58:20 +0800	[thread overview]
Message-ID: <1426143501-30827-1-git-send-email-Yanjun.Zhu@windriver.com> (raw)

V2:
  set ARP_PROBE_BCAST default N.

V1:
  Have a problem with an HP router at a certain location, which
  is configured to only answer to broadcast ARP requests.
  That cannot be changed.

  The first ARP request the kernel sends out, is a broadcast request,
  which is fine, but after the reply, the kernel sends unicast requests,
  which will not get any replies.

  The ARP entry will after some time enter STALE state,
  and if nothing is done it will time out, and be removed.
  This process takes to long, and I have been told that it is
  difficult to makes changes that will eventually remove it.

  Have tried to change the state from STALE to INCOMPLETE, which failed,
  and then tried to change the state to PROBE which also failed.

  The stack is only sending out unicasts, and never broadcast.
  Is there any way to get the stack to send out a broadcast ARP
  without having to wait for the entry to be removed?

  I think the recommended behaviour in IPv6 is to send out 3 unicasts
  and if all fails, to send out broadcasts.

Zhu Yanjun (1):
  neighbour: Support broadcast ARP in neighbor PROPE state

 include/net/neighbour.h        |  7 ++++++
 include/uapi/linux/neighbour.h |  6 +++++
 include/uapi/linux/sysctl.h    |  3 +++
 kernel/sysctl_binary.c         |  3 +++
 net/core/neighbour.c           | 44 +++++++++++++++++++++++++++++---
 net/ipv4/Kconfig               | 57 ++++++++++++++++++++++++++++++++++++++++++
 net/ipv4/arp.c                 |  7 ++++--
 7 files changed, 121 insertions(+), 6 deletions(-)

-- 
1.9.1

             reply	other threads:[~2015-03-12  6:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12  6:58 Zhu Yanjun [this message]
2015-03-12  6:58 ` [PATCH V2 1/1] neighbour: Support broadcast ARP in neighbor PROPE state Zhu Yanjun
2015-03-12 10:05   ` YOSHIFUJI Hideaki/吉藤英明
2015-03-12  7:10 ` [PATCH V2 0/1] " yzhu1
2015-03-12  8:42   ` YOSHIFUJI Hideaki
2015-03-12  8:59     ` Ulf samuelsson
2015-03-12  9:28       ` YOSHIFUJI Hideaki/吉藤英明
2015-03-12  9:45         ` Ulf samuelsson
2015-03-12 10:16           ` YOSHIFUJI Hideaki
2015-03-18  8:51     ` Ulf Samuelsson
2015-03-18 10:34       ` YOSHIFUJI Hideaki/吉藤英明
2015-03-18 12:15         ` Ulf Samuelsson
2015-03-18 13:22           ` YOSHIFUJI Hideaki/吉藤英明
2015-03-18 15:12             ` Ulf Samuelsson
2015-03-19  2:42             ` yzhu1
2015-03-19  2:14           ` yzhu1
2015-03-19  2:24       ` yzhu1
2015-03-12 19:22 ` David Miller
2015-03-16 12:39   ` Ulf Samuelsson
2015-03-19  5:52     ` yzhu1

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=1426143501-30827-1-git-send-email-Yanjun.Zhu@windriver.com \
    --to=yanjun.zhu@windriver.com \
    --cc=alexandre.dietsch@windriver.com \
    --cc=brian.haley@hp.com \
    --cc=clinton.slabbert@windriver.com \
    --cc=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@vger.kernel.org \
    --cc=ulf.samuelsson@ericsson.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).