public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Gustavo F. Padovan" <gustavo@padovan•org>
To: netdev@vger•kernel.org
Cc: marco bonola <marco.bonola@gmail•com>,
	"ZioPRoTo (Saverio Proto)" <zioproto@gmail•com>,
	Behling Mario <mb@mariobehling•de>,
	"L. Aaron Kaplan" <aaron@lo-res•org>
Subject: IP/UDP encapsulation
Date: Thu, 8 Apr 2010 04:42:47 -0300	[thread overview]
Message-ID: <20100408074247.GA19798@vigoh> (raw)

Hi,

I'm looking for some advice on that work. The Freifunk organization is
planning work on the IP/UDP encapsulation kernel module as a GSoC
project. The idea is to create a IP-in-UDP tunnel like we do for
IP-in-IP or IP-in-GRE tunnels. The only way to do that today is to use
some VPN software.

The module will export its virtual interface through sockets and will
have support for the standard syscalls like the others encapsulation
modules.

It will improve the performance of mesh networks that will we be able
to use IP-in-UDP rather than IP-in-IP. So, instead of push all data to
local gateway into the mesh all the data can be tunneled to a faster
server and from there to the Internet. With all the data exiting with
the same IP address (the fast server IP). That will improve bandwidth,
especially for upload.

Is such module acceptable for merge into the Linux Kernel?

Any comments or suggestions to the module architecture and
implementation? If you want more information about the module I can
provide that.

Regards,

-- 
Gustavo F. Padovan
http://padovan.org

             reply	other threads:[~2010-04-08  7:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08  7:42 Gustavo F. Padovan [this message]
2010-04-08  7:58 ` IP/UDP encapsulation Eric Dumazet
2010-04-08  9:48 ` Mark Smith
2010-04-08 10:29   ` Eric Dumazet
2010-04-08 10:39     ` ZioPRoTo (Saverio Proto)

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=20100408074247.GA19798@vigoh \
    --to=gustavo@padovan$(echo .)org \
    --cc=aaron@lo-res$(echo .)org \
    --cc=marco.bonola@gmail$(echo .)com \
    --cc=mb@mariobehling$(echo .)de \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=zioproto@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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