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: <4667D02E.2090404@bull.net> Date: Thu, 07 Jun 2007 11:30:22 +0200 From: Benjamin Thery <benjamin.thery@...l.net> To: David Miller <davem@...emloft.net> Cc: dev@...ru, containers@...ts.osdl.org, netdev@...r.kernel.org, dev@...nvz.org, kaber@...sh.net, xemul@...nvz.org Subject: Re: [Devel] Re: [PATCH] Virtual ethernet tunnel David Miller wrote: > From: Kirill Korotaev <dev@...ru> > Date: Thu, 07 Jun 2007 12:14:29 +0400 > >> David Miller wrote: >>> From: Pavel Emelianov <xemul@...nvz.org> >>> Date: Wed, 06 Jun 2007 19:11:38 +0400 >>> >>> >>>> 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. >>> >>> I would suggest choosing a different name. >>> >>> 'veth' is also the name of the virtualized ethernet device >>> found on IBM machines, driven by driver/net/ibmveth.[ch] >> AFAICS, ibmveth.c registers ethX devices, while this driver registers >> vethX by default, so there is no much conflict IMHO. > > If that's the case, veth is fine with me. I like Daniel's proposals with the tunnel or pipe thing in the name. I think it is more explicit about what the device really is. I'm currently using etun, Eric Biederman's implementation. It will be nice to have this kind of device merged. -- Benjamin -- B e n j a m i n T h e r y - BULL/DT/Open Software R&D http://www.bull.com - 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