qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hetz Ben Hamo <hetzbh@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Regarding Linux TUN/TAP
Date: Fri, 15 Apr 2005 22:07:51 +0200	[thread overview]
Message-ID: <41e41e7a05041513075fe5764b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0504151754150.30308@filer.marasystems.com>

Hi Henrik, all..

Henrik, I think your patch is great and surely can help when using TUN/TAP..

However, I would like to point an issue (and I'm not criticizing
anyone here, I'm just asking for people thoughts, solutions)..

The SLiRP solution for QEMU is great if a user want to connect to the
net and browse, do some updates, etc, but it's not a good solution if
someone want to stuff like:

* Connect to host OS
* Connect to other machines in the LAN
* Use services from host OS

For the things in the list above to make them work, the solution is to
use TUN/TAP and/or VDE. These are great solutions  - but setting them
up is quite a challange for people who are nor familiar (or doesn't
have a big knowledge) with Linux.

What do people think could be a solution for end users? comments?

Thanks,
Hetz

On 4/15/05, Henrik Nordstrom <hno@marasystems.com> wrote:
> The attached patch updates the Linux TUN/TAP interface
>

  reply	other threads:[~2005-04-15 20:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-15 16:18 [Qemu-devel] [patch] Linux TUN/TAP driver updates Henrik Nordstrom
2005-04-15 20:07 ` Hetz Ben Hamo [this message]
2005-04-15 20:18   ` [Qemu-devel] Regarding Linux TUN/TAP Laurent Amon
2005-04-15 22:33     ` Paul Brook
2005-04-18 15:46   ` Henrik Nordstrom
2005-04-15 22:40 ` [Qemu-devel] [patch] Linux TUN/TAP driver updates Jean-Christian de Rivaz
2005-04-16  7:00   ` emuls

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=41e41e7a05041513075fe5764b@mail.gmail.com \
    --to=hetzbh@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).