search for: sles113

...test]# tcpdump -i bond0 port 69 -vv tcpdump: listening on bond0, link-type EN10MB (Ethernet), capture size 65535 bytes 12:19:58.575731 IP (tos 0x0, ttl 63, id 34438, offset 0, flags [none], proto UDP (17), length 78) 10.16.233.15.winpoplanmess > 10.16.195.178.tftp: [udp sum ok] 50 RRQ "sles113/syslinux.efi" octet tsize 0 blksize 1468 12:19:58.582689 IP (tos 0x0, ttl 63, id 34441, offset 0, flags [none], proto UDP (17), length 70) 10.16.233.15.c1222-acse > 10.16.195.178.tftp: [udp sum ok] 42 RRQ "sles113/syslinux.efi" octet blksize 1468 12:20:00.729468 IP (tos 0x0,...

Hum... Some packets seems duplicated when captured from the server, but not when captured from the mirror port. So let's assume that's ok. I can't find anything in the capture of the non-modified version that would look suspicious. Anyway, syslinux.efi is supposed to be downloaded by the UEFI firmware itself. It succeed but keep restarting for no apparent reason. Maybe an early

...vin: > Thank you for posting the pcap files, by the way. Analyzing them in > Wireshark is so much nicer than reading the text output of tcpdump. Fetch the new capture with wget -O pcap2.zip http://ge.tt/api/1/files/136167y/0/blob?downlad The capture[1] shows two[2] TFTP transmissions of sles113/syslinux.efi, but nothing after that. As if syslinux.efi was crashed. Groeten Geert Stappers Notes [1] With a snaplength of 96 bytes or something. Add -S0 to tcpdump to get the full network packets. [2] A previous posting says that the repeated transmission is an artifact of the firmware...

...dified sendto but not send. The TFTP request is > sent using "sendto" while the acknowledgement are sent using "send". > Thus you need to patch both. That makes sense. My observation is also that the transmit works, but the recieve fails. At packet 90 starts TFTP of file sles113/syslinux.efi, which is succesfull. At packet 327 is the file sles113/syslinux.efi a second time transmitted. For reason unclear to me. At packet 564 starts 10.16.233.20 asking for sles113/ldlinux.e64. 10.168.195.178 answers, but client re-acts as if it didn't get that answer. > I think yo...

...FTP request is > > sent using "sendto" while the acknowledgement are sent using "send". > > Thus you need to patch both. > > That makes sense. > My observation is also that the transmit works, but the recieve fails. > > At packet 90 starts TFTP of file sles113/syslinux.efi, which is succesfull. > > At packet 327 is the file sles113/syslinux.efi a second time transmitted. > For reason unclear to me. > > At packet 564 starts 10.16.233.20 asking for sles113/ldlinux.e64. > 10.168.195.178 answers, but client re-acts as if it didn't get t...

...yzing them in > >> Wireshark is so much nicer than reading the text output of tcpdump. > > > > Fetch the new capture with > > > > wget -O pcap2.zip http://ge.tt/api/1/files/136167y/0/blob?downlad > > > > The capture[1] shows two TFTP transmissions of sles113/syslinux.efi, > > but nothing after that. As if syslinux.efi was crashed. > > > > [1] With a snaplength of 96 bytes or something. > > Add -S0 to tcpdump to get the full network packets. > > syslinux.efi either crashed or just can't get packets out. Either of...

...p files, by the way. Analyzing them in >> Wireshark is so much nicer than reading the text output of tcpdump. > > Fetch the new capture with > > wget -O pcap2.zip http://ge.tt/api/1/files/136167y/0/blob?downlad > > > The capture[1] shows two[2] TFTP transmissions of sles113/syslinux.efi, > but nothing after that. As if syslinux.efi was crashed. > > Groeten > Geert Stappers > > Notes > [1] With a snaplength of 96 bytes or something. > Add -S0 to tcpdump to get the full network packets. > [2] A previous posting says that the repeated tra...

...Wireshark is so much nicer than reading the text output of tcpdump. > > > > > > Fetch the new capture with > > > > > > wget -O pcap2.zip http://ge.tt/api/1/files/136167y/0/blob?downlad > > > > > > The capture[1] shows two TFTP transmissions of sles113/syslinux.efi, > > > but nothing after that. As if syslinux.efi was crashed. > > > > > > [1] With a snaplength of 96 bytes or something. > > > Add -S0 to tcpdump to get the full network packets. > > > > syslinux.efi either crashed or just can't...

...ing them in >>> Wireshark is so much nicer than reading the text output of tcpdump. >> >> Fetch the new capture with >> >> wget -O pcap2.zip http://ge.tt/api/1/files/136167y/0/blob?downlad >> >> >> The capture[1] shows two[2] TFTP transmissions of sles113/syslinux.efi, >> but nothing after that. As if syslinux.efi was crashed. >> >> Groeten >> Geert Stappers >> >> Notes >> [1] With a snaplength of 96 bytes or something. >> Add -S0 to tcpdump to get the full network packets. >> [2] A previous...