From: Harley Stenzel <hstenzel@nc.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: BUG: 2 NICs on same network
Date: Tue, 23 Apr 2002 09:58:27 -0400 [thread overview]
Message-ID: <3CC56883.9020506@nc.rr.com> (raw)
In-Reply-To: <20020423113935.A30329@openminds.be>
Frank Louwers wrote:
> Hi,
>
> We recently stummed across a rather annoying bug when 2 nics are on
> the same network.
>
> Our situation is this: we have a server with 2 nics, each with a
> different IP on the same network, connected to the same switch. Let's
> assume eth0 has ip 1.2.3.1 and eth1 has 1.2.3.2, with a both with a
> netmask of 255.255.255.0.
. . .
>
> Is this a bug or a known issue? If it is not a bug, how can it be
> solved?
It is a known issue with 2.4 Linux kernels and ARP. Linux will respond
to arp requests for any address configured on the box on any interface
that receives the arp request. Patches have been proposed in the past,
but the maintainers have elected to not accept the patches on the basis
that the current behavior is RFC-compliant. The behavior you describe
is also RFC-compliant, and is in fact what the other OSes that I'm
familiar with do.
In your situation, where you have a single nic that you want to use as
backup only, you could set noarp on the backup nic. Then, when you want
to talk to the machine on the backup nic, you could use a static arp
entry specifying the MAC address of the backup and any IP address on the
box.
Alternatively, you could put the NICs on different physical segments or
you could dig up the proposed patches (2.4.0,2,and 12 if I remember
correctly) and port them forward and apply them.
>
> Kind Regards,
> Frank Louwers
>
--Harley Stenzel
hstenzel@nc.rr.com
next prev parent reply other threads:[~2002-04-23 13:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 9:39 BUG: 2 NICs on same network Frank Louwers
2002-04-23 10:53 ` rpm
2002-04-23 10:52 ` Frank Louwers
2002-04-23 11:12 ` rpm
[not found] ` <20020423124756.A3572@auto.ucl.ac.be>
[not found] ` <20020423115710.A31456@openminds.be>
[not found] ` <20020423134135.A7941@auto.ucl.ac.be>
2002-04-23 10:57 ` Frank Louwers
2002-04-23 13:10 ` Chris Friesen
2002-04-23 15:20 ` Vincent Guffens
2002-04-23 16:38 ` Chris Friesen
2002-04-23 20:54 ` Vincent Guffens
2002-04-23 19:19 ` Chris Friesen
2002-04-23 13:40 ` Jeff Garzik
2002-04-23 13:45 ` J.A. Magallon
2002-04-23 13:51 ` Frank Louwers
2002-04-23 13:58 ` Harley Stenzel [this message]
2002-04-23 16:05 ` Denis Vlasenko
2002-04-23 11:11 ` Frank Louwers
2002-04-23 16:21 ` Denis Vlasenko
2002-04-23 13:20 ` Jesse Pollard
2002-04-23 17:04 ` dean gaudet
2002-04-23 22:18 ` Bill Davidsen
2002-04-25 12:09 ` Roland Kuhn
-- strict thread matches above, loose matches on Subject: below --
2002-04-23 14:55 Dag Bakke
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=3CC56883.9020506@nc.rr.com \
--to=hstenzel@nc.rr.com \
--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