From: "Sebastian Herbszt" <herbszt@gmx.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Re: [PATCH] Add pcap-based host network bridge
Date: Mon, 11 May 2009 23:30:23 +0200 [thread overview]
Message-ID: <7A9475ADF255438F86B48879B553733E@FSCPC> (raw)
In-Reply-To: <49CE5DD1.1010302@codemonkey.ws>
Anthony Liguori wrote:
> Jan Kiszka wrote:
>> 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?
>>
>
> What's the use-case you're trying to address? Who do you expect to use
> this functionality?
>
> Setting up bridging isn't really that bad on Linux. Is this primarily
> targeted at Windows? libpcap requires a kernel driver on Windows so I
> don't know that I believe it's a great general solution for Windows either.
I would really like to see pcap support in mainline (even as a windows only
feature). Qemu networking with pcap is trivial on windows. No need to
configure tap bridges, but just specify "ifname" and there you go.
- Sebastian
next prev parent reply other threads:[~2009-05-11 21:32 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 ` Sebastian Herbszt [this message]
2009-05-12 8:23 ` 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=7A9475ADF255438F86B48879B553733E@FSCPC \
--to=herbszt@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.