qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel@nongnu.org, Sebastian Herbszt <herbszt@gmx.de>
Subject: Re: [Qemu-devel] Re: [PATCH] Add pcap-based host network bridge
Date: Tue, 12 May 2009 13:09:32 -0400	[thread overview]
Message-ID: <20090512170932.GK21463@csclub.uwaterloo.ca> (raw)
In-Reply-To: <4A09A4FC.5000108@siemens.com>

On Tue, May 12, 2009 at 06:34:04PM +0200, Jan Kiszka wrote:
> Lennart Sorensen wrote:
> > On Tue, May 12, 2009 at 10:23:43AM +0200, Jan Kiszka wrote:
> >> We basically dropped the idea as it turned out that - at least under
> >> Linux - there is no host<->guest link realizable with reasonable effort.
> > 
> > Has anyone ever looked at how vmware's vmnet does it?
> 
> Whatever they do (I bet it's nothing trivial): Everything that
> complicates the pcap-based approach beyond a certain level (roughly the
> one that is required for tap-based bridges) makes it unattractive. There
> are alternatives (except for ancient Win2k IIRC), pcap just appeared to
> be a cheap shortcut. But that turned out to be not true.

Not sure.  I just know with the vmware approache, the guest can be
bridged to the network in a way that allows the guest to talk to the
host as well as anything else on the external network, which to me is
by far the nicest setup.  I still haven't clued in to how to make vmware
talk to the host system and allow incoming connections on a real IP yet.
Guest to host works through 10.2.2.2 or something like that, but nothing
else ever has for me.  Maybe I just haven't managed to make sense of the
-net documentation to figure out which of the very many options would
do what I want.

Vmware's vmnet does look like a lot of code (somewhere near 400k) and
has some binary only code included, so who knows.  Certainly involves
bridging though.

-- 
Len Sorensen

  reply	other threads:[~2009-05-12 17:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18  9:33 [Qemu-devel] [PATCH] Add pcap-based host network bridge Jan Kiszka
2009-03-22 20:38 ` Robert Riebisch
2009-03-22 21:38 ` [Qemu-devel] " Sebastian Herbszt
2009-03-24 17:21   ` Jan Kiszka
2009-03-23  2:23 ` [Qemu-devel] " Anthony Liguori
2009-03-24 17:28   ` [Qemu-devel] " Jan Kiszka
2009-03-28 17:26     ` Anthony Liguori
2009-05-11 21:30       ` [Qemu-devel] " Sebastian Herbszt
2009-05-12  8:23         ` [Qemu-devel] " Jan Kiszka
2009-05-12 15:48           ` Lennart Sorensen
2009-05-12 16:34             ` Jan Kiszka
2009-05-12 17:09               ` Lennart Sorensen [this message]
2009-05-12 21:45             ` Paul Brook
2009-05-12 21:17           ` Sebastian Herbszt
2009-05-20 17:43             ` Consul
2009-05-28 20:50               ` Sebastian Herbszt
2009-05-28 21:52                 ` Consul
2009-06-06 17:13                   ` Sebastian Herbszt
2009-06-06 18:40                     ` Alex
2009-06-08 21:27                       ` Consul
2009-06-09 20:13                         ` Sebastian Herbszt
2009-06-09 21:49                           ` Consul
2009-06-10 21:39                             ` Sebastian Herbszt

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=20090512170932.GK21463@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=herbszt@gmx.de \
    --cc=jan.kiszka@siemens.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).