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: Thu, 31 Mar 2005 21:27:05 -0800 [thread overview]
Message-ID: <424CDBA9.80703@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0504010801170.6417@netcore.fi>
Pekka Savola wrote:
> On Thu, 31 Mar 2005, Ben Greear wrote:
>
>> I created a new virtual ethernet device that solves a problem
>> I faced. I thought I'd see if anyone else sees a use for this,
>> and if so, I'll work to polish the patch so that it can be
>> accepted into the kernel.
>
>
> Unless I'm misunderstanding..
>
> You seem to have pretty much duplicated the work by Lennert (see thread
> "[PATCH][RFC] etherip: Ethernet-in-IPv4 tunneling" from January).
>
> That particular thread seemed to conclude that instead of creating
> something new, you can just use GRE tunneling to bridge Ethernet, and it
> works in a multi-vendor environment as well.
>
> 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.
I think I may be the only one that needs such a thing, and since I'm
reluctant to remove the /proc interface, I don't think this will be
going into the official kernel soon. If anyone does end up wanting
this later, I can email them my consolidated patch....
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2005-04-01 5:27 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 [this message]
2005-04-01 9:28 ` Pekka Savola
2005-04-01 16:29 ` Ben Greear
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=424CDBA9.80703@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).