From: Andi Kleen <ak@suse.de>
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: Andi Kleen <ak@suse.de>, Eric Weigle <ehw@lanl.gov>,
Sampsa Ranta <sampsa@netsonic.fi>,
linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
zebra@zebra.org
Subject: Re: ARP responses broken!
Date: Tue, 17 Apr 2001 17:01:10 +0200 [thread overview]
Message-ID: <20010417170110.A10430@gruyere.muc.suse.de> (raw)
In-Reply-To: <20010417161919.A8842@gruyere.muc.suse.de> <Pine.LNX.4.21.0104171652360.9099-100000@tux.rsn.bth.se>
In-Reply-To: <Pine.LNX.4.21.0104171652360.9099-100000@tux.rsn.bth.se>; from gandalf@wlug.westbo.se on Tue, Apr 17, 2001 at 04:53:01PM +0200
On Tue, Apr 17, 2001 at 04:53:01PM +0200, Martin Josefsson wrote:
> On Tue, 17 Apr 2001, Andi Kleen wrote:
>
> > On Mon, Apr 16, 2001 at 03:26:19PM -0600, Eric Weigle wrote:
> > > Hello-
> > >
> > > This is a known 'feature' of the Linux kernel, and can help with load sharing
> > > and fault tolerance. However, it can also cause problems (such as when one nic
> > > in a multi-nic machine fails and you don't know right away).
> > >
> > > There are three 'solutions' I know of:
> > >
> > > * In recent 2.2 kernels, it was possible to fix this by doing the following as
> >
> > Or use arpfilter in even newer 2.2 kernels; which filters based on the routing
> > table. "hidden" is quite a sledgehammer which often does more harm than good.
>
> Does arpfilter exist in 2.4 kernels?
Not yet, will be merged very soon. I can send you a patch if you need it urgently.
-Andi
next prev parent reply other threads:[~2001-04-17 15:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-16 21:26 Eric Weigle
2001-04-17 14:12 ` Broken ARP (was Re: ARP responses broken!) Sampsa Ranta
2001-04-17 15:21 ` Eric Weigle
2001-04-17 15:32 ` dean gaudet
2001-04-17 14:19 ` ARP responses broken! Andi Kleen
2001-04-17 14:53 ` Martin Josefsson
2001-04-17 15:01 ` Andi Kleen [this message]
2001-04-17 15:07 ` Martin Josefsson
2001-04-17 16:05 ` Alan Cox
2001-04-17 21:43 ` Rogier Wolff
-- strict thread matches above, loose matches on Subject: below --
2001-04-18 1:05 Julian Anastasov
2001-04-18 22:02 ` Sampsa Ranta
2001-04-19 1:46 ` Julian Anastasov
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
[not found] <4CDA8A6D03EFD411A1D300D0B7E83E8F6972AC@FSKNMD07.hickam.af.mil>
2001-04-17 13:56 ` Eric Weigle
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=20010417170110.A10430@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=ehw@lanl.gov \
--cc=gandalf@wlug.westbo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=sampsa@netsonic.fi \
--cc=zebra@zebra.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
all inboxes | Powered by JetHome®