qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mike Tremoulet <coffeemike@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] pcap-based networking?
Date: Thu, 26 Aug 2004 12:19:27 -0500	[thread overview]
Message-ID: <564021330408261019668a33d1@mail.gmail.com> (raw)
In-Reply-To: <1093540521.3851.898.camel@aragorn>

On Thu, 26 Aug 2004 10:15:21 -0700, John R. Hogerhuis <jhoger@pobox.com> wrote:
> Just to clarify, TUN/TAP and user mode serve different ends.
> 
> User mode is zero-configuration, and does not require administrative
> rights to set it up. The slirp code code be improved in many ways, and
> the strategy has inherenent limitations, but as I said it has clear
> advantages.
> 
> Any alternative for the slirp solution would have to meet the
> zero-config, no admin rights test.
> 
> TUN/TAP is just a packet forwarding/tunnel solution, just like what you
> are describing. It is harder to set up than user mode networking, you
> need admin rights, but it is faster and certainly more flexible than
> user mode. It seems to me you are describing an alternative to TUN/TAP
> not user mode networing.
> 

True.  That's a better way to say it - can I have a TUN/TAP
alternative that runs on Windows?  It wouldn't be zero-config, but the
config could be minimal - install a TAP adapter, enable Internet
Connection Sharing, and point QEMU at the TAP interface.

Thanks for the clarification,
-- Mike

  reply	other threads:[~2004-08-26 17:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 16:42 [Qemu-devel] pcap-based networking? Mike Tremoulet
2004-08-26 17:15 ` John R. Hogerhuis
2004-08-26 17:19   ` Mike Tremoulet [this message]
2004-08-26 17:48     ` John R. Hogerhuis
2004-08-27  6:08       ` Mike Tremoulet
2004-08-27  6:28         ` John R. Hogerhuis
2004-08-27  6:32           ` Mike Tremoulet
2004-08-26 17:33 ` Jim C. Brown

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=564021330408261019668a33d1@mail.gmail.com \
    --to=coffeemike@gmail.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).