qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Add pcap-based host network bridge
Date: Tue, 24 Mar 2009 18:28:09 +0100	[thread overview]
Message-ID: <49C91829.6000606@siemens.com> (raw)
In-Reply-To: <49C6F2AA.40408@codemonkey.ws>

Anthony Liguori wrote:
> Jan Kiszka wrote:
>> This introduces bridged networking via pcap. Both Unix and Windows
>> platforms are supported.
>>
>> While tap-based bridging provides basically the same support pcap does,
>> the latter is often more handy to set up. Under Linux, it doesn't
>> require to configure a bridge and it is able to bypass the ebtables if
>> this is desired. Also under Windows, the bridge setup can be lengthy
>> procedure compared to using the pcap interface.
>>
>> Signed-off-by: Klaus Wenninger <klaus.wenninger@siemens-enterprise.com>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>>   
> 
> The previous version of this had a fundamental flaw wrt guest->host
> communication on Linux.  My understanding was that this was an intrinsic
> limitation of pcap.

To my understanding too. We will try to look closer at this, maybe there
are smarter alternatives at least on some platforms (PF_PACKET under
Linux...?).

Klaus explained to me that there is some switch in winpcap to support
this, but it caused troubles due to weird packet loops. I don't have a
Windows platform to test, but I will see if we can clarify this in some
other way.

> 
> That's a blocker IMHO because it will invariably lead to many folks
> asking why ping to the host doesn't work (just like slirp).  Since it
> still requires root privileges, I don't think it improves a lot on tap.
> 

Well, in case we do not find a workaround for host<->guest
communication, would the patch remain unacceptable even with proper,
prominent documentation of this shortcoming?

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

  reply	other threads:[~2009-03-24 17:28 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   ` Jan Kiszka [this message]
2009-03-28 17:26     ` [Qemu-devel] " 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
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=49C91829.6000606@siemens.com \
    --to=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).