From: Dominik Kubla <kubla@sciobyte.de>
To: Michael Poole <poole@troilus.org>
Cc: Paul Jakma <paul@clubi.ie>, linux-kernel@vger.kernel.org
Subject: Re: Arp problem
Date: Tue, 24 Jul 2001 16:03:26 +0200 [thread overview]
Message-ID: <20010724160326.G31198@intern.kubla.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0107240208460.10839-100000@fogarty.jakma.org> <20010724140916.F31198@intern.kubla.de> <87k80y8qsz.fsf@cj46222-a.reston1.va.home.com>
In-Reply-To: <87k80y8qsz.fsf@cj46222-a.reston1.va.home.com>
On Tue, Jul 24, 2001 at 08:17:16AM -0400, Michael Poole wrote:
>
> This may be a stupid question, but does
> cat 0 > /proc/sys/net/ipv4/conf/eth0/send_redirects
> help the problem any (for the proper value of "eth0")? A college
> roommate of mine once had the same problem, and clearing
> send_redirects for the interface fixed it for him.
>
> -- Michael Poole
It may be a work-around, but it does not solve the problem.
There are legitimate uses of redirects and simply disabling them
might cause different problems. The correct solution is to have
the kernel treat aliased interfaces the same as interfaces on
different networking cards.
Dominik
--
ScioByte GmbH, Zum Schiersteiner Grund 2, 55127 Mainz (Germany)
Phone: +49 6131 550 117 Fax: +49 6131 610 99 16
GnuPG: 717F16BB / A384 F5F1 F566 5716 5485 27EF 3B00 C007 717F 16BB
next prev parent reply other threads:[~2001-07-24 14:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 19:46 Arp problem Sourav Sen
2001-07-23 20:13 ` Chris Friesen
2001-07-24 1:03 ` Ben Greear
2001-07-24 1:10 ` Paul Jakma
2001-07-24 1:19 ` Ben Greear
2001-07-24 1:29 ` Paul Jakma
2001-07-24 1:24 ` Matthew Dharm
2001-07-24 12:09 ` Dominik Kubla
2001-07-24 12:17 ` Michael Poole
2001-07-24 14:03 ` Dominik Kubla [this message]
2001-07-24 14:15 ` Paul Jakma
2001-07-24 14:20 ` Paul Jakma
2001-07-24 16:34 ` Alan Cox
2001-07-24 20:31 ` Paul Jakma
2001-07-24 23:11 ` Alan Cox
2001-07-25 10:40 ` Dominik Kubla
2001-07-26 6:54 ` Alexey Kuznetsov
2001-07-24 1:13 ` 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=20010724160326.G31198@intern.kubla.de \
--to=kubla@sciobyte.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@clubi.ie \
--cc=poole@troilus.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