[ILUG] pxeboot & dhcp

[Darragh Bailey]

On Wed, Mar 11, 2009 at 04:01:18PM +0000, Lars Hecking wrote:
> Darragh Bailey writes:
<snipage>
> > In any case, I was doing some reading on syslinux and from reading it I
> > seems that since bootp is an extension and a separate request that it
> > might be possible to have 2 dhcp instances running within the same
> > network. 1 which takes care of assigning addresses, i.e. the instance
> > running on my linkSys wireless device and should basically ignore any
> > bootp requests, and a second instance that I can start on my PC along
> > with tftpd only when I need to, and is configured to only handle bootp
> > requests.
> > 
> > I haven't looked at it closely enough, so I don't know if dhcp even 
> > allows you to do this as part of the protocol standard and additionally 
> > whether it is then actually implemented to allow this for the dhcpd that 
> > would be installed on my PC.
> > 
> > Anyone tried anything like this before?
>  
>  I'm not sure I understand. What would you need a second dhcpd instance for?
>  Ok, I'm not familiar with the Linksys' dhcp, but ISC dhcpd does implement
>  bootp. I have in fact done something similar recently (installed OBSD on a
>  Soekris 5501 through the serial port [as control channel] via pxeboot).
>  The dhcp server and the tftp server are two separate machines. dhcpd is
>  configured

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. :)


-- 
Darragh

"Nothing is foolproof to a sufficiently talented fool."