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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 02 May 2007 14:07:26 +0200 From: Daniel Lezcano <dlezcano@...ibm.com> To: Pavel Emelianov <xemul@...ru> CC: David Miller <davem@...emloft.net>, Patrick McHardy <kaber@...sh.net>, Linux Netdev List <netdev@...r.kernel.org>, Linux Containers <containers@...ts.osdl.org>, Ben Greear <greearb@...delatech.com>, Stephen Hemminger <shemminger@...ux-foundation.org>, devel@...nvz.org Subject: Re: [Devel] [PATCH] Virtual ethernet device (tunnel) Pavel Emelianov wrote: > Veth stands for Virtual ETHernet. It is a simple tunnel driver > that works at the link layer and looks like a pair of ethernet > devices interconnected with each other. > > Mainly it allows to communicate between network namespaces but > it can be used as is as well. > > Eric recently sent a similar driver called etun. This > implementation is closer to the OpenVZ one and it lacks > some unimportant features of etun driver (like ethtool_ops) > for simplicity. > > The general difference from etun is that a netlink interface > is used to create and destroy the pairs. The patch for an > ip utility is also provided. if etun and veth are similar, why didn't you put the netlink interface to the etun driver instead of sending a new driver ? -- Daniel - 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