From: Adrian Gschwend <ktk@netlabs.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Bridge with qemu VMs & VDE
Date: Fri, 07 Jul 2006 15:50:20 -0000 [thread overview]
Message-ID: <e8lves$jvo$1@sea.gmane.org> (raw)
Hi all,
I try to connect my qemu sessions to the "normal" local network, I would
like to do it bridged, which means I don't want to port/ip forwards or
anything like this.
I set up VDEv2.0 and launched vde_switch, tap0 gets created. As long as
I work like this and start qemu with vdeqemu everything works fine, I
can use the whole setup as a virtual switch and ping the tun0 IP and the
VMs.
Now I thought I will create a bridge interface, let's call it br0. I add
eth0 to the bridge with "brctl addif eth0", and I do the same for tap0.
Problem is that it doesn't seem to work, brctl show still shows both
interaces but I can't do anything with tap0 now anymore, neither tcpdump
from the host nor pinging or anything from the guest.
I checked all docs I found for VDE but I don't get what I am doing
wrong. Is this possible after all with VDE? If not, what other options
do I have to use qemu sessions in a transparent way from the network POV?
thanks
Adrian
next reply other threads:[~2006-07-07 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 15:50 Adrian Gschwend [this message]
2006-08-21 15:23 ` [Qemu-devel] Bridge with qemu VMs & VDE James Oakley
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='e8lves$jvo$1@sea.gmane.org' \
--to=ktk@netlabs.org \
--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).