netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Pekka Savola <pekkas@netcore.fi>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: RFC:  Redirect-Device
Date: Fri, 01 Apr 2005 08:29:19 -0800	[thread overview]
Message-ID: <424D76DF.5070002@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0504011222140.10960@netcore.fi>

Pekka Savola wrote:
> On Thu, 31 Mar 2005, Ben Greear wrote:
> 
>>> Is there something in your problem statement I'm missing?
>>
>>
>> That would be similar to what I'm doing, but I'm not really trying
>> to tunnel anything.  I am trying to duplicate the behaviour of two
>> ethernet interfaces connected by an external cross-over cable, and I'm
>> trying to duplicate it at the network-device interface level so that
>> common tools (and my own tools) can treat these virtual interfaces
>> just like ethernet interfaces.
> 
> 
> Oh ok, what you seem to want is some kind of "Ethernet loopback++", but 
> the "looped" packets should come back from a virtual interface instead 
> of the same interface?

Yes.  In practice, I use a pair of virtual interfaces, so I send on one
virtual and receive on the other.  I use separate software to bridge,
or the normal linux stacks to route, the packets to other interfaces,
including real interfaces.

> Btw, does the kernel support traditional loopback, so that at the last 
> stage, just before sending a packet on the wire, it would be pushed back.

Not that I'm aware of.


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

      reply	other threads:[~2005-04-01 16:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31 20:41 RFC: Redirect-Device Ben Greear
2005-03-31 21:02 ` David S. Miller
2005-03-31 21:05 ` Stephen Hemminger
2005-03-31 21:45   ` Ben Greear
2005-03-31 21:52     ` David S. Miller
2005-03-31 22:04       ` Ben Greear
2005-03-31 22:21         ` David S. Miller
2005-03-31 22:05       ` Stephen Hemminger
2005-03-31 22:26         ` Ben Greear
2005-03-31 22:33           ` David S. Miller
2005-03-31 22:42             ` Ben Greear
2005-03-31 22:43               ` David S. Miller
2005-03-31 21:13 ` jamal
2005-03-31 21:26   ` Ben Greear
2005-03-31 21:53     ` jamal
2005-03-31 22:22       ` Ben Greear
2005-03-31 22:35         ` David S. Miller
2005-03-31 22:54           ` Ben Greear
2005-03-31 23:26             ` jamal
2005-03-31 23:56               ` Ben Greear
2005-04-01  0:53                 ` jamal
2005-04-01  9:01                 ` bert hubert
2005-04-01 16:58                   ` Ben Greear
2005-03-31 22:46         ` Thomas Graf
2005-03-31 23:00           ` Ben Greear
2005-03-31 23:20         ` jamal
2005-03-31 23:35           ` Ben Greear
2005-03-31 23:46             ` jamal
2005-04-02  8:41   ` Meelis Roos
2005-04-02 21:08     ` jamal
2005-04-01  5:03 ` Pekka Savola
2005-04-01  5:27   ` Ben Greear
2005-04-01  9:28     ` Pekka Savola
2005-04-01 16:29       ` Ben Greear [this message]

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=424D76DF.5070002@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=netdev@oss.sgi.com \
    --cc=pekkas@netcore.fi \
    /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).