qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "John Poplett" <john.poplett@comcast.net>
To: Mike Tremoulet <coffeemike@gmail.com>,
	John Poplett <jpoplett@acm.org>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] A QEMU net driver for OpenVPN's Tap-Win32 driver
Date: Mon, 4 Oct 2004 16:48:05 -0500	[thread overview]
Message-ID: <000e01c4aa5b$d4f10e50$6900a8c0@cstreet> (raw)
In-Reply-To: 564021330410030959451391f4@mail.gmail.com

Hi, Mike

Another developer sent me a patch recently that looks promising. It is based 
on the user-mode code in openvpn and works with the Tap-Win32 driver. I am 
out of town for a few days and have some more coding to do when I get back 
but will keep you posted.

Regards,

John

----- Original Message ----- 
From: "Mike Tremoulet" <coffeemike@gmail.com>
To: "John Poplett" <jpoplett@acm.org>; <qemu-devel@nongnu.org>
Sent: Sunday, October 03, 2004 11:59 AM
Subject: Re: [Qemu-devel] A QEMU net driver for OpenVPN's Tap-Win32 driver


> John --
>
> I had looked into this only very slightly.  My thoughts were to use
> libpcap/libnet to essentially be a generic network adapter that could
> take over any network device, with the goal of using that to
> read/write from a TAP driver.  I'm not sure how the libpcap vs.
> winpcap API lines up, and I think (not 100% sure) that winpcap can
> write to the device as well, but that was the idea.  A command line
> switch could specify which network device to control, so I could
> concievably run multiple QEMUs with multiple TAP devices.
>
> I spent a week hunting down the networking code in QEMU (hey, I
> haven't done *that* much C programming lately) and then, well, life
> got busy.  I'd love to see this added, though, as it seems much more
> stable than the SLIRP in place today.
>
> -- Mike
>
>
> On Wed, 29 Sep 2004 20:47:32 -0500, John Poplett
> <john.poplett@comcast.net> wrote:
>> Hi, all
>>
>> I'm looking at what it would take to create a QEMU net driver to 
>> interface
>> with OpenVN's Tap-Win32 driver. So far it looks fairly straightforward to
>> do. colinux interfaces to Tap-Win32 already. Has anyone else looked into
>> this?
>>
>> John
>>
>> _______________________________________________
>> Qemu-devel mailing list
>> Qemu-devel@nongnu.org
>> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>>
>
> __________ NOD32 1.882 (20041002) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.nod32.com
>
> 

  reply	other threads:[~2004-10-04 21:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-12  1:54 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='000e01c4aa5b$d4f10e50$6900a8c0@cstreet' \
    --to=john.poplett@comcast.net \
    --cc=coffeemike@gmail.com \
    --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).