From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fc9Tf-0005Yn-IL for qemu-devel@nongnu.org; Fri, 05 May 2006 19:12:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fc9Te-0005X8-0U for qemu-devel@nongnu.org; Fri, 05 May 2006 19:12:51 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fc9Td-0005X3-PK for qemu-devel@nongnu.org; Fri, 05 May 2006 19:12:49 -0400 Received: from [213.165.64.20] (helo=mail.gmx.net) by monty-python.gnu.org with smtp (Exim 4.52) id 1Fc9Tt-0007Tz-Hg for qemu-devel@nongnu.org; Fri, 05 May 2006 19:13:05 -0400 Message-ID: <445BDBF2.9060605@gmx.de> Date: Sat, 06 May 2006 01:12:50 +0200 From: Oliver Gerlich MIME-Version: 1.0 Subject: Re: [Qemu-devel] bug reports and suggestions References: <20060505215128.4171C1DC197@ravel.n2.net> In-Reply-To: <20060505215128.4171C1DC197@ravel.n2.net> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Don Kitchen schrieb: > Next, it seems the *one* thing QEMU lacks that you-know-who does correctly > is networking, specifically bridged mode. I know about creating a tap device > and sticking it into a bridge (really hasn't worked for me, but that's the > subject for a different day.) I realize that it's a complicated issue > requiring kernel modules, etc, and exponentially more complicated with > cross platform, but I wonder if anyone has considered trying to tie into > the vmware-player's kernel modules and use them? There has to be some sort > of de-facto API for interaction between the modules and the player. Too > rife with IP problems? Someone wrote a kernel module some months ago which exposes some special kernel function via /proc ... IIUC this was intended to allow easier networking... Does anyone know more about it (or did anyone understand my confusing description ;) ? Another interesting thing concerning networking: I use a little script to set up a bridge between eth0 and tap0; but I have give the new bridge interface (eg. br0) an IP address and such stuff, because eth0 doesn't work. This is with Linux 2.6, but I read that with Linux 2.4 it was not necessary to configure br0, as eth0 would still be accessible. Does anyone know why this changed? I think it would be much easier if an interface used in a bridge was still usable. Thanks, Oliver -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEW9vwTFOM6DcNJ6cRApc8AJ9qYCEBHJqu/TsWilH5ztnx+PF8wACffVTp 2AbeG8IcGxMz3lO1BUeZ3gY= =a4mn -----END PGP SIGNATURE-----