qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Amon <amon@stanfordalumni.org>
To: Hetz Ben Hamo <hetzbh@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Regarding Linux TUN/TAP
Date: Fri, 15 Apr 2005 22:18:36 +0200	[thread overview]
Message-ID: <c2ee65b95b02e1e866a778236afa2349@stanfordalumni.org> (raw)
In-Reply-To: <41e41e7a05041513075fe5764b@mail.gmail.com>

Hi Hetz,

On 15 avr. 05, at 22:07, Hetz Ben Hamo wrote:
> 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.
>
I don't really follow you. I believe Slirp is OK when you want to 
connect from the guest to the host or the net at large. Didn't you mean 
"guest" instead of "host" in the sentences above?

Another solution would be to run a PPP server on the host and connect 
through PPP (using user-net) from the guest to the host. In this case, 
provided the host routes the connection, you should have your virtual 
machine fully on the net.

Lga.

  reply	other threads:[~2005-04-15 20:22 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 ` [Qemu-devel] Regarding Linux TUN/TAP Hetz Ben Hamo
2005-04-15 20:18   ` Laurent Amon [this message]
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=c2ee65b95b02e1e866a778236afa2349@stanfordalumni.org \
    --to=amon@stanfordalumni.org \
    --cc=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).