From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1C1EBL-0002AQ-L2 for qemu-devel@nongnu.org; Sat, 28 Aug 2004 21:08:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1C1EBK-0002AE-3n for qemu-devel@nongnu.org; Sat, 28 Aug 2004 21:08:31 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C1EBK-0002AB-0h for qemu-devel@nongnu.org; Sat, 28 Aug 2004 21:08:30 -0400 Received: from [38.113.3.61] (helo=smtp-out.hotpop.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1C1E6D-0006NW-2G for qemu-devel@nongnu.org; Sat, 28 Aug 2004 21:03:13 -0400 Received: from phreaker.net (kubrick.hotpop.com [38.113.3.103]) by smtp-out.hotpop.com (Postfix) with SMTP id 13D3C7E223B for ; Sun, 29 Aug 2004 01:03:12 +0000 (UTC) Received: from jbrown.mylinuxbox.org (pcp03144805pcs.midval01.tn.comcast.net [68.59.228.236]) by smtp-3.hotpop.com (Postfix) with ESMTP id 6BD1C10A649E for ; Sun, 29 Aug 2004 01:03:09 +0000 (UTC) Date: Sat, 28 Aug 2004 21:03:07 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] eth0 problems Message-ID: <20040829010306.GA15763@jbrown.mylinuxbox.org> References: <4130FF10.4040502@neenet.com> <200408281918.38859.menola@sbcglobal.net> <20040829003335.GA15499@jbrown.mylinuxbox.org> <200408281943.55470.menola@sbcglobal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408281943.55470.menola@sbcglobal.net> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Sat, Aug 28, 2004 at 07:43:55PM -0500, Joe Menola wrote: > > 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? > Not sure. A node on the lan can't access shares on the user net guest, but the guest may be able to access shares on the node ... this depends on the protocol in question. Windows shares have the additional complication that they have to be on the same subnet, although I am not familar with Windows XP and above so they may have removed this limitation (Samba removes this limitation if you set an option in its config file). > Thanks for the correction. > > -jm > -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.