qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] about DHCP server in qemu
Date: Sun, 2 Oct 2005 15:23:48 -0400	[thread overview]
Message-ID: <20051002192347.GA13825@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0510020422550.21519@filer.marasystems.com>

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.

  reply	other threads:[~2005-10-02 19:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29 15:00 [Qemu-devel] about DHCP server in qemu octane indice
2005-09-29 20:34 ` Jim C. Brown
2005-09-29 21:50   ` Brad Campbell
2005-09-29 22:14     ` Jim C. Brown
2005-09-30  8:17       ` octane indice
2005-09-30 12:21         ` Oliver Gerlich
2005-09-30 13:10         ` Jim C. Brown
2005-09-30 14:51           ` octane indice
2005-10-01 21:17             ` Jim C. Brown
2005-10-02  2:39               ` Henrik Nordstrom
2005-10-02 19:23                 ` Jim C. Brown [this message]
2005-10-03 11:34                   ` octane indice
2005-09-30 18:28           ` John R. Hogerhuis
2005-09-30 21:37             ` Henrik Nordstrom
2005-09-30 21:59             ` Jim C. Brown
2005-10-03 15:55               ` octane indice
2005-10-03 18:12                 ` Henrik Nordstrom
2005-10-03 19:20                 ` Christian MICHON
2005-10-03 20:37                   ` Henrik Nordstrom
2005-10-04  7:47                     ` Christian MICHON
2005-10-04 11:43                       ` Jim C. Brown
2005-10-05  9:38                       ` Henrik Nordstrom
2005-10-03 21:31                 ` Jim C. Brown
2005-10-04  4:19                   ` octane indice

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051002192347.GA13825@jbrown.mylinuxbox.org \
    --to=jma5@umd.edu \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).