linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Summerfield <summer@os2.ami.com.au>
To: Linux-Kernel@vger.kernel.org
Subject: DHCP broken in 2.4.x
Date: Mon, 05 Nov 2001 21:49:15 +0800	[thread overview]
Message-ID: <200111051349.fA5DnFD29728@numbat.os2.ami.com.au> (raw)

x in this case is 13.

As I type this my DHCP server is saying

ov  5 20:58:12 dugite dhcpd: DHCPDISCOVER from 00:c0:26:2d:be:12 via 
eth0
Nov  5 20:58:12 dugite dhcpd: DHCPOFFER on 192.168.1.6 to 
00:c0:26:2d:be:12 via eth0
Nov  5 20:58:15 dugite dhcpd: DHCPDISCOVER from 00:c0:26:2d:be:12 via 
eth0
Nov  5 20:58:15 dugite dhcpd: DHCPOFFER on 192.168.1.6 to 
00:c0:26:2d:be:12 via eth0
Nov  5 20:58:19 dugite dhcpd: DHCPDISCOVER from 00:c0:26:2d:be:12 via 
eth0
Nov  5 20:58:19 dugite dhcpd: DHCPOFFER on 192.168.1.6 to 
00:c0:26:2d:be:12 via eth0
Nov  5 20:58:28 dugite dhcpd: DHCPDISCOVER from 00:c0:26:2d:be:12 via 
eth0
Nov  5 20:58:28 dugite dhcpd: DHCPOFFER on 192.168.1.6 to 
00:c0:26:2d:be:12 via eth0
Nov  5 20:58:42 dugite dhcpd: DHCPDISCOVER from 00:c0:26:2d:be:12 via 
eth0
Nov  5 20:58:42 dugite dhcpd: DHCPOFFER on 192.168.1.6 to 
00:c0:26:2d:be:12 via eth0
Nov  5 20:59:06 dugite dhcpd: DHCPDISCOVER from 00:c0:26:2d:be:12 via 
eth0
Nov  5 20:59:06 dugite dhcpd: DHCPOFFER on 192.168.1.6 to 
00:c0:26:2d:be:12 via eth0


and the poor sod at the other end is
setting half-duplex ....
sending DHCP and RARP requests .... Timed out!
IPConfig: Retrying forever (NFS root).


Here's how I'm booting:
root@numbat /root]# cat /misc/fd1/syslinux.cfg
default linux
prompt 1
display boot.msg
timeout 100
label linux
        kernel vmlinuz
        append  root=/dev/hda5
[root@numbat /root]

I'm running dhcp-2.0pl5-4 on RHL 7.1.

If I override the boot prompt:
ip=bootp
then it works.


Now I can see that I misunderstood the documentation (which, btw, could 
use a minor touch-up to mention DHCP), but

but

According to the source code, ip=dchp is legit. However, it causes lots 
of messages on the server just like above., and the client's looping 
just like before.

Two things I'd like to see:
1) A message to the user if an invalid value's given
2) DHCP actually work. BOOTP seems fine, as far as BOOTP goes.

I have RARP genned, but there's not actually anything to talk to.

-- 
Cheers
John Summerfield

Microsoft's most solid OS: http://www.geocities.com/rcwoolley/

Note: mail delivered to me is deemed to be intended for me, for my 
disposition.




                 reply	other threads:[~2001-11-05 15:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200111051349.fA5DnFD29728@numbat.os2.ami.com.au \
    --to=summer@os2.ami.com.au \
    --cc=Linux-Kernel@vger.kernel.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).