From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Elwp3-0003i8-LK for qemu-devel@nongnu.org; Mon, 12 Dec 2005 18:11:09 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Elwp0-0003fe-JM for qemu-devel@nongnu.org; Mon, 12 Dec 2005 18:11:06 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Elwp0-0003fE-0E for qemu-devel@nongnu.org; Mon, 12 Dec 2005 18:11:06 -0500 Received: from [213.92.5.108] (helo=fe-4c.inet.it) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Elwqn-0005xr-4m for qemu-devel@nongnu.org; Mon, 12 Dec 2005 18:12:57 -0500 Message-ID: <439E035D.9040804@tiscali.it> Date: Tue, 13 Dec 2005 00:10:21 +0100 From: Cesare Leonardi MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] User mode network and multiple nics 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 Hi all. Some days ago i have done some tests using the user mode network stack with multiple network interfaces and i noticed some strange behaviours that i would report to you. I use QEMU 0.7.2 under Debian Sid, using the package provided by the distribution, and the guest OS is Debian testing. I've observed the following things using "-nics n": 1) all the networks interfaces are detected correctly during the boot phase: eth0, eth1, ... ethn-1, ethn; 2) the DHCP server doesn't work with the first n-1 interfaces but it's OK with the last. For example, with "-nics 4" DHCP works only with eth3 and not with eth0,1,2 and with "-nics 2" works only with eth1. To try out, in the guest system leave all nics unconfigured, then launch the DHCP client on each nic separately. For example, lauching dhclient 2.0p15 on the first n-1 interfaces, after some wait, it terms saying "No DHCPOFFERS received". With ethn works. 3) in general, seems that the network (not only DHCP) doesn't work correctly with first n-1 interfaces. Trying to leave all network interfaces unconfigured and trying to configure each of them individually with IP 10.0.2.20, netmask 255.255.255.0, 10.0.2.2 as gateway and 10.0.2.3 as DNS: - all nics can ping its IP address; - only ethn can ping 10.0.2.2, the others gets "Destination host unreachable" from the IP of the network card; - none of the nics can ping 10.0.2.3: all gets "Destination host unreachable" from the IP of the network card, except ethn, that doesn't obtain responses (but the name resolution seems to work); - only ethn can go out the 10.0.2.x network (internet, for example). Anyone has experienced such behaviour that appear to me as bug(s)? It's a known thing (googling around the mailng-list and internet i have found nothing)? Cesare.