From: Eric Weigle <ehw@lanl.gov>
To: "Bingner Sam J. Contractor RSIS" <Sam.Bingner@hickam.af.mil>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: ARP responses broken!
Date: Tue, 17 Apr 2001 07:56:01 -0600 [thread overview]
Message-ID: <3ADC4B71.2FE60B57@lanl.gov> (raw)
In-Reply-To: <4CDA8A6D03EFD411A1D300D0B7E83E8F6972AC@FSKNMD07.hickam.af.mil>
> oh great, now I wont be able to upgrade our kernels to 2.4 unless I find a
> utility to filter out the ARP requests?
"There's more than one way to do it" (see below)
> Why was this ability removed?
Apparently the decision was made to do it this way because it simplified the
fast path of the code; but I could be wrong. I have yet to achieve Linux Guru
status, right now I'm just some guy who has hit this problem and knows the
work-arounds.
> If I screw up and put it on the wrong card, I WANT the system to stop
> working...
I agree. I'm not making an argument for this implementation. Well, maybe I am;
Linux is intended as a desktop operating system and in that context most people
would rather have the failsafe than the failstop. Perhaps this method is
`inelegant' but it kept up a cluster of machines we have here a lot longer than
they might otherwise have functioned (the gige Acenic driver had some problems a
while back and about half the cards silently failed-- the 'broken' arp responses
meant that we could still talk to those boxes without reconfiguring IPs).
Anyway, Here's links to a discussion that occurred this January.
If you require the 'hidden' functionality, the first message cites the following
links; the patch apparently works with 2.4.x with some tweaking.
http://www.linuxvirtualserver.org/arp.html
http://www.linuxvirtualserver.org/hidden-2.3.41-1.diff
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0101.3/0014.html
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0101.3/0020.html
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0101.3/0188.html
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0101.3/0213.html
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0101.3/0220.html
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0101.3/0268.html
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0101.3/0334.html
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0101.3/0410.html
Hope that helps
-Eric
--------------------------------------------
Eric H. Weigle CCS-1, RADIANT team
ehw@lanl.gov Los Alamos National Lab
(505) 665-4937 http://home.lanl.gov/ehw/
--------------------------------------------
next parent reply other threads:[~2001-04-17 13:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4CDA8A6D03EFD411A1D300D0B7E83E8F6972AC@FSKNMD07.hickam.af.mil>
2001-04-17 13:56 ` Eric Weigle [this message]
2001-04-18 1:05 ARP responses broken! Julian Anastasov
2001-04-18 22:02 ` Sampsa Ranta
2001-04-19 1:46 ` Julian Anastasov
-- strict thread matches above, loose matches on Subject: below --
2001-04-17 18:25 Sam.Bingner
2001-04-17 18:07 Bingner Sam J. Contractor RSIS
[not found] <E14pWQ2-0005LM-00@calista.inka.de>
2001-04-17 14:31 ` Bernd Eckenfels
2001-04-16 21:26 Eric Weigle
2001-04-17 14:19 ` Andi Kleen
2001-04-17 14:53 ` Martin Josefsson
2001-04-17 15:01 ` Andi Kleen
2001-04-17 15:07 ` Martin Josefsson
2001-04-17 16:05 ` Alan Cox
2001-04-17 21:43 ` Rogier Wolff
2001-04-16 20:49 Sampsa Ranta
2001-04-16 22:47 ` Bernd Eckenfels
2001-04-17 14:24 ` Christopher 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=3ADC4B71.2FE60B57@lanl.gov \
--to=ehw@lanl.gov \
--cc=Sam.Bingner@hickam.af.mil \
--cc=linux-kernel@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