From: Frank Louwers <frank@openminds.be>
To: linux-kernel@vger.kernel.org
Subject: BUG: 2 NICs on same network
Date: Tue, 23 Apr 2002 11:39:35 +0200 [thread overview]
Message-ID: <20020423113935.A30329@openminds.be> (raw)
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.
Now the strange thing is that traffic for 1.2.3.2 arrives at eth0 no
matter what!
Even if we disconnect the cable for eth1, 1.2.3.2 still replies to
pings, ssh, web, ...
We tested this on IA32 architecture, different 2.4.x kernels and
different nics ...
Is this a bug or a known issue? If it is not a bug, how can it be
solved?
Kind Regards,
Frank Louwers
--
Openminds bvba www.openminds.be
Tweebruggenstraat 16 - 9000 Gent - Belgium
next reply other threads:[~2002-04-23 9:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 9:39 Frank Louwers [this message]
2002-04-23 10:53 ` BUG: 2 NICs on same network 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
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=20020423113935.A30329@openminds.be \
--to=frank@openminds.be \
--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