public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Elton <elton@iqs.net>
To: linux-kernel@vger.kernel.org
Cc: Andi Kleen <ak@suse.de>
Subject: Re: Turning off ARP in linux-2.4.0
Date: Tue, 23 Jan 2001 16:49:04 -0800	[thread overview]
Message-ID: <200101240049.QAA14815@tech1.nameservers.com> (raw)
In-Reply-To: Your message of "Wed, 24 Jan 2001 01:38:00 +0100." <20010124013800.A12632@gruyere.muc.suse.de>

> On Tue, Jan 23, 2001 at 04:27:21PM -0800, Pete Elton wrote:
> > Any ideas on how I can turn off the arping?  I guess the thing that I 
> 
> I explained it in my last mail how to do it using arpfilter. I do not claim 
> that it is an elegant solution.
> It's probably not worse a hack than hidden is in the first place though.

I either missed that or did not understand it.  I am now rereading your
message....

Is that what you were referring to when you said
	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.

I am not familiar with policy routing.  Could you point me to some
docs I could read or maybe even give a trivial example to start me
on the right path?

> > am most curious about is how it ending up being removed from the kernel
> > in the first place.  It must have been a decision that someone made.
> > Either, we don't need that any more since we can do it this way, or
> > we'll take it out since nobody uses it.
> 
> It was only submitted to 2.2 a few months ago (=years after 2.3 branched), b
>     ut 
> never added to 2.4. 

Well that at least makes sense as to why it's not in there.

Thank you for all of your help.

Pete

-
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:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-23  0:50 Turning off ARP in linux-2.4.0 Bernd Eckenfels
2001-01-23  9:08 ` Andi Kleen
2001-01-23 23:50   ` Pete Elton
2001-01-24  0:10     ` Andi Kleen
2001-01-24  0:27       ` Pete Elton
2001-01-24  0:38         ` Andi Kleen
2001-01-24  0:49           ` Pete Elton [this message]
  -- 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=200101240049.QAA14815@tech1.nameservers.com \
    --to=elton@iqs.net \
    --cc=ak@suse.de \
    --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