When retrieving next-server/filename options during autboot from 2nd and
subsequent NIC's after a boot failure, settings obtained from previous
NIC's may be used - with erroneous results. Fix this by unregistering
all DHCP obtained parameters before trying the next interface.
Signed-off-by:
When doing autoboot in a proxydhcp environment, the settings-fetch for
next-server returns the IP given by a DHCP server which has nothing to
do with PXEboot and has not specified a boot filename. This happens even
when ProxyDHCP has been selected for boot and has returned a boot
filename. Fix
At our site we want to be able to store a series of values from a
single DHCP option (in our case, kernel arguments) in this manner:
set kargs ${net0/224:string}
I'm including our patch which allows multiple value arguments to the
'set' command. This change does not break or affect existing
On Fri, Sep 17, 2010 at 9:43 PM, Pasi Kärkkäinen pa...@iki.fi wrote:
On Fri, Sep 17, 2010 at 02:59:11PM -0400, Joshua Oreman wrote:
On Fri, Sep 17, 2010 at 2:52 PM, Pasi Kärkkäinen pa...@iki.fi wrote:
Any ideas?
Setting use-cached to zero in the DHCP packet won't override
gpxelinux.0's
