qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "John Poplett" <john.poplett@comcast.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] A QEMU net driver for OpenVPN's Tap-Win32 driver
Date: Mon, 11 Oct 2004 20:54:47 -0500	[thread overview]
Message-ID: <001001c4affe$743e2400$6500a8c0@cstreet> (raw)

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

Hi, all

Here is a patch that allows qemu to interface with OpenVPN's Tap-Win32
driver on windows. This provides an alternative to slirp and allows a guest
OS to appear as though it is directly connected to a LAN.

I have tested it by bridging OpenVPN's Tap-Win32 adapter with an Ethernet
adapter using Windows XP's software network bridge. It gets about 4Mbytes
bandwidth in either direction, tested with iperf on my 2.4 GHz P4. My test
environment consists of Windows XP (host), Slackware 10 (guest) and the 2.0 
beta 11 version of the Tap-Win32 driver. I have
not tested this code against ppc or sparc.

Most of the work was done by a friend who wishes to remain anonymous. I have
contributed the semaphore code, benchmarking and other minor tweaks.

The patch adds a new, win32 specific command line option: -tap adapter. 
"adapter" should be the name of an installed Tap-Win32 driver.

Here is an example command line using the new option:

qemu.exe -L %QEMU_HOME%\. -tap tap -m 128 -boot c -hda slackware-10-x86.img

John

[-- Attachment #2: tap-win32_3.patch.gz --]
[-- Type: application/x-gzip, Size: 6872 bytes --]

             reply	other threads:[~2004-10-12  2:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-12  1:54 John Poplett [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-09-30  1:47 [Qemu-devel] A QEMU net driver for OpenVPN's Tap-Win32 driver John Poplett
2004-10-03 16:59 ` Mike Tremoulet
2004-10-04 21:48   ` John Poplett

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='001001c4affe$743e2400$6500a8c0@cstreet' \
    --to=john.poplett@comcast.net \
    --cc=jpoplett@acm.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).