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 [thread overview]
Message-ID: <200404190614.21764.cryptic-lkml@bloodletting.com> (raw)
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.
next reply other threads:[~2004-04-20 1:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 13:14 Nick Popoff [this message]
2004-04-20 19:26 ` Pavel Machek
2004-04-22 20:54 ` Richard B. Johnson
2004-04-22 22:33 ` Anton Blanchard
2004-04-20 22:38 ` Edgar Toernig
2004-04-20 13:46 Antony Suter
2004-04-20 16:01 ` Richard B. Johnson
2004-04-22 11:08 Nick Popoff
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=200404190614.21764.cryptic-lkml@bloodletting.com \
--to=cryptic-lkml@bloodletting.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
all inboxes | Powered by JetHome®