DHCP, bootpd, WFWG & Windows 95

DHCP, bootpd, WFWG & Windows 95

Post by Neil Thomps » Thu, 15 Jun 1995 04:00:00



Hi all,

We have quite a large WFWG network here, and I'm running a Linux box
which acts as our DNS, mailserver & general Internet connection box.  The
WFWG network administrator has just come off a course where he's gotten
all e*d about the NT DHCP setup.  Not wanting to have data duplicated
all over the place I set up bootpd (2.4 - the latest on sunsite) to try
and test whether it'll do the job.

Here's the relevant part of the bootptab -

external:       hn:ht=ethernet:ha=0020AF9AC803:dn=spl.co.za:ds=196.14.5.2:\
                :sm=255.255.255.0:gw=196.14.5.1:

and here's the syslog entry of what happens when I try to start the
Windows box -

in.bootpd[260]: recvd pkt from IP addr 0.0.0.0
in.bootpd[260]: bootptab mtime: Wed Jun 14 11:08:04 1995
in.bootpd[260]: request from Ethernet address 00:20:AF:9A:C8:03
in.bootpd[260]: found 196.14.5.22 (external)
in.bootpd[260]: bootfile=""
in.bootpd[260]: vendor magic field is 99.130.83.99
in.bootpd[260]: request message length=548
in.bootpd[260]: extended reply, length=548, options=312
in.bootpd[260]: sending reply (with RFC1048 options)
in.bootpd[260]: setarp 196.14.5.22 - 00:20:AF:9A:C8:03

This all looks good to me.

Unfortunately, (you knew that was coming didn't you :-), the WFWG box
just sits there for a while and then comes up with a message about not
being able to find the DHCP server.  This same box with no change in
config is able to use the NT DHCP server with no problems.  I have also
tried this with a box using Windows 95 Final Beta - same problem.

So, does anyone know what the problem is?  Can bootpd 2.4 not handle
DHCP, or has Uncle Bill done a dirty on us again and used a strange
proprietry version of the protocol?

Alternatively, does anyone have another piece of software for Linux which
can do the job?

Thanks

--
Neil

=========== It don't mean a thing if it ain't got that swing ==============

 
 
 

DHCP, bootpd, WFWG & Windows 95

Post by John Duks » Mon, 19 Jun 1995 04:00:00




>Unfortunately, (you knew that was coming didn't you :-), the WFWG box
>just sits there for a while and then comes up with a message about not
>being able to find the DHCP server.  This same box with no change in
>config is able to use the NT DHCP server with no problems.  I have also
>tried this with a box using Windows 95 Final Beta - same problem.
>So, does anyone know what the problem is?  Can bootpd 2.4 not handle
>DHCP, or has Uncle Bill done a dirty on us again and used a strange
>proprietry version of the protocol?

First, yes Uncle Bill has hosed the WFW implementation of DHCP, but not
in the manner that you are expecting. The DCHP spec states that DHCP
responses should be unicasts, where as MS has made them broadcasts.

Unfortunately, DHCP clients cannot accept a bootp response, because DHCP
has this concept of "Leasing" an IP address for x amount of time.
You're going to need to get a DHCPd for linux if one exists.

Good Luck

-John

 
 
 

DHCP, bootpd, WFWG & Windows 95

Post by Stephane FILL » Wed, 21 Jun 1995 04:00:00


: Hi all,

[...]
: in.bootpd[260]: setarp 196.14.5.22 - 00:20:AF:9A:C8:03

: This all looks good to me.

        and you're right !

[.... Uncle Bill is ..... ]

        we know this ;-)

: Alternatively, does anyone have another piece of software for Linux which
: can do the job?

        yes, look at this article posted some time ago; it works for me !

| Hi Andrew,
|
| > If you've done a later version of your DHCP patch, can you let me
| > know? I sometimes get questions about DHCP, so I point people to you
| > and your patch on nimbus.
|
| Sure, I made a new version of the patch for bootp-2.4.2
| which also integrates lots of comments I got on the previous
| one :)
|
| I will include the patch below...
|
| Could you please add a remark that bootp-related questions
| should be forwarded to the bootp-list, and not me?
| Oh, and that the latest version of bootp can be found at
|       firewall.mc.com:/pub
|
|     Met vriendelijke groet,
|         Pauline Middelink
| +------------------------------+-------------------------------------+

| | Boterkorfhoek 34             | zakelijk : 053-780020               |
| | 7546 JA  Enschede, Holland   | fax/data : 053-780021 (ook ISDN)    |
| +------------------------------+-------------------------------------+

        the patch is too long, download it from :

  ftp://iutserveur.univ-lyon1.fr/pub/linux/tcpview/DHCP.patch

        this should help....   8-)
--

Universite Lyon 1                         | "Un homme seul est en        
Institut Universitaire de Technologie A   |      mauvaise compagnie" P.Valery

 
 
 

1. Windows NT DHCP clients and SunOS 4.x BOOTPD+DHCP patches

I've been unable to get bootpd with DHCP patches on SunOS 4.1.3
to work with our Windows NT clients.  The problem appears to be
that the NT clients want the DHCP reply sent to 255.255.255.255,
but SunOS 4.x is unable to do that.  The network number for the
DHCP client and bootp server is 199.4.88.0, and I can send the reply
to 199.4.88.255, but not 255.255.255.255.  The sendto() fails with
ENETUNREACH.

I have been able to run the bootp server on a Solaris 2.3 box and
have it work with the Windows NT DHCP clients, because Solaris has
no problems sending to 255.255.255.255.

Is there any way to get BOOTP on a SunOS 4.x box to work with
Windows NT, or am I stuck with having to use Solaris 2?


2. Menubar sizes in X

3. I want Linux, Windows 95 & Windows NT all on C:

4. IPX - Anyone using it?

5. Installing Windows 95, Windows NT & Linux on same hard disk

6. Monitor refresh rates

7. OS/2 Warp && Windows 95

8. smp

9. Linux && Windows 95

10. dhcp server and windows 95

11. Windows 95 and ISC dhcp beta 5.14 server problem

12. Linux DHCP with Windows 95?

13. dhcp and windows 95