mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Pete Elton <elton@iqs.net>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>,
	"A.N.Kuznetsov" <kuznet@ms2.inr.ac.ru>
Subject: Re: Turning off ARP in linux-2.4.0
Date: Wed, 24 Jan 2001 01:10:11 +0100	[thread overview]
Message-ID: <20010124011011.A12252@gruyere.muc.suse.de> (raw)
In-Reply-To: <20010123100803.A24145@gruyere.muc.suse.de> <200101232350.PAA14448@tech1.nameservers.com>
In-Reply-To: <200101232350.PAA14448@tech1.nameservers.com>; from elton@iqs.net on Tue, Jan 23, 2001 at 03:50:36PM -0800

On Tue, Jan 23, 2001 at 03:50:36PM -0800, Pete Elton wrote:
> Is there something that the arp_filter can do that will mirror this
> functionality?  The modification that you made to the documentation 
> was pretty straight forward in that the arp_filter was BOOLEAN, so 
> I think I implemented it right.

The snippet you posted doesn't describe what ClusterThingy exactly wants
to do with ARPs. 

Arpfilter was designed for multiple interfaces, to direct ARP replies
to specific interfaces based on the routing table. If you have only a 
single interface and no other way to policy route the packet I think you can 
only try to use policy routing hacks (not tested). e.g. tag all outgoing 
packets with a specific fwmark that redirects them to a specific routing
table which does the real routing, and put no routes into the normal 
one used by arpfilter so that it doesnt' reply.

Admittedly it's quite a hack. Perhaps Alexey can suggest a better solution,
he's the routing/arp guru. I guess it would be easier if arpfilter was
able to select a special own routing table, but I was too chicken to implement
that.


-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-24  0:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-23  0:50 Bernd Eckenfels
2001-01-23  9:08 ` Andi Kleen
2001-01-23 23:50   ` Pete Elton
2001-01-24  0:10     ` Andi Kleen [this message]
2001-01-24  0:27       ` Pete Elton
2001-01-24  0:38         ` Andi Kleen
2001-01-24  0:49           ` Pete Elton
  -- strict thread matches above, loose matches on Subject: below --
2001-01-25 11:02 Julian Anastasov
2001-01-25 17:08 ` Bernd Eckenfels
2001-01-25 23:13   ` Julian Anastasov
2001-01-25  0:19 Julian Anastasov
2001-01-25  0:08 Bernd Eckenfels
2001-01-24  9:21 Julian Anastasov
2001-01-25  0:30 ` Pete Elton
2001-01-24  8:32 Bernd Eckenfels
2001-01-24  4:07 Bernd Eckenfels
2001-01-24  4:02 Bernd Eckenfels
2001-01-23 13:19 NDias
2001-01-22 20:59 Pete Elton

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=20010124011011.A12252@gruyere.muc.suse.de \
    --to=ak@suse.de \
    --cc=elton@iqs.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --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

all inboxes | Powered by JetHome®