From: Anton Blanchard <anton@samba.org>
To: netdev@oss.sgi.com
Cc: ja@ssi.bg
Subject: [cryptic-lkml@bloodletting.com: Re: Testing Dual Ethernet via Loopback]
Date: Sun, 25 Apr 2004 11:17:06 +1000 [thread overview]
Message-ID: <20040425011706.GD20714@krispykreme> (raw)
Hi,
We have found Julian Anastasov's send-to-self patch extremely useful in
the lab. There seem to be a number of other people who agree, what are
the chances of getting it merged into 2.6?
Ive got a version rediffed against recent BK if required.
Anton
----- Forwarded message from Nick Popoff <cryptic-lkml@bloodletting.com> -----
From: Nick Popoff <cryptic-lkml@bloodletting.com>
To: Anton Blanchard <anton@samba.org>, linux-kernel@vger.kernel.org
Subject: Re: Testing Dual Ethernet via Loopback
On Fri, 23 Apr 2004, Anton Blanchard wrote:
> Sounds like you need the send-to-self patch:
> http://www.ssi.bg/~ja/
> We've been using it a lot in the lab, it works well.
I tried this out yesterday with Linux 2.6.5 at it worked like a charm. Thank
you to everyone who replied with solutions and to the author of this patch!
I thought the idea of pinging an invalid IP from one interface while snooping
with ethereal on the other interface was very clever, but hard to use for
performance testing. :-)
----- End forwarded message -----
reply other threads:[~2004-04-25 1:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040425011706.GD20714@krispykreme \
--to=anton@samba.org \
--cc=ja@ssi.bg \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).