search for: filerequest

...ort numbers it uses? > > -- > Matt Fleming, Intel Open Source Technology Center > Hi Matt, I think I've found the problem. In /core/fs/pxe/tftp.c in function tftp_open: First you do a core_udp_connect to port 69 (TFTP) at line 264. -> source port = x After that you sent the filerequest at line 265 You receive the fileinfo and also the used port (y) for the transfer in line 273 Than you perform a core_udp_disconnect at line 286 Now you perform a new core_udp_connect to port y which set the source port to x + 1 at line 287 for example: Client | Server TFTP get f...

...:52PM, Michael Szerencsits wrote: > Hi Matt, > > I think I've found the problem. Thanks for doing this analysis. > In /core/fs/pxe/tftp.c in function tftp_open: > First you do a core_udp_connect to port 69 (TFTP) at line 264. -> source port = x > After that you sent the filerequest at line 265 > You receive the fileinfo and also the used port (y) for the transfer in line 273 > Than you perform a core_udp_disconnect at line 286 > Now you perform a new core_udp_connect to port y which set the source port to x + 1 at line 287 > > for example: >...

Hello, I tried to boot the new syslinux.efi (32bit) from the released syslinux 6 via PXE. In a wireshark trace I can see that the syslinux.efi was loaded successfully via TFTP. Then the client try to load ldlinux.e32. I see the request and also the acknoledgement in the trace. After that the client try to load the file, but the source port is changed to tftp request port + 1. For example: