From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EM9eD-0005ht-RU for qemu-devel@nongnu.org; Sun, 02 Oct 2005 15:37:23 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EM9e5-0005e2-P5 for qemu-devel@nongnu.org; Sun, 02 Oct 2005 15:37:14 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EM9e5-0005VA-I5 for qemu-devel@nongnu.org; Sun, 02 Oct 2005 15:37:13 -0400 Received: from [128.8.10.163] (helo=po1.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EM9RN-0003xP-4a for qemu-devel@nongnu.org; Sun, 02 Oct 2005 15:24:05 -0400 Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.253.219]) by po1.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j92JO4Zw005034 for ; Sun, 2 Oct 2005 15:24:04 -0400 (EDT) Date: Sun, 2 Oct 2005 15:23:48 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] about DHCP server in qemu Message-ID: <20051002192347.GA13825@jbrown.mylinuxbox.org> References: <1128006042.433c019a295a8@webmail.alinto.com> <20050929203431.GA4684@jbrown.mylinuxbox.org> <433C61B7.6070804@wasp.net.au> <20050929221406.GA6019@jbrown.mylinuxbox.org> <1128068224.433cf48005ab5@webmail.alinto.com> <20050930131014.GA14173@jbrown.mylinuxbox.org> <1128091901.433d50fd7d9d3@webmail.alinto.com> <20051001211702.GC553@jbrown.mylinuxbox.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Sun, Oct 02, 2005 at 04:39:59AM +0200, Henrik Nordstrom wrote: > 1.1.1.1 is not a QEMU given IP. > I know. I have no idea why that shows up. > Try manually assigning the IP 10.0.2.15/24(255.255.255.0) to the quest > with a default route to 10.0.2.2. This should work. > Already did. It does. 10.0.2.2 is pingable, at least. > It is quite possible the guest is not happy about something in the qemu > DHCP reply. QEMU responds with a DHCP reply even if the client sent a > BOOTP request and this can confuse some badly implemented BOOTP clients, > and the number of DHCP options returned differ slightly from most DHCP > servers possibly confusing some DHCP clients expecting additional options. > The client is definitely using (and expecting) DHCP, not BOOTP. Oddly enough, it gets a timeout error. Very strange. I tried to test out pump under tomsbrt but it refused to work; I'm too lazy to attempt recompile a real dhcp client under a floppy linux. Since the pump binary that I was using works under the redhat distro that it came from, I'm guessing that its a bug in the LUA client. Will investigate further. > Regards > Henrik > > > _______________________________________________ > 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.