From: Joe Perches <joe@perches.com>
To: Veaceslav Falico <vfalico@redhat.com>
Cc: netdev@vger.kernel.org,
"François CACHEREUL" <f.cachereul@alphalink.fr>,
"Zhenjie Chen" <zhchen@redhat.com>,
"Jay Vosburgh" <fubar@us.ibm.com>,
"Andy Gospodarek" <andy@greyhouse.net>
Subject: Re: [PATCH net-next] bonding: send arp requests even if there's no route to them
Date: Fri, 28 Feb 2014 03:12:51 -0800 [thread overview]
Message-ID: <1393585971.10280.5.camel@joe-AO722> (raw)
In-Reply-To: <1393585076-22786-1-git-send-email-vfalico@redhat.com>
On Fri, 2014-02-28 at 11:57 +0100, Veaceslav Falico wrote:
> Currently we're only sending arp requests if we have a route to the target
> (and, thus, can find out the source ip address).
>
> There are some use cases, however, where we don't want/need to set an ip
> address (or set up a specific route) for bonding to use arp monitoring *for
> traffic generation*. We can easily send arp probes (arp requests with src
> ip == 0) to generate arp broadcast responses from the target ip and use
> them for determining if the target is up.
>
> This, obviously, won't work with arp validation - because we don't have the
> ip address set and, thus, will filter out the responses. So in that case -
> print a warning.
[]
> diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
[]
> @@ -2155,8 +2155,13 @@ static void bond_arp_send_all(struct bonding *bond, struct slave *slave)
[]
> + if (bond->params.arp_validate)
> + pr_warn("%s: no route to arp_ip_target %pI4 and arp_validate is set\n",
> + bond->dev->name, &targets[i]);
Maybe
if (bond->params.arp_validate && net_ratelimit())
next prev parent reply other threads:[~2014-02-28 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 10:57 [PATCH net-next] bonding: send arp requests even if there's no route to them Veaceslav Falico
2014-02-28 11:12 ` Joe Perches [this message]
2014-02-28 11:28 ` Veaceslav Falico
2014-02-28 11:38 ` Joe Perches
2014-02-28 11:40 ` Veaceslav Falico
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=1393585971.10280.5.camel@joe-AO722 \
--to=joe@perches.com \
--cc=andy@greyhouse.net \
--cc=f.cachereul@alphalink.fr \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=vfalico@redhat.com \
--cc=zhchen@redhat.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