Displaying 3 results from an estimated 3 matches for "pxespec".
Did you mean:
espec
2015 Sep 12
2
pxelinux tries to load ldlinux.c32 from DHCP server, instead of next-server
On Sat, Sep 12, 2015 at 6:37 PM, Gene Cumm <gene.cumm at gmail.com> wrote:
> On Sat, Sep 12, 2015 at 10:23 AM, Geert Stappers <stappers at stappers.nl> wrote:
>> Euh, could this be reviewed:
>>
>> diff --git a/core/fs/pxe/dhcp_option.c b/core/fs/pxe/dhcp_option.c
>> index 8d93a6a..b82e944 100644
>> --- a/core/fs/pxe/dhcp_option.c
>> +++
2015 Sep 13
0
pxelinux tries to load ldlinux.c32 from DHCP server, instead of next-server
..., attempt to resolve then set serverip.
> > Last, if serverip is not set, copy siaddr to serverip.
>
> Perhaps a more important question is if ANY PXE implementation uses
> DHCP option 66 over BOOTP field siaddr.
Quoting the spec ( I used http://www.pix.net/software/pxeboot/archive/pxespec.pdf )
sname, 64 bytes, Can be overloaded if using Opt 66
Hope this helps
Groeten
Geert Stappers
--
Leven en laten leven
2015 Sep 13
3
pxelinux tries to load ldlinux.c32 from DHCP server, instead of next-server
...n set serverip.
>> > Last, if serverip is not set, copy siaddr to serverip.
>>
>> Perhaps a more important question is if ANY PXE implementation uses
>> DHCP option 66 over BOOTP field siaddr.
>
> Quoting the spec ( I used http://www.pix.net/software/pxeboot/archive/pxespec.pdf )
>
> sname, 64 bytes, Can be overloaded if using Opt 66
>
> Hope this helps
I didn't question the specification, where BOOT field sname or DHCP
option 66 could be loaded with some string. I questioned if any
_implementation_ (ie a PC with PXE OROM) bothers to pay attention...