On Wed, Jun 5, 2013 at 9:58 PM, upen <upendra.gandhi at gmail.com> wrote:> I copied pxelinux.cfg/default to pxelinux.cfg/<IP to HEX> and it looks this > step resolved the earlier error. Next I get failed to load com32 file > vesamenu.c32 while that file exists in /tftplinux/linux-install.Is vesamenu.c32 from 5.10? -- -Gene
On Wed, Jun 5, 2013 at 11:18 PM, Gene Cumm <gene.cumm at gmail.com> wrote:> On Wed, Jun 5, 2013 at 9:58 PM, upen <upendra.gandhi at gmail.com> wrote: > > > I copied pxelinux.cfg/default to pxelinux.cfg/<IP to HEX> and it looks > this > > step resolved the earlier error. Next I get failed to load com32 file > > vesamenu.c32 while that file exists in /tftplinux/linux-install. > > Is vesamenu.c32 from 5.10? >Yes. I verified that vesamenu.c32 is from 5.10. ls -l /tftpboot/linux-install/vesamenu.c32 /tmp/syslinux-5.10/com32/menu/vesamenu.c32 /usr/share/syslinux/vesamenu.c32 -rwxr-xr-x 1 root root 26352 Jun 5 15:50 /tftpboot/linux-install/vesamenu.c32 -rwxrwxr-x 1 11341510 vboxsf 26352 Jun 4 14:33 /tmp/syslinux-5.10/com32/menu/vesamenu.c32 (location at source where it was compiled) -rw-r--r-- 1 root root 26352 Jun 5 15:50 /usr/share/syslinux/vesamenu.c32 (the step 'make install' installed it here) --> -Gene >-- upen, emerge -uD life (Upgrade Life with dependencies)
On Thu, Jun 6, 2013 at 7:27 AM, upen <upendra.gandhi at gmail.com> wrote:> On Wed, Jun 5, 2013 at 11:18 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Wed, Jun 5, 2013 at 9:58 PM, upen <upendra.gandhi at gmail.com> wrote: >> > I copied pxelinux.cfg/default to pxelinux.cfg/<IP to HEX> and it looks >> > this >> > step resolved the earlier error. Next I get failed to load com32 file >> > vesamenu.c32 while that file exists in /tftplinux/linux-install. >> >> Is vesamenu.c32 from 5.10? > > > Yes. I verified that vesamenu.c32 is from 5.10. > ls -l /tftpboot/linux-install/vesamenu.c32 > /tmp/syslinux-5.10/com32/menu/vesamenu.c32 /usr/share/syslinux/vesamenu.c32 > > -rwxr-xr-x 1 root root 26352 Jun 5 15:50 > /tftpboot/linux-install/vesamenu.c32 > -rwxrwxr-x 1 11341510 vboxsf 26352 Jun 4 14:33 > /tmp/syslinux-5.10/com32/menu/vesamenu.c32 (location at source where it was > compiled) > -rw-r--r-- 1 root root 26352 Jun 5 15:50 /usr/share/syslinux/vesamenu.c32 > (the step 'make install' installed it here)This is sounding like dropped/intercepted packets. Could we get some details on the client (make/model of computer/motherboard, same for NIC, PXE OROM details)? Is it connected to the same physical switch as the DHCP/TFTP server? Any chance that the physical switch that the client is connected to can perform port mirroring to see what is received? Any chance you could try manually copying pxelinux.0, lpxelinux.0, ldlinux.c32, libcom32.c32, libutil.c32, libgpl.c32 and vesamenu.c32 from a freshly extracted copy of the tar (without running make at all)? I presume using pxelinux.0 showed no errors such as this (aside from slow TFTP transfer speed)? -- -Gene
On Thu, Jun 6, 2013 at 11:58 AM, upen <upendra.gandhi at gmail.com> wrote:>> This is sounding like dropped/intercepted packets. Could we get some >> details on the client (make/model of computer/motherboard, same for >> NIC, PXE OROM details)? Is it connected to the same physical switch >> as the DHCP/TFTP server? Any chance that the physical switch that the >> client is connected to can perform port mirroring to see what is >> received? > > > DHCPD and TFTP server on Redhat 5.9 running as Virtualbox guest. > > 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) > 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] > 00:01.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) > 00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox > Graphics Adapter > 00:04.0 System peripheral: InnoTek Systemberatung GmbH VirtualBox Guest > Service > 00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08) > 00:08.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet32 > LANCE] (rev 40) <----This is the one that is connected to Internal virtual > switch on the server side. > > Client is also a Virtualbox guest. > Intel UNDI - PXE-2.1 > 1997-2000 Intel corporation > Network adapter: Intel pro/1000 T server(82543GC) > > I don't think how I can do port mirroring on this veritual switch but I am > attaching another file tcpdump o/p and screenshot of what I see.I think the RHEL guest or the host's interface to this network with its NIC in promiscuous mode would suffice.>> Any chance you could try manually copying pxelinux.0, lpxelinux.0, >> ldlinux.c32, libcom32.c32, libutil.c32, libgpl.c32 and vesamenu.c32 >> from a freshly extracted copy of the tar (without running make at >> all)? > > > I did this some time back and then did the tcpdump and the screenshot I > mentioned above and is attached here.Thanks. I'm still trying to see if there's any way to translate that to PCAP format (ie tcpdump's -w _file_ option). Using tcpdump with -A I presume?>> I presume using pxelinux.0 showed no errors such as this (aside from >> slow TFTP transfer speed)? > > > Yes that's correct. When I change my dhcpd.conf to load pxelinux.0 instead > of lpxelinux.0, all works fine except ofcourse the ISO doesn't load via http > , saying file not found which I think is expected being usage of pxelinux.0Except that you're inside iPXE so I'd expect this to work if the iPXE OROM has HTTP enabled (which is sounds like it's not).> /tftpboot/linux-install/pxelinux.cfg/C0A80058 > prompt 0 > timeout 600 > > # Set-up menu as default > DEFAULT vesamenu.c32 > PROMPT 0 > > # Menu config > MENU TITLE PXE Boot Menu > MENU BACKGROUND iit.png > > label local > localboot 0x80 > > label linux > MENU LABEL Install RHEL6 > kernel rhel6client/linux > append initrd=rhel6client/initrd.img ramdisk_size=14532 ks=nfs:NFS > server:/ks/ks-rhel6.cfg ext4 > > label ^-----freedos > MENU LABEL FreeDOS > kernel memdisk > # append initrd=msdos/FreeDOS-1.1-USB-Boot.img > append initrd=msdos/freedos > > ##THIS is MY CONCERN, loading this ISO via HTTP. > LABEL hiren > MENU LABEL HIREN > LINUX memdisk > INITRD http://192.168.0.100/hiren.iso > APPEND iso > > > Thanks for continuous help! I really appreciate it!! > > I am trying this on virtual machine to prepare for actual physical machine. > Actualy physical machines is where the loading of iso took time.Always good to test like this. -- -Gene
On Thu, Jun 6, 2013 at 3:48 PM, upen <upendra.gandhi at gmail.com> wrote:> > > > On Thu, Jun 6, 2013 at 1:01 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> On Thu, Jun 6, 2013 at 11:58 AM, upen <upendra.gandhi at gmail.com> wrote: >> >> >> This is sounding like dropped/intercepted packets. Could we get some >> >> details on the client (make/model of computer/motherboard, same for >> >> NIC, PXE OROM details)? Is it connected to the same physical switch >> >> as the DHCP/TFTP server? Any chance that the physical switch that the >> >> client is connected to can perform port mirroring to see what is >> >> received? >> > >> > >> > DHCPD and TFTP server on Redhat 5.9 running as Virtualbox guest. >> > >> > 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev >> > 02) >> > 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton >> > II] >> > 00:01.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev >> > 01) >> > 00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH >> > VirtualBox >> > Graphics Adapter >> > 00:04.0 System peripheral: InnoTek Systemberatung GmbH VirtualBox Guest >> > Service >> > 00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08) >> > 00:08.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 >> > [PCnet32 >> > LANCE] (rev 40) <----This is the one that is connected to Internal >> > virtual >> > switch on the server side. >> > >> > Client is also a Virtualbox guest. >> > Intel UNDI - PXE-2.1 >> > 1997-2000 Intel corporation >> > Network adapter: Intel pro/1000 T server(82543GC) >> > >> > I don't think how I can do port mirroring on this veritual switch but I >> > am >> > attaching another file tcpdump o/p and screenshot of what I see. >> >> I think the RHEL guest or the host's interface to this network with >> its NIC in promiscuous mode would suffice. >> >> >> Any chance you could try manually copying pxelinux.0, lpxelinux.0, >> >> ldlinux.c32, libcom32.c32, libutil.c32, libgpl.c32 and vesamenu.c32 >> >> from a freshly extracted copy of the tar (without running make at >> >> all)? >> > >> > >> > I did this some time back and then did the tcpdump and the screenshot I >> > mentioned above and is attached here. >> >> Thanks. I'm still trying to see if there's any way to translate that >> to PCAP format (ie tcpdump's -w _file_ option). Using tcpdump with -A >> I presume? > > > Me not sure either how that could be translated. > I have now attached file with packets captured running tcpdump -w filename.Supposedly text2cap could do something but not sure. Thanks. -- -Gene
Very odd! This shows a TFTP connection being correctly established and then disconnected, with all the negotiation involved. I'm wondering if it is iPXE that is playing games with us here... -hpa
On Thu, Jun 6, 2013 at 4:01 PM, H. Peter Anvin <hpa at zytor.com> wrote:> Very odd! > > This shows a TFTP connection being correctly established and then > disconnected, with all the negotiation involved. I'm wondering if it is > iPXE that is playing games with us here... > > -hpa > >Some odd things I observed just now. 1. Since yesterday, I have been reseting the client box from Virtualbox VM menu (Reset option). This always showed me com32 vesamenu.c32 message. 2. Some time ago, I decided I power off the client VM( Close->poweroff from Menu). This time I saw the menu. It didn't show the background jpg though. Anyways I chose the menu option for loading ISO. It returned me the same menu options, while showing file not found messages at the bottom of the screen. 3. I tried reset as in (1), again com32 -vesamenu.c32 message as stated earlier. 4. Power off , power on . No menu this time. Shows the com32-vesamenu.c32 message as stated earlier. No such issues with pxelinux.0 though. I am now rebooting TFTP/DHCP server and see if that helps to any level.
On Thu, Jun 6, 2013 at 5:01 PM, H. Peter Anvin <hpa at zytor.com> wrote:> Very odd! > > This shows a TFTP connection being correctly established and then > disconnected, with all the negotiation involved. I'm wondering if it is > iPXE that is playing games with us here...Packets 301-306, 309-312 show two successful attempts to read linux-install/pxelinux.cfg/C0A80058 with the same UDP source port (49153). Packets 307,308,313-316 show two unsuccessful attempts to read linux-install/pxelinux.cfg/vesamenu.c32 reusing the same UDP source port (49153) with an ICMP reply stating the port is closed. Packets 317-357 show a successful single attempt to read linux-install/pxelinux.cfg/vesamenu.c32 reusing the same UDP source port (49153). Packets 358,360-412,415-625 show a success on libcom32.c32 while 359,413,414 show an unsuccessful attempt. Something is certainly tripping up as I don't see these duplicate attempts in my testing and in my mind iPXE is in the lead. -- -Gene
On Thu, Jun 6, 2013 at 2:01 PM, Gene Cumm <gene.cumm at gmail.com> wrote:> On Thu, Jun 6, 2013 at 11:58 AM, upen <upendra.gandhi at gmail.com> wrote:>> DHCPD and TFTP server on Redhat 5.9 running as Virtualbox guest. >> >> 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) >> 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] >> 00:01.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) >> 00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox >> Graphics Adapter >> 00:04.0 System peripheral: InnoTek Systemberatung GmbH VirtualBox Guest >> Service >> 00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08) >> 00:08.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet32 >> LANCE] (rev 40) <----This is the one that is connected to Internal virtual >> switch on the server side. >> >> Client is also a Virtualbox guest. >> Intel UNDI - PXE-2.1 >> 1997-2000 Intel corporation >> Network adapter: Intel pro/1000 T server(82543GC)>> Yes that's correct. When I change my dhcpd.conf to load pxelinux.0 instead >> of lpxelinux.0, all works fine except ofcourse the ISO doesn't load via http >> , saying file not found which I think is expected being usage of pxelinux.0 > > Except that you're inside iPXE so I'd expect this to work if the iPXE > OROM has HTTP enabled (which is sounds like it's not).Rereading this thread, I must have some how crossed the two threads. There's no iPXE in this thread. -- -Gene