imgfetch stuck mid-download

[Geth]

(2016-06-03 16:35)mcb30 Wrote:  What is the exact iPXE script that you are using to load WinPE?

The most recent one (I've read that font files are redundant long since):

Code:

imgfetch --name Boot.wim Boot.amd64.wim Boot.wim
imgfetch --name BCD BCD BCD
imgfetch --name Boot.sdi Boot.sdi Boot.sdi
chain wimboot gui

(2016-06-03 16:35)mcb30 Wrote:  What are the symptoms? Do you see TCP retransmissions showing up in a packet capture? Does "ifstat" report packets being received? On the server side, does "arp -n" show an entry for iPXE's IP address? Are you still able to ping iPXE from the server?

I haven't got any time to test all this (and therefore I don't expect any advancement), also I switched to undionly.kpxe and memtest.0, so I don't experience this anymore.

While I was still there, I've tried to put 5sec timeout on .wim fetch, and monitor ifstat before and after it failed (or not). I've realized that error packet counter growing steadily between trials. In the meantime I've pinged constantly from the server: the almost zero ping went up during the not-so-fast download (which may or may not timed out later) to an almost constant 1000ms.

After I've scratched that concept blaming my buggy BIOS/NIC/etc, and switched to undionly, checking ifstat before/after (successful) fetch: 0 error packets, but of course that was expected.
Anyway I'm using undionly.kpxe now, after a little slower init, it's fast and reliable.