| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20100408074247.GA19798@vigoh> Date: Thu, 8 Apr 2010 04:42:47 -0300 From: "Gustavo F. Padovan" <gustavo@...ovan.org> To: netdev@...r.kernel.org Cc: marco bonola <marco.bonola@...il.com>, "ZioPRoTo (Saverio Proto)" <zioproto@...il.com>, Behling Mario <mb@...iobehling.de>, "L. Aaron Kaplan" <aaron@...res.org> Subject: IP/UDP encapsulation 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 -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists