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: Thu, 21 Jun 2007 12:13:05 -0700 (PDT) From: David Miller <davem@...emloft.net> To: ebiederm@...ssion.com Cc: kaber@...sh.net, netdev@...r.kernel.org, shemminger@...ux-foundation.org, jeff@...zik.org Subject: Re: [RFC NET 00/02]: Secondary unicast address support From: ebiederm@...ssion.com (Eric W. Biederman) Date: Thu, 21 Jun 2007 13:08:12 -0600 > However this just seems to allow a card to decode multiple mac addresses > which in some oddball load balancing configurations may actually be > useful, but it seems fairly limited. > > Do you have a specific use case you envision for this multiple mac > functionality? Virtualization. If you can't tell the ethernet card that more than 1 MAC address are for it, you have to turn the thing into promiscuous mode. Networking on virtualization is typically done by giving each guest a unique MAC address, the guests have a virtual network device that connects to the control node (or dom0 in Xen parlace) and/or other guests. The control node has a switch that routes the packets from the guests either to other guests or out the real ethernet interface. Each guest gets a unique MAC so that the switch can know which guest an incoming packet is for. - 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