From: Bernd Eckenfels <ecki@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: ARP responses broken!
Date: Tue, 17 Apr 2001 16:31:11 +0200 [thread overview]
Message-ID: <20010417163111.A20874@lina.inka.de> (raw)
In-Reply-To: <E14pWQ2-0005LM-00@calista.inka.de>
In-Reply-To: <E14pWQ2-0005LM-00@calista.inka.de>; from Mailer-Daemon@lina.inka.de on Tue, Apr 17, 2001 at 04:25:26PM +0200
> but why would you want it to reply for the IP of the other interface even if
> it was NOT on the same subnet?
Because Linux is always answering to all its local IP addresses, regardless
of the Network interface. Even if you tun off the IP Forwarding.
This is by Designs, there are situation where this is good and there are
situations where it is not so good. But it's an old tradition.
Greetings
Bernd
--
(OO) -- Bernd_Eckenfels@Wendelinusstrasse39.76646Bruchsal.de --
( .. ) ecki@{inka.de,linux.de,debian.org} http://home.pages.de/~eckes/
o--o *plush* 2048/93600EFD eckes@irc +497257930613 BE5-RIPE
(O____O) When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!
next parent reply other threads:[~2001-04-17 14:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E14pWQ2-0005LM-00@calista.inka.de>
2001-04-17 14:31 ` Bernd Eckenfels [this message]
2001-04-18 1:05 Julian Anastasov
2001-04-18 22:02 ` Sampsa Ranta
2001-04-19 1:46 ` Julian Anastasov
-- strict thread matches above, loose matches on Subject: below --
2001-04-17 18:25 Sam.Bingner
2001-04-17 18:07 Bingner Sam J. Contractor RSIS
[not found] <4CDA8A6D03EFD411A1D300D0B7E83E8F6972AC@FSKNMD07.hickam.af.mil>
2001-04-17 13:56 ` Eric Weigle
2001-04-16 21:26 Eric Weigle
2001-04-17 14:19 ` Andi Kleen
2001-04-17 14:53 ` Martin Josefsson
2001-04-17 15:01 ` Andi Kleen
2001-04-17 15:07 ` Martin Josefsson
2001-04-17 16:05 ` Alan Cox
2001-04-17 21:43 ` Rogier Wolff
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=20010417163111.A20874@lina.inka.de \
--to=ecki@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
all inboxes | Powered by JetHome®