From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BdDhM-0000Hk-PE for qemu-devel@nongnu.org; Wed, 23 Jun 2004 15:46:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BdDhH-0000FZ-Md for qemu-devel@nongnu.org; Wed, 23 Jun 2004 15:46:20 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BdDhH-0000D6-ES for qemu-devel@nongnu.org; Wed, 23 Jun 2004 15:46:15 -0400 Received: from [199.232.41.8] (helo=mx20.gnu.org) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1BdDff-0006jm-FG for qemu-devel@nongnu.org; Wed, 23 Jun 2004 15:44:35 -0400 Received: from [38.113.3.61] (helo=babyruth.hotpop.com) by mx20.gnu.org with esmtp (Exim 4.34) id 1BdDXm-0002UH-Rn for qemu-devel@nongnu.org; Wed, 23 Jun 2004 15:36:27 -0400 Received: from phreaker.net (kubrick.hotpop.com [38.113.3.103]) by babyruth.hotpop.com (Postfix) with SMTP id EBF60635EC9 for ; Wed, 23 Jun 2004 18:55:21 +0000 (UTC) Date: Wed, 23 Jun 2004 15:32:45 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] Question about tun/tap networking Message-ID: <20040623193245.GA24051@jbrown.mylinuxbox.org> References: <200406230754.07821.pjr@ucar.edu> <20040623170325.GB22835@jbrown.mylinuxbox.org> <1088010992.30210.58.camel@sherbert> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1088010992.30210.58.camel@sherbert> 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 Wed, Jun 23, 2004 at 06:16:32PM +0100, Gianni Tedesco wrote: > On Wed, 2004-06-23 at 13:03 -0400, Jim C. Brown wrote: > > That is tricky. You will need to look into bridging. > > There are a few ways to do it: > o static nat > o iptables nat > o bridging > > Try this qemu-ifup for script for the iptables method: > > http://www.scaramanga.co.uk/stuff/qemu-ifup > That's not what he asked for. AFAICT that script will set up a separate subnet, 192.168.1.*, instead of using the 192.168.0.* subnet. It won't do what he wants. (It looks like that to the outside world it will have an ip of $qemu_ip, but from inside the guest OS he will still be on a separate subnet.) In any case my recommendation is that he uses VDE and maintains all the virtual machines on a separate subnet from his actual LAN (assuming thats possible, of course some Windows machines will refuse to browse SMB network shares that aren't on the same subnet ... but thats slightly off-topic). > -- > // Gianni Tedesco (gianni at scaramanga dot co dot uk) > lynx --source www.scaramanga.co.uk/scaramanga.asc | gpg --import > 8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.