Boot file name not passed in boot reply if host not declared in conf

[Jeffrey Hutzelman]

--On Wednesday, April 30, 2008 01:05:30 AM +0200 Harry Zachrisson 
<harry at zachrisson.net> wrote:

> Hi.
> I have a problem getting the DHCP server to pass the boot file name in the
> boot reply if I dont specify my host in the dhcpd.conf file and I rather
> avoid that if possible.

What version of the DHCP server are you using?
On what platform are you running it?

> This works fine if my config file on the DHCP server looks like this:

Is that your entire dhcpd.conf?


> Reply:
> --------------------------------
> Bootstrap Protocol
>     Message type: Boot Reply (2)
>     Hardware type: Ethernet
>     Hardware address length: 6
>     Hops: 0
>     Transaction ID: 0x000079b2
>     Seconds elapsed: 5
>     Bootp flags: 0x0000 (Unicast)
>         0... .... .... .... = Broadcast flag: Unicast
>         .000 0000 0000 0000 = Reserved flags: 0x0000
>     Client IP address: 192.168.1.101 (192.168.1.101)
>     Your (client) IP address: 192.168.1.101 (192.168.1.101)
>     Next server IP address: 0.0.0.0 (0.0.0.0)
>     Relay agent IP address: 0.0.0.0 (0.0.0.0)
>     Client MAC address: SGI_0a:a2:70 (08:00:69:0a:a2:70)
>     Server host name not given
>     Boot file name not given
>     Option: (t=54,l=4) Server Identifier = 127.0.0.1
>     Option: (t=1,l=4) Subnet Mask = 255.255.255.0
>     End Option
> --------------------------------

Something here is not only preventing the filename from being sent, but 
also preventing siaddr from being set appropriately.  The presence of the 
server identifier option seems odd, too, as does its value.

-- Jeffrey T. Hutzelman (N3NHS) <jhutz+ at cmu.edu>
   Carnegie Mellon University - Pittsburgh, PA