From: Nick Popoff <cryptic-lkml@bloodletting.com>
To: linux-kernel@vger.kernel.org
Subject: Testing Dual Ethernet via Loopback
Date: Mon, 19 Apr 2004 06:14:21 -0700
User-Agent: KMail/1.5.4
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200404190614.21764.cryptic-lkml@bloodletting.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1283
Lines: 27

Greetings,

I am trying to write some software to test a dual port ethernet card.  I
was hoping to be able to use an ethernet cable to just connect the
ethernet board to itself and then write a program that talks to itself to
make sure that both ports are working.  However, I've noticed that Linux
is smart enough to realize it is talking to its own IP address, and it
just delivers the data internally rather than use the network hardware at
all.

So what I'm wondering is if there is a way to force Linux to actually
utilize its network hardware in sending these packets to itself?  In other
words, a ping or file transfer from an IP assigned to eth0 to another IP
assigned to eth1 should fail if I unplug the network cable connecting the
two.  Any advice on this would be much appreciated.  I'm not afraid of
reading kernel source but have no idea where to start on this one.

I'm using 2.4.22 but would use any 2.4 or 2.6 kernel that supported this
behavior. The National Semiconductor DP83815 (natsemi.o) is the 
ethernet chipset.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/