From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1C1DsS-0003F2-EF
	for qemu-devel@nongnu.org; Sat, 28 Aug 2004 20:49:00 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1C1DsQ-0003EI-T4
	for qemu-devel@nongnu.org; Sat, 28 Aug 2004 20:49:00 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1C1DsQ-0003E5-PW
	for qemu-devel@nongnu.org; Sat, 28 Aug 2004 20:48:58 -0400
Received: from [66.163.168.179] (helo=smtp800.mail.sc5.yahoo.com)
	by monty-python.gnu.org with smtp (Exim 4.34) id 1C1DnZ-0003uH-TU
	for qemu-devel@nongnu.org; Sat, 28 Aug 2004 20:43:58 -0400
From: Joe Menola <menola@sbcglobal.net>
Subject: Re: [Qemu-devel] eth0 problems
Date: Sat, 28 Aug 2004 19:43:55 -0500
References: <4130FF10.4040502@neenet.com>
	<200408281918.38859.menola@sbcglobal.net>
	<20040829003335.GA15499@jbrown.mylinuxbox.org>
In-Reply-To: <20040829003335.GA15499@jbrown.mylinuxbox.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200408281943.55470.menola@sbcglobal.net>
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

On Sat August 28 2004 7:33 pm, Jim C. Brown wrote:
> On Sat, Aug 28, 2004 at 07:18:38PM -0500, Joe Menola wrote:
> > On Sat August 28 2004 6:04 pm, Lonnie Cumberland wrote:
> > > No, the /etc/qemu-ifup does not exist and my host eth0 is there but the
> > > guest linux.img eth0 does not show. Only the "lo" loopback.
> >
> > -user-net doesn't provide eth0 in your qemu host. It provides internet
> > access only. To get full networking (eth0) you need to setup a tun
> > device.
> >
> > -jm
>
> Technically, tun doesn't provide eth0 for the host either. In fact, the
> kernel documentation says you need to have eth0 first, or else you cant use
> tuntap (that may no longer be true though, remember this is from the
> offical kernel docs :). tuntap provides a tun0/tap0 device in the host and
> an eth0 device in the guest. user net should provide an eth0 as well, but
> it won't add anything to the host.
>
> If eth0 doesn't show, that may be due to lack of hardware support. Be sure
> your kernel has support for the ne2k-pci module.
>
> user net isn't just for internet access .. the guest can still access the
> LAN or the WAN/intranet .. they just can't initiate a talk to it.
>
You're correct...nor can network shares be accesed?

Thanks for the correction.

-jm