From: Ross Boylan <ross@biostat.ucsf.edu>
To: kvm@vger.kernel.org
Cc: ross@biostat.ucsf.edu
Subject: bridges
Date: Thu, 07 May 2009 08:57:03 -0700 [thread overview]
Message-ID: <1241711823.5366.47.camel@corn.betterworld.us> (raw)
I'm trying to understand bridging with KVM, but am still puzzled.
I think that the recommended bridging with TAP means that packets from
the VM will end up going out the host card attached to the default
gateway. But it looks to me as if their IP address is unchanged, which
means replies will never reach me. Is that correct? Do I need to NAT
the packets, or is something already doing that?
Some documents indicate that I need to bring the interfaces (e.g., eth0)
down before I bring the bridge up, and that afterwards only the bridge
will have an IP address. Is that right?
Some documents, e.g.,
http://ebtables.sourceforge.net/br_fw_ia/br_fw_ia.html, indicate
iptables should "just work" with bridging. However, I've seen someone
with a 2.6.15 kernel ask about firewalling and be told they needed to
patch the kernel to get it work (don't have the reference handy).
Should it just work?
I'm running a 2.6.29 kernel on Debian Lenny with kvm 72+dfsg-5~lenny1.
Version 84+dfsg-2 is available in experimental. Is there much to be
gained by going with the more recent version?
Please cc me; I'm not on the list.
Thanks.
Ross Boylan
next reply other threads:[~2009-05-07 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 15:57 Ross Boylan [this message]
[not found] ` <4A03169C.60301@cs.ualberta.ca>
2009-05-07 17:48 ` bridges Ross Boylan
2009-05-07 19:19 ` bridges Cam Macdonell
2009-05-07 21:15 ` bridges Matthew Palmer
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=1241711823.5366.47.camel@corn.betterworld.us \
--to=ross@biostat.ucsf.edu \
--cc=kvm@vger.kernel.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