From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1DMXL0-0006k2-0T
	for qemu-devel@nongnu.org; Fri, 15 Apr 2005 16:22:50 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1DMXKv-0006ij-GP
	for qemu-devel@nongnu.org; Fri, 15 Apr 2005 16:22:47 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1DMXKu-0006gz-Tk
	for qemu-devel@nongnu.org; Fri, 15 Apr 2005 16:22:44 -0400
Received: from [213.228.0.44] (helo=postfix3-1.free.fr)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1DMXH1-0007Pe-Fp
	for qemu-devel@nongnu.org; Fri, 15 Apr 2005 16:18:43 -0400
Mime-Version: 1.0 (Apple Message framework v619.2)
In-Reply-To: <41e41e7a05041513075fe5764b@mail.gmail.com>
References: <Pine.LNX.4.61.0504151754150.30308@filer.marasystems.com>
	<41e41e7a05041513075fe5764b@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <c2ee65b95b02e1e866a778236afa2349@stanfordalumni.org>
Content-Transfer-Encoding: 7bit
From: Laurent Amon <amon@stanfordalumni.org>
Subject: Re: [Qemu-devel] Regarding Linux TUN/TAP
Date: Fri, 15 Apr 2005 22:18:36 +0200
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Hetz Ben Hamo <hetzbh@gmail.com>, qemu-devel@nongnu.org

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.