From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 99191] New: ARP monitoring with bonding module uses interface alias for ARP request
Date: Wed, 10 Jun 2015 17:41:21 -0700 [thread overview]
Message-ID: <20150610174121.39f9d19d@urahara> (raw)
Begin forwarded message:
Date: Fri, 29 May 2015 17:59:33 +0000
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "shemminger@linux-foundation.org" <shemminger@linux-foundation.org>
Subject: [Bug 99191] New: ARP monitoring with bonding module uses interface alias for ARP request
https://bugzilla.kernel.org/show_bug.cgi?id=99191
Bug ID: 99191
Summary: ARP monitoring with bonding module uses interface
alias for ARP request
Product: Networking
Version: 2.5
Kernel Version: All
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: shemminger@linux-foundation.org
Reporter: lessani@gmail.com
Regression: No
When using arp_ip_target combined with arp_validate to verify the connectivity
status of a bond, the wrong IP address is used as the source of the request if
multiple IP aliases are assigned to the bond0.
Example 1.
bond0 - 10.0.0.5/24 (WAN)
bond0:1 - 10.0.1.5/24 (LAN)
arp_validate - all
arp_ip_target - 10.0.0.1
Expected result: ARP, Request who-has 10.0.0.1 tell 10.0.0.5
Actual result: ARP, Request who-has 10.0.0.1 tell 10.0.1.5
Issue: The Layer 3 switch responsible for replying to the ARP request
does not have the local interface of 10.0.1.5 configured, so the ARP request
goes unanswered.
-
My expectation is that the bonding driver would use the primary IP on the bond0
interface, not a secondary IP. The solution being to be able to specify which
IP the ARP should originate from in a scenario where bondX has multiple IPs
assigned.
Mangling the packet in/out using arptables does not achieve the desired effect.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2015-06-11 0:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150610174121.39f9d19d@urahara \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.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