netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com, shollenbeck@verisign.com
Subject: Re: [PATCH][RFC] etherip: Ethernet-in-IPv4 tunneling
Date: Thu, 13 Jan 2005 01:29:59 +0100	[thread overview]
Message-ID: <20050113002959.GI14280@xi.wantstofly.org> (raw)
In-Reply-To: <20050112160455.3b839b21@dxpl.pdx.osdl.net>

On Wed, Jan 12, 2005 at 04:04:55PM -0800, Stephen Hemminger wrote:

> > After struggling with various userland VPN solutions for a while (and
> > failing to make IPSEC tunnel mode do what I want), I decided to just
> > implement ethernet-in-IP tunneling in the kernel and let IPSEC transport
> > mode handle the rest.
> > 
> > There appeared to be an RFC for ethernet-in-IP already, RFC 3378, so I
> > just implemented that.  It's very simple -- slap a 16-bit header (0x3000,
> > which is 4 bits of etherip version number and 12 bits of padding) onto
> > the beginning of the ethernet packet, and then wrap it in an IP packet.
> > 
> > Below is what I came up with, against the latest Fedora Core 3 kernel,
> > which is 2.6.10-something.  It survives some fairly basic testing between
> > a number of different machines, UP and SMP.  (Corresponding iproute2
> > patch is available from http://www.wantstofly.org/~buytenh/etherip/ )
> 
> Since it is an RFC, any chance of interoperability testing it with
> something besides Linux on the other end?

Some googling suggests that OpenBSD implements this as well.

Anyone here with an OpenBSD box on the 'net that's willing to do
some tests?


cheers,
Lennert

  reply	other threads:[~2005-01-13  0:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 22:24 [PATCH][RFC] etherip: Ethernet-in-IPv4 tunneling Lennert Buytenhek
2005-01-12 22:42 ` Ben Greear
2005-01-12 22:48   ` Lennert Buytenhek
2005-01-12 23:11     ` Ben Greear
2005-01-12 23:16       ` Lennert Buytenhek
2005-01-12 23:43         ` Thomas Graf
2005-01-13  0:18           ` Lennert Buytenhek
2005-01-13  0:28             ` Thomas Graf
2005-01-13  0:36               ` Lennert Buytenhek
2005-01-13  1:20                 ` Thomas Graf
2005-01-12 23:43         ` Ben Greear
2005-01-13  0:04 ` Stephen Hemminger
2005-01-13  0:29   ` Lennert Buytenhek [this message]
2005-01-13  7:49 ` Pekka Savola
2005-01-13  9:23   ` Lennert Buytenhek
2005-01-16 17:37     ` jamal
2005-01-16 18:55       ` tunneling in linux (was: Re: [PATCH][RFC] etherip: Ethernet-in-IPv4 tunneling) Lennert Buytenhek
2005-01-16 19:51         ` Pekka Savola
2005-01-16 19:57           ` Lennert Buytenhek
2005-01-17  5:45             ` Pekka Savola
2005-01-16 20:02         ` jamal
2005-01-16 20:20           ` Lennert Buytenhek
2005-01-16 20:37             ` Hasso Tepper
2005-01-16 21:21               ` Lennert Buytenhek
2005-01-16 21:32                 ` Hasso Tepper
2005-01-16 21:44                   ` Lennert Buytenhek
2005-01-16 23:09             ` jamal
2005-01-16 19:02       ` [PATCH][RFC] etherip: Ethernet-in-IPv4 tunneling Lennert Buytenhek
2005-01-16 20:05         ` jamal
2005-01-16 20:22           ` Lennert Buytenhek

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=20050113002959.GI14280@xi.wantstofly.org \
    --to=buytenh@wantstofly.org \
    --cc=netdev@oss.sgi.com \
    --cc=shemminger@osdl.org \
    --cc=shollenbeck@verisign.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).