> The settings you were suggesting appear to be valid if I wanted to both
> hand out automatic ip address and respond to bootp requests with the
> same DHCP server. What I want to know, is if that can be done
> separately?
>> My original thoughts were to try and avoid having to change the config
> of the dhcp on my router or disable it while trying to netboot a machine
> via another instance on PC so that there wouldn't be any conflicts.
> Also didn't want to have to remember to re-enable it again afterwards.
>> Now while I've found a workable solution in this case, not all wireless
> routers are capable of being configured to respond in this way. So I
> basically want to see if my original thoughts could work, and could
> apply in situations where I either can't change the existing environment
> (DHCP server with no bootp enabled), or the hardware doesn't have the
> interfaces to premit me (wireless router with limited DHCP config).
>> Which can all probably be summed up as:
> What the hell, I just want to see if it could work. :)
It might work if you can tell your current dhcp server to ignore bootp
requests (it can be done in ISC DHCP),set up another dhcp server with
no pools) and an explicit host entry for the machine(s) you want to netboot.
But I'm not sure dhcpd will start without any pool declarations.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
