From: Bernd Eckenfels <inka-user@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Turning off ARP in linux-2.4.0
Date: Wed, 24 Jan 2001 09:32:13 +0100 [thread overview]
Message-ID: <E14LLLh-0004Il-00@sites.inka.de> (raw)
In article <Pine.LNX.4.30.0101240857420.1024-100000@u.domain.uli> you wrote:
> The problem is complex and can't be solved with ifconfig -arp
why?
> The needs for clusters with shared addresses include:
> 1. block ARP replies for such addresses
-arp will do that
> 2. don't announce these addresses in the ARP probes (can be achieved
> using ip addr add IP brd + dev lo scope host)
i guess -arp will disable neighbour alive probes, too?
> 3. don't autoselect such addresses (for source addresses)
This is not done if you do not use a route through that ip
So where is the problem with -arp?
Well.. another solution would be to use the ipip system instead of the arp
redirection, right?
Greetings
Bernd
-
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/
next reply other threads:[~2001-01-24 8:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 8:32 Bernd Eckenfels [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-25 11:02 Turning off ARP in linux-2.4.0 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 4:07 Bernd Eckenfels
2001-01-24 4:02 Bernd Eckenfels
2001-01-23 13:19 NDias
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
2001-01-24 0:27 ` Pete Elton
2001-01-24 0:38 ` Andi Kleen
2001-01-24 0:49 ` Pete Elton
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=E14LLLh-0004Il-00@sites.inka.de \
--to=inka-user@lina.inka.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