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
| ||
|
Date: Fri, 19 Jan 2007 09:07:45 +0900 (JST) From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@...ux-ipv6.org> To: dim@...nvz.org Cc: containers@...ts.osdl.org, alexey@...ru, saw@...ru, akpm@...l.org, netdev@...r.kernel.org, yoshfuji@...ux-ipv6.org Subject: Re: [PATCH 0/12] L2 network namespace (v3) In article <200701171851.14734.dim@...nvz.org> (at Wed, 17 Jan 2007 18:51:14 +0300), Dmitry Mishin <dim@...nvz.org> says: > =================================== > L2 network namespaces > > The most straightforward concept of network virtualization is complete > separation of namespaces, covering device list, routing tables, netfilter > tables, socket hashes, and everything else. > > On input path, each packet is tagged with namespace right from the > place where it appears from a device, and is processed by each layer > in the context of this namespace. > Non-root namespaces communicate with the outside world in two ways: by > owning hardware devices, or receiving packets forwarded them by their parent > namespace via pass-through device. Can you handle multicast / broadcast and IPv6, which are very important? --yoshfuji - 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