From: Max Dmitrichenko <dmitrmax@gmail.com>
To: netfilter-devel@vger.kernel.org
Subject: ARP flux on bond interface
Date: Mon, 25 Aug 2014 12:47:23 +0400 [thread overview]
Message-ID: <CAMRqRqwzKEe4-L4Zxp8fciVQc_aN02uBuR9kSWmr3vQHc3xJBA@mail.gmail.com> (raw)
Hi!
There is a strange problem on the following setup.
There is two bond interfaces in the same IP-subnet (I know this is a
little bit weird). Let's say first has IP-address Ai and MAC-address
Am and the second Bi and Bm respectively.
Sometimes when interface B makes an ARP-request, the same request
appears on the interface A, but with source MAC-address of B, i.e. Bm.
This event poisons the ARP-table of the upstream switch and it sends
to A packets addressed to B which are dropped by my host system.
I've set arp_ignore=1 and tried to set arp_announce to 1 and 2, but
neither combination helps.
Is it kind of bug or it is expected behavior?
The kernel version is 2.6.32 from Scientific Linux 6.5 (i.e. it is
very close to one from RHEL 6).
--
Max
next reply other threads:[~2014-08-25 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 8:47 Max Dmitrichenko [this message]
2014-08-25 21:20 ` ARP flux on bond interface Paul Robert Marino
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=CAMRqRqwzKEe4-L4Zxp8fciVQc_aN02uBuR9kSWmr3vQHc3xJBA@mail.gmail.com \
--to=dmitrmax@gmail.com \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).