Create a BootP netboot server on an existing DHCP network?
 

Ok, I've literally spent weeks trying to get this to work, and despite my best efforts I just can't get this working. Anyways, I already have a router setup on my network which is acting as the DHCP server (DLink Dl-524). I'm trying to get a server (running Suse 9.3) which is on that network to act as a BootP server. (Already have NFS, and TFTP working flawlessly, DHCP net-booting is fine, but some legacy computers need bootp) I tried the bootps server in xinetd but for whatever reason no tests would successfully connect and no reply was ever received. So I moved on to using dhcpd and in the dhcpd.conf declaring "allow bootp;" But I can't get dhcpd to get onto the network because it is already in use specifically the problem is: "Can't bind to dhcp address: Address already in use... exiting."

Is there any way to work around this? And if that would work is it even possible to have the BootP server not be the actual DHCP server/router? (will forwarding ports 67 and 68 (bootp) on the router to the server work?) Thanks in advance for any help. I'm stumped.
:scratch:

Ok, so here is my current dhcpd.conf:

#Standard dhcpd options
default-lease-time 600;
max-lease-time 7200;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.255;
option routers 192.168.1.1;
allow bootp;
not authoritative;

# the subnet from which dhcp requests will come
subnet 192.168.1.0 netmask 255.255.255.0 {

# the host to boot in BootP
host iMac233 {
hardware ethernet 00:03:93:93:54:18;
fixed-address 192.168.1.4;
filename "/store/Netboot/yaboot";
server-name "192.168.1.8";
next-server 192.168.1.8;
{
{

Is there any option to make the server just listen on DHCP and only respond to BootP requests?

Come on, anyone? Would declaring "shared-network" work maybe?

Edit: Is it impossible or something? If this just isn't possible I'd really appreciate someone just saying it or something, 72 people so far and nothing?

Not authoritative
 

I have a similar problem, I'm on a largish campus where the central services provide a DHCP server and a bootp server.

Watching my log messages and the chatter on the wire via wireshark I conclude the main DHCP server hears my response, and slaps me down with a "not authoritative" message.

I see you have the "not authoritative" thing in your config as well. I suspect if you change that to "authoritative" one of following will happen.
* it works.
* everything else stops working.

Do let me know which!

I'm reluctant to experiment or quite a few other PC's on my subnet may stop working... :-)