Hi, I'm trying to boot 64bit version of syslinux.efi through network. But booting is freezes with following message: Getting cached packets My IP is X.X.X.X the last file that was requested through tftp is syslinux.efi. I'm using precompiled binary from official syslinux-6.02.tar.gz. Here is the dump in ASCII - http://brom.in/dumps/syslinux-20131220.txt Any help is appreciated.
Op 2013-12-20 om 12:05 schreef Roman:> Hi, > > I'm trying to boot 64bit version of syslinux.efi through network. But > booting is freezes with following message: > Getting cached packets > My IP is X.X.X.XThat is a very strange IPv4 address ...> the last file that was requested through tftp is syslinux.efi. > I'm using precompiled binary from official syslinux-6.02.tar.gz. > > Here is the dump in ASCII - http://brom.in/dumps/syslinux-20131220.txt01:48:53.357724 IP (tos 0x0, ttl 62, id 25667, offset 0, flags [none], proto UDP (17), length 61) 192.168.1.1.1971 > 10.0.0.1.69: [udp sum ok] 33 RRQ "bootx64.efi" octet blksize 1468 01:48:53.358430 IP (tos 0x0, ttl 64, id 62406, offset 0, flags [none], proto UDP (17), length 43, bad cksum 0 (->c26e)!) 10.0.0.1.22448 > 192.168.1.1.1971: [udp sum ok] UDP, length 15 01:48:53.358756 IP (tos 0x0, ttl 62, id 25668, offset 0, flags [none], proto UDP (17), length 32) 192.168.1.1.1971 > 10.0.0.1.22448: [udp sum ok] UDP, length 4 01:48:53.358835 IP (tos 0x0, ttl 64, id 47893, offset 0, flags [none], proto UDP (17), length 1500, bad cksum 0 (->f56e)!) 10.0.0.1.22448 > 192.168.1.1.1971: [udp sum ok] UDP, length 1472 The preferred file format for tcpdumps is "pcap". Create them with the -w option.> > Any help is appreciated.As I see it, is it related to TFTP-across-a-router-problem from a few weeks ago. Groeten Geert Stappers -- Leven en laten leven
Hello, On Sat, Dec 21, 2013 at 6:07 PM, Geert Stappers <stappers at stappers.nl>wrote:> Op 2013-12-20 om 12:05 schreef Roman: > > Hi, > > > > I'm trying to boot 64bit version of syslinux.efi through network. But > > booting is freezes with following message: > > Getting cached packets > > My IP is X.X.X.X > > That is a very strange IPv4 address ... > > > this is just a "pattern", may be 192.168.1.1 or may be 192.168.2.100.Doesn't matter.> the last file that was requested through tftp is syslinux.efi. > > I'm using precompiled binary from official syslinux-6.02.tar.gz. > > > > Here is the dump in ASCII - http://brom.in/dumps/syslinux-20131220.txt > > 01:48:53.357724 IP (tos 0x0, ttl 62, id 25667, offset 0, flags [none], > proto UDP (17), length 61) > 192.168.1.1.1971 > 10.0.0.1.69: [udp sum ok] 33 RRQ "bootx64.efi" > octet blksize 1468 > 01:48:53.358430 IP (tos 0x0, ttl 64, id 62406, offset 0, flags [none], > proto UDP (17), length 43, bad cksum 0 (->c26e)!) > 10.0.0.1.22448 > 192.168.1.1.1971: [udp sum ok] UDP, length 15 > 01:48:53.358756 IP (tos 0x0, ttl 62, id 25668, offset 0, flags [none], > proto UDP (17), length 32) > 192.168.1.1.1971 > 10.0.0.1.22448: [udp sum ok] UDP, length 4 > 01:48:53.358835 IP (tos 0x0, ttl 64, id 47893, offset 0, flags [none], > proto UDP (17), length 1500, bad cksum 0 (->f56e)!) > 10.0.0.1.22448 > 192.168.1.1.1971: [udp sum ok] UDP, length 1472 > > > The preferred file format for tcpdumps is "pcap". > > Create them with the -w option. > > > > > Any help is appreciated. > > As I see it, > is it related to TFTP-across-a-router-problem from a few weeks ago. > > > as far as I understand "native" solution is not present at the currenttime?
On 12/20/2013 2:05 AM, Roman wrote:> Hi, > > I'm trying to boot 64bit version of syslinux.efi through network. But > booting is freezes with following message: > Getting cached packets > My IP is X.X.X.X > > the last file that was requested through tftp is syslinux.efi. > I'm using precompiled binary from official syslinux-6.02.tar.gz. > > Here is the dump in ASCII - http://brom.in/dumps/syslinux-20131220.txt > > Any help is appreciated.I am experiencing something similar to this. I don't have a tcpdump file available. I can however share a copy of my tftpd log from the server. When I didn't have ldlinux.e64 available: Dec 27 16:40:42 scrappy in.tftpd[55787]: RRQ from 192.168.1.133 filename syslinux.efi Dec 27 16:40:42 scrappy in.tftpd[55787]: tftp: client does not accept options Dec 27 16:40:43 scrappy in.tftpd[55788]: RRQ from 192.168.1.133 filename syslinux.efi Dec 27 16:40:43 scrappy in.tftpd[55789]: RRQ from 192.168.1.133 filename ldlinux.e64 Dec 27 16:40:43 scrappy in.tftpd[55790]: RRQ from 192.168.1.133 filename /ldlinux.e64 Dec 27 16:40:43 scrappy in.tftpd[55791]: RRQ from 192.168.1.133 filename /boot/isolinux/ldlinux.e64 Dec 27 16:40:43 scrappy in.tftpd[55792]: RRQ from 192.168.1.133 filename /isolinux/ldlinux.e64 Dec 27 16:40:43 scrappy in.tftpd[55793]: RRQ from 192.168.1.133 filename /boot/syslinux/ldlinux.e64 Dec 27 16:40:43 scrappy in.tftpd[55794]: RRQ from 192.168.1.133 filename /syslinux/ldlinux.e64 Dec 27 16:40:43 scrappy in.tftpd[55795]: RRQ from 192.168.1.133 filename /ldlinux.e64 Machine reboots at this point With ldlinux.e64 put in root of server: Dec 27 16:44:58 scrappy in.tftpd[55824]: RRQ from 192.168.1.133 filename syslinux.efi Dec 27 16:44:58 scrappy in.tftpd[55824]: tftp: client does not accept options Dec 27 16:44:58 scrappy in.tftpd[55825]: RRQ from 192.168.1.133 filename syslinux.efi Dec 27 16:44:58 scrappy in.tftpd[55826]: RRQ from 192.168.1.133 filename ldlinux.e64 Machine is hard locked with the same output as the originator. hard reset is the only thing effective Machine is custom, with MSI CSM-H61M-P32/W8 mainboard with onboard Realtek 8111E. I am using syslinux.efi / ldlinux.e64 from the syslinux-6.02.zip I will see if I can get some more time early next week to poke more at this. For giggles, I tried a copy of snponly.efi from iPXE which fails while configuring the NIC Error: 040ee106 This specific hardware is known to work with the dhcpd (isc) /tftpd (hpa) server loading either memtest5.efi (beta) or WinPE bootmgfw.efi. It also works in bios mode with pxelinux 3.86 flawlessly. dhcpd host entry: host s_lan_20 { hardware ethernet d4:3d:7e:df:b2:19; filename "syslinux.efi"; option tftp-server-name "192.168.1.12"; } -Andrew