netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Joerg Roedel <joro-lkml@zlug.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	davem@davemloft.net
Subject: Re: [PATCH] EtherIP tunnel driver (RFC 3378)
Date: Mon, 18 Sep 2006 22:52:52 +0200	[thread overview]
Message-ID: <20060918205252.GA6830@xi.wantstofly.org> (raw)
In-Reply-To: <20060911204129.GA28929@zlug.org>

On Mon, Sep 11, 2006 at 10:41:29PM +0200, Joerg Roedel wrote:

> This driver implements the tunneling of Ethernet packets over IPv4
> networks for Linux. It uses the protocol defined in RFC 3378.

Check out the thread "[PATCH][RFC] etherip: Ethernet-in-IPv4 tunneling"
that was on netdev in January of 2005 -- a number of arguments against
etherip (and for tunneling ethernet in GRE) were raised back then.

One of the most significant ones, IMHO:

> Another argument against etherip would be that OpenBSD apparently
> mis-implemented etherip by putting the etherip version nibble in the
> second nibble of the etherip header instead of the first, which would
> probably prevent the linux and OpenBSD versions from interoperating,
> negating the advantage of using etherip in the first place.


cheers,
Lennert

  parent reply	other threads:[~2006-09-18 20:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-11 20:41 [PATCH] EtherIP tunnel driver (RFC 3378) Joerg Roedel
2006-09-13 16:27 ` Patrick McHardy
2006-09-14  1:21 ` Philip Craig
2006-09-14  1:33   ` Stephen Hemminger
2006-09-14  9:52   ` Joerg Roedel
2006-09-14 10:11     ` Patrick McHardy
2006-09-14 23:06       ` Philip Craig
2006-09-15  8:17         ` Joerg Roedel
2006-09-18 20:52 ` Lennert Buytenhek [this message]
2006-09-19  7:08   ` Joerg Roedel

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=20060918205252.GA6830@xi.wantstofly.org \
    --to=buytenh@wantstofly.org \
    --cc=davem@davemloft.net \
    --cc=joro-lkml@zlug.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).