[syslinux] Syslinux-5.10-pre1 looks for ldlinux.c32 in TFTP instead of HTTP

[Gene Cumm]

On Mar 8, 2013 5:54 AM, "Tobias Göbel" <kubax1983 at gmail.com> wrote:
>
> Am Freitag, 08.03.2013 01:40, schrieb Gene Cumm:
>
>> On Thu, Mar 7, 2013 at 12:57 PM, Tobias Göbel <kubax1983 at gmail.com>
wrote:
>>>
>>> Am 07.03.2013 18:24, schrieb H. Peter Anvin:
>>>
>>>> On 03/07/2013 04:51 AM, Matt Fleming wrote:
>>>>>
>>>>> On Thu, 2013-03-07 at 13:32 +0100, Tobias Göbel wrote:
>>>>>>
>>>>>> As you can see, everything is set to HTTP and i have no clue, why
>>>>>> pxelinux.0 tries to load it from TFTP anyways.
>>>>>
>>>>> The lwIP PXE stack is called lpxelinux.0 in 5.10-pre1, not pxelinux.0.
>>>>> pxelinux.0 is the legacy code.
>>>>>
>>>> So the legacy stack does special things when it sees gPXE/iPXE
>>>> underneath it; it talks a custom protocol with iPXE to allow it to use
>>>> TCP-based protocols using the stack in iPXE.
>>>>
>>>> The lwIP-based stack shouldn't need to do that, and probably shouldn't,
>>>> but it is not well know how much problem the iPXE stack being in
between
>>>> will cause.  I suspect we need to get the iPXE people involved, though.
>>>>
>>>> We should check, though, that we aren't simply using vestiges of the
>>>> custom protocol that is tripping us up.
>>>>
>>>>          -hpa
>>>
>>> I'll try tomorrow at work, if legacy pxelinux works.
>>> But i think i'll not work, i didn't checked the logs from the TFTP
server
>>> back then, but the "ldlinux.c32 not found" thingy was there, too.
>>>
>>> I'll report back tomorrow.
>>
>>
>> On Thu, Mar 7, 2013 at 12:26 PM, H. Peter Anvin <hpa at zytor.com> wrote:
>>>
>>> It would be interesting to know what we see in the incoming cached
>>> packet at this time.  Does legacy pxelinux.0 behave the same way?
>>>
>>>          -hpa
>>
>>
>> An easy way to examine the packets as *pxelinux.0 finds them is
>> prdhcp.c32.  If you can satisfy the path for the TFTP request, you
>> could easily examine the results.
>>
> Ok, i've tested with legacy pxelinux.0 and it's the same.
> I also tested the different pre-releases, and the first version where it
happens is PRE-3.
>
> I managed to get a "working" menu. But it's not possible to boot files
from http (either with legacy and iPXE nor lwip and iPXE) legacy pxelinux.0
gives me an "not found" but doesn't even ask on TFTP or HTTP server, lwip
pxelinux.0 gives me "Boot failed: press a key to retry, or wait for
reset..." and also doesn't even ask a server.
>
> prdhcp.c32 shows me 3 Pakets from dhcp, but it's a lot of data, and i
don't want to write all the data by hand, could you specify wich
informations you need?
>

The third packet should be the most important.  The sname field/option 66,
file field/option 67, and options 209, 210 should be the only data needed.
I find mobile device (ie cell phone, tablet, media player) cameras to be
handy if you can get fair focus and lower glare (ie no flash).

If you have both sname/66 or file/67, please note both appropriately.

--Gene
On Mar 8, 2013 5:54 AM, "Tobias Göbel" <kubax1983 at gmail.com> wrote:

> Am Freitag, 08.03.2013 01:40, schrieb Gene Cumm:
>
>> On Thu, Mar 7, 2013 at 12:57 PM, Tobias Göbel <kubax1983 at gmail.com>
>> wrote:
>>
>>> Am 07.03.2013 18:24, schrieb H. Peter Anvin:
>>>
>>>  On 03/07/2013 04:51 AM, Matt Fleming wrote:
>>>>
>>>>> On Thu, 2013-03-07 at 13:32 +0100, Tobias Göbel wrote:
>>>>>
>>>>>> As you can see, everything is set to HTTP and i have no clue, why
>>>>>> pxelinux.0 tries to load it from TFTP anyways.
>>>>>>
>>>>> The lwIP PXE stack is called lpxelinux.0 in 5.10-pre1, not pxelinux.0.
>>>>> pxelinux.0 is the legacy code.
>>>>>
>>>>>  So the legacy stack does special things when it sees gPXE/iPXE
>>>> underneath it; it talks a custom protocol with iPXE to allow it to use
>>>> TCP-based protocols using the stack in iPXE.
>>>>
>>>> The lwIP-based stack shouldn't need to do that, and probably shouldn't,
>>>> but it is not well know how much problem the iPXE stack being in between
>>>> will cause.  I suspect we need to get the iPXE people involved, though.
>>>>
>>>> We should check, though, that we aren't simply using vestiges of the
>>>> custom protocol that is tripping us up.
>>>>
>>>>          -hpa
>>>>
>>> I'll try tomorrow at work, if legacy pxelinux works.
>>> But i think i'll not work, i didn't checked the logs from the TFTP server
>>> back then, but the "ldlinux.c32 not found" thingy was there, too.
>>>
>>> I'll report back tomorrow.
>>>
>>
>> On Thu, Mar 7, 2013 at 12:26 PM, H. Peter Anvin <hpa at zytor.com> wrote:
>>
>>> It would be interesting to know what we see in the incoming cached
>>> packet at this time.  Does legacy pxelinux.0 behave the same way?
>>>
>>>          -hpa
>>>
>>
>> An easy way to examine the packets as *pxelinux.0 finds them is
>> prdhcp.c32.  If you can satisfy the path for the TFTP request, you
>> could easily examine the results.
>>
>>  Ok, i've tested with legacy pxelinux.0 and it's the same.
> I also tested the different pre-releases, and the first version where it
> happens is PRE-3.
>
> I managed to get a "working" menu. But it's not possible to boot files
> from http (either with legacy and iPXE nor lwip and iPXE) legacy pxelinux.0
> gives me an "not found" but doesn't even ask on TFTP or HTTP server, lwip
> pxelinux.0 gives me "Boot failed: press a key to retry, or wait for
> reset..." and also doesn't even ask a server.
>
> prdhcp.c32 shows me 3 Pakets from dhcp, but it's a lot of data, and i
> don't want to write all the data by hand, could you specify wich
> informations you need?
>
>
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>
>
>