From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel@nongnu.org
Cc: Jung-uk Kim <jkim@FreeBSD.org>
Subject: [Qemu-devel] Re: [PATCH] Add pcap-based host network bridge
Date: Tue, 24 Mar 2009 18:21:51 +0100 [thread overview]
Message-ID: <49C916AF.3010307@siemens.com> (raw)
In-Reply-To: <B2D2B134E08348FCA4F75E3D46D88AC4@FSCPC>
Sebastian Herbszt 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.
>
> This looks like the pcap approach by Jung-uk Kim [1]. It was reported that
> guest <-> host communication didn't work on Linux [2]. Is this also true
> for
> this patch?
Yes, it is, see my reply to Anthony.
>
> [1] http://article.gmane.org/gmane.comp.emulators.qemu/27304
> [2] http://article.gmane.org/gmane.comp.emulators.qemu/27553
>
>> Signed-off-by: Klaus Wenninger <klaus.wenninger@siemens-enterprise.com>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>>
>> Makefile.target | 2 configure | 35 ++++++++
>> net.c | 252
>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> qemu-doc.texi | 14 +++
>> vl.c | 4 +
>> 5 files changed, 305 insertions(+), 2 deletions(-)
>>
>
> [snip]
>
>> diff --git a/net.c b/net.c
>> index c853daf..3cf372d 100644
>> --- a/net.c
>> +++ b/net.c
>> @@ -93,6 +93,13 @@
>> #endif
>> #endif
>>
>> +#if defined(CONFIG_PCAP)
>> +#include <pcap.h>
>> +#ifdef _WIN32
>> +#include <remote-ext.h>
>> +#endif /* _WIN32 */
>> +#endif /* CONFIG_PCAP */
>> +
>> #if defined(__OpenBSD__)
>> #include <util.h>
>> #endif
>> @@ -1033,6 +1040,241 @@ static int net_tap_init(VLANState *vlan, const
>> char *model,
>>
>> #endif /* !_WIN32 */
>>
>> +#if defined(CONFIG_PCAP)
>> +
>> +#ifdef _WIN32
>> +#define ADAPTER_KEY
>> "SYSTEM\\CurrentControlSet\\Control\\Class" \
>> +
>> "\\{4D36E972-E325-11CE-BFC1-08002BE10318}"
>> +#define NETWORK_CONNECTIONS_KEY
>> "SYSTEM\\CurrentControlSet\\Control\\Network" \
>> +
>> "\\{4D36E972-E325-11CE-BFC1-08002BE10318}"
>> +#endif
>
> ADAPTER_KEY doesn't seem to be used.
>
Thanks, will drop it when posting an update.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-03-24 17:22 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 [this message]
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
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=49C916AF.3010307@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=jkim@FreeBSD.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).