From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1BuYxw-0005OB-Uh
	for qemu-devel@nongnu.org; Tue, 10 Aug 2004 11:55:09 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1BuYxu-0005Nz-T8
	for qemu-devel@nongnu.org; Tue, 10 Aug 2004 11:55:08 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1BuYxu-0005Nw-NR
	for qemu-devel@nongnu.org; Tue, 10 Aug 2004 11:55:06 -0400
Received: from [81.209.184.159] (helo=dd2718.kasserver.com)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1BuYtJ-0004Yo-Ch
	for qemu-devel@nongnu.org; Tue, 10 Aug 2004 11:50:21 -0400
Received: from [192.168.0.7] (dsl-082-083-136-207.arcor-ip.net [82.83.136.207])
	by dd2718.kasserver.com (Postfix) with ESMTP id 9CA2D18738
	for <qemu-devel@nongnu.org>; Tue, 10 Aug 2004 17:50:14 +0200 (CEST)
Message-ID: <4118EEBE.1020009@fabianowski.de>
Date: Tue, 10 Aug 2004 17:50:22 +0200
From: Bartosz Fabianowski <bartosz@fabianowski.de>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Help with tun/tap with qemu
References: <20040810150655.25395.qmail@webmail-au.server-secure.com>
In-Reply-To: <20040810150655.25395.qmail@webmail-au.server-secure.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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: qemu-devel@nongnu.org

> So I am trying TUN/TAP.  The guest and host OS can ping each other.
> However, the guest OS cannot ping any other host

If the setup on Linux is any similar to that on FreeBSD (and I am sure 
it is), the problem probably is routing. The guest and host are on 
different networks. So, you need to tell your host to forward packets to 
and from the guest's network. You didn't have that problem in slirp, 
because slirp bridges between the two networks for you, it implicitly 
does the forwarding.

Unfortunately, I can't tell you how to add the route under Linux due to 
my lack of experience with that platform.

- Bartosz