#754 closed defect (fixed)
PXE:Tftp Empty File Request
| Reported by: | bombela | Owned by: | michaln |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 1.5.0 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
When VirtualBox (1.5.0) send request to tftp serveur, the first request send the filename. If the first request abort, the second request will not send the filename ! The tftp server respond : error.
I have compared with Toshiba Laptop (Satellite pro 4600). The laprop send correctly the name at the second (or more) request.
I send a network snif in a file.
VirtualBox Network sniff :
- VirtualBox : 192.168.0.67
- TftpServer : 192.168.0.12
Tothiba Networdk sniff :
- Toshiba : 192.168.0.57
- TftpServer : 192.168.0.12
Compare each packet N°6 of Toshiba VirtalBox, in Toshiba sniff, you can see the filename but for the VirtualBox snif the filename is empty.
(And sorry for my bad english)
Attachments (1)
Change History (7)
by , 17 years ago
| Attachment: | toshiba_and_virtualbox.txt added |
|---|
comment:1 by , 17 years ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
comment:2 by , 17 years ago
Could you please provide a full-frame packet trace in pcap format? Many tools can create that format (wireshark, ethereal, tcpdump - but with tcpdump make sure you specify -s 1500 to capture all data). Please include the DHCP part, as that may be the cause of all the trouble.
comment:3 by , 17 years ago
In less than 24h, i will make more packet trac.
I make juste the software i have tested :
I have tested with tftp serveur :
- FAIL atfpd
- FAIL tftd-hpa
- FAIL DnsMasq integrated tftpd - http://www.thekelleys.org.uk/dnsmasq/doc.html
- SUCC Windows 2003 - WDS/RIS
- SUCC SystemRescueCd - (use tftp-hpa) - http://www.sysresccd.org
With this list you can see : tftp-hpa with SystemRescueCD is ok, but with my own config : no.
I will make many other test for check the configration diff. Not only in tftp serveur, but also in dhcp configuration. I suppose it's also very important.
Best regards,
comment:4 by , 17 years ago
Yes, please make sure to include a complete DHCP packet trace. I have a strong suspicion that the DHCP packets are causing the problem (and it's not really caused by anything in TFTP). Is it possible that when PXE boot failed, there were multiple DHCP servers on your network? Perhaps your regular DHCP server plus a DHCP server built into the PXE server product?
comment:5 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Actually, it looks like we won't need the packet trace. We got a trace from another customer, which allowed me to find and fix the problem. FYI, it would happen when a DHCP server sent option 67 (bootfile name) but not option 60 (PXEClient). That's why it showed up with some servers but not others. The fix will be in the next VBox release.
Should you still have trouble, please reopen this bug (with additional details).
Could you please tell me what exactly your PXE server software is? I already know about this problem but unfortunately the packet trace isn't sufficient to fix it. I'm sure I could fix this if I could reproduce the problem, but it appears to be specific only to some PXE server setups.