From: "Chris Friesen" <cfriesen@nortel.com>
To: netdev@vger.kernel.org
Subject: dhcp/bonding interaction question
Date: Tue, 23 Sep 2008 09:24:32 -0600 [thread overview]
Message-ID: <48D90A30.8000701@nortel.com> (raw)
We've recently run into an interesting issue, and I was hoping to get
some suggestions.
We've got a boot server configured with two bonded links using the XOR
tx mode. Another board comes up. It's got two links which will
eventually be bonded. It issues a DHCP request to the server over one
of the links, which arrives on one of the bonded slaves. The server
sends a reply, but the XOR results in the packet being sent back via the
other slave. On the booting blade the xid in the packet doesn't match
the xid for the device on which the packet was received, so the packet
is dropped.
What's the proper solution here? Should dhcpd be forcing reply packets
out the slave on which the packet was received?
Chris
next reply other threads:[~2008-09-23 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 15:24 Chris Friesen [this message]
2008-09-23 16:42 ` dhcp/bonding interaction question Jay Vosburgh
2008-09-23 17:17 ` Chris Friesen
2008-09-23 18:17 ` Jay Vosburgh
2008-09-24 0:15 ` Chris Friesen
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=48D90A30.8000701@nortel.com \
--to=cfriesen@nortel.com \
--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;
as well as URLs for NNTP newsgroup(s).