From: Gerhard Wiesinger <lists@wiesinger.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Network bridging without adding bridge with brctl, possible?
Date: Sat, 19 Feb 2011 20:32:59 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1102192024040.22181@bbs.intern> (raw)
Hello,
I like the way like VMWare Server 2.x does bridging: There is no need to
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
VMWare Server 2.x does the following:
1.) Add vmnet network interfaces with vmnet.tar code (should be GPL v2).
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
/usr/bin/vmnet-bridge
Either the '-n' or '-p' option must be given exactly once.
Usage: vmnet-bridge (-n<number> | -p<uuid>) [-d<file name>]
[(-e<interface> | -i<interface>)] [-s<number>] [-h]
-i<interface> include interface
-e<interface> exclude interface
-g prefer default gateway interface
-n<number> virtual network
-p<uuid> private virtual network
-d<file name> process identifier file name
-s<number> optional pipe descriptor for service to send
a two byte startup status code
-h help
Might this also be easily possible with QEMU/KVM?
What do you thing about this? Worth to implement?
Any other suggestions to achieve this?
Thnx.
Ciao,
Gerhard
--
http://www.wiesinger.com/
next reply other threads:[~2011-02-19 19:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 19:32 Gerhard Wiesinger [this message]
2011-02-20 9:44 ` [Qemu-devel] Re: Network bridging without adding bridge with brctl, possible? Jan Kiszka
2011-02-20 10:19 ` Gerhard Wiesinger
2011-02-20 11:19 ` Jan Kiszka
2011-02-20 21:28 ` Arnd Bergmann
2011-02-21 6:12 ` Gerhard Wiesinger
2011-02-20 12:49 ` Gerhard Wiesinger
2011-02-20 14:15 ` Jan Kiszka
2011-02-20 15:19 ` Gerhard Wiesinger
2011-02-20 17:39 ` Jan Kiszka
2011-02-20 20:03 ` Gerhard Wiesinger
2011-02-20 21:33 ` Arnd Bergmann
2011-02-21 6:40 ` Gerhard Wiesinger
2011-02-21 8:44 ` Jan Kiszka
2011-02-21 12:07 ` Arnd Bergmann
2011-02-23 6:38 ` Gerhard Wiesinger
2011-02-23 12:53 ` Jan Kiszka
2011-02-24 6:49 ` Gerhard Wiesinger
2011-02-24 7:50 ` Jan Kiszka
2011-02-24 8:00 ` Arnd Bergmann
2011-02-23 14:47 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.02.1102192024040.22181@bbs.intern \
--to=lists@wiesinger.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).