From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=33828 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pr5q3-0008H5-MK for qemu-devel@nongnu.org; Sun, 20 Feb 2011 04:44:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pr5q2-0006Vr-BI for qemu-devel@nongnu.org; Sun, 20 Feb 2011 04:44:23 -0500 Received: from fmmailgate03.web.de ([217.72.192.234]:43615) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pr5q1-0006Vn-Uq for qemu-devel@nongnu.org; Sun, 20 Feb 2011 04:44:22 -0500 Message-ID: <4D60E26D.3060202@web.de> Date: Sun, 20 Feb 2011 10:44:13 +0100 From: Jan Kiszka MIME-Version: 1.0 References: In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig07F7D536BF17635E0FF218BB" Sender: jan.kiszka@web.de Subject: [Qemu-devel] Re: Network bridging without adding bridge with brctl, possible? List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerhard Wiesinger Cc: qemu-devel@nongnu.org, Arnd Bergmann This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig07F7D536BF17635E0FF218BB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-02-19 20:32, Gerhard Wiesinger wrote: > Hello, >=20 > I like the way like VMWare Server 2.x does bridging: There is no need t= o > change basic network interface settings and add a bridge between the > existing network interface like e.g. discussed in: > http://www.linux-kvm.com/content/using-bridged-networking-virt-manager >=20 > VMWare Server 2.x does the following: > 1.) Add vmnet network interfaces with vmnet.tar code (should be GPL v2)= =2E > 2.) Starting a user mode process which I guess does the forwarding: > /usr/bin/vmnet-bridge > /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid -n 0 -i eth0 > 3.) 2 other processes: > /usr/bin/vmnet-netifup -d /var/run/vmnet-netifup-vmnet1.pid /dev/vmnet1= > vmnet1 > /usr/bin/vmnet-dhcpd -cf /etc/vmware/vmnet1/dhcpd/dhcpd.conf -lf > /etc/vmware/vmnet1/dhcpd/dhcpd.leases -pf > /var/run/vmnet-dhcpd-vmnet1.pid vmnet1 >=20 > /usr/bin/vmnet-bridge > Either the '-n' or '-p' option must be given exactly once. > Usage: vmnet-bridge (-n | -p) [-d] > [(-e | -i)] [-s] [-h] > -i include interface > -e exclude interface > -g prefer default gateway interface > -n virtual network > -p private virtual network > -d process identifier file name > -s optional pipe descriptor for service to send > a two byte startup status code > -h help >=20 > Might this also be easily possible with QEMU/KVM? > What do you thing about this? Worth to implement? > Any other suggestions to achieve this? http://virt.kernelnewbies.org/MacVTap Enabling host<->guest communication this way is still a bit unhandy IMHO. You need a fairly recent iproute2 version, then set up macvtap like this ip link add link eth1 name macvtap0 type macvtap mode bridge And you additionally seem to need a separate macvlan device attached to that bridge, configured to the IP of the host. ip link add link eth1 name macvlan0 type macvlan mode bridge ifconfig macvlan0 ... Not sure if this is by design or due to internals of the networking stack, but it looks unintuitive from user perspective. Maybe Arnd can shed a light on this. Of course, you could also simply offload all that setup to libvirt. Jan --------------enig07F7D536BF17635E0FF218BB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk1g4m0ACgkQitSsb3rl5xRSJACfZOOHrqrrLvsfr7OfU0Fvq9v4 +h8An2rxCYl16NYuxoHN2asSrhtRxyv9 =FR5O -----END PGP SIGNATURE----- --------------enig07F7D536BF17635E0FF218BB--