[Etherboot-developers] dhcpd won't answer the initial broadcast from the client

[Eno C. <Eno...@Mi...>]

Thanks, Ken,

That helps much. I am sorry about this but I have given this my best shot
and I cannot get dhcpd to dance. Here's another question.

I have religiously followed the READMEs from the distribution. Have the
initial broadcast packet coming from the client. But the dhcpd server ( runs
on vinilla RedHat 6.1) will not answer that sucker. Have put a monitor on
the net and verified the packet is as it should be. Have studied the
/etc/dhcpd.conf file which I copy here.

option domain-name "test.com";
option domain-name-servers 192.168.0.1;
option broadcast-address 192.168.0.255;
subnet 192.168.1.0 netmask 255.255.255.0 {
	filename "/tftpdir/vmlinuz.xterm";
	host xterm {
		hardware ethernet 00:40:53:01:22:36;
		option host-name "xterm";
		fixed-address 192.168.0.100;
	}
}

Have verified dhcpd is running. Every time I change dhcpd.conf, I kill the
server daemon and restart it to insure the new conf file gets read. Can't
think how to proceed. 

Have any ideas?

Eno

 -----Original Message-----
From: 	Ken Yap [mailto:ke...@nl...] 
Sent:	Thursday, February 01, 2001 9:15 PM
To:	eth...@li...
Subject:	Re: [Etherboot-developers] what is meant by, ..." set a path
explicitly to tftpd "... ? 

|The 4.7.17 distribution states, in README-3.html, "It is recommended that
|you set a path explicitly to tftpd instead of relying on any defaults. For
|example:
|
|tftp   dgram   udp   wait   root   /usr/sbin/tcpd   in.tftpd   /tftpdir
|
|Would somebody please explain what this means?

That's a typical line to be put in /etc/inetd.conf. The meanings of the
various fields are explained in the man page for inetd, but the ones of
interests are the last three. They say: run tcpd (tcpwrappers), and when
a connection comes in, invoke /usr/sbin/in.tftpd (implied directory),
with an argument of /tftpdir.

Now it is possible to invoke in.tftpd with no arguments and this
typically means, accept the compiled-in default top directory of
/tftpboot. I do not like this because:

1. I prefer to keep my boot images separate from the exported root
trees; they are different kettles of fish.

2. I do not like files in my exported root trees to be available to
tftp, e.g. someone might do:

	tftp /tftpboot/xterminal/etc/passwd

and get hold of passwords to crack.

Hence my practice is to explicitly tell in.tftpd which is to be the top
directory for boot images.  Things may vary a bit depending on which
tftpd you are using (there are several around).

_______________________________________________
Etherboot-developers mailing list
Eth...@li...
http://lists.sourceforge.net/lists/listinfo/etherboot-developers