Opened 18 months ago
Closed 7 months ago
#1088 closed enhancement (fixed)
Use ftp/tftp-hpa instead of FreeBSD's default tftpd
| Reported by: | CsMAr51 | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 8.3.0-RELEASE |
| Component: | Backend | Version: | |
| Keywords: | Cc: |
Description
FreeBSD's default tftpd doesn't support RFC2348 and therefor can't handle files of 32MB+, use ftp/tftp-hpa instead.
I've hit this problem while trying to install an ESXi 5.0 server via PXE.
See the attached patch to replace tftpd by ftp/tftp-hpa.
I guess net/freebsd-tftp could also be used as a replacement (haven't tried it).
Attachments (1)
Change History (6)
Changed 18 months ago by CsMAr51
comment:1 Changed 18 months ago by gcooper
comment:2 Changed 18 months ago by gcooper
- Resolution set to duplicate
- Status changed from new to closed
comment:3 Changed 18 months ago by CsMAr51
Hum I should have searched the bug tracker before reporting this...
Well the RFC2348 non compliance was kind of a guess, but apparently FreeBSD's tftpd is RFC2348 compliant as stated on the man page (http://www.freebsd.org/cgi/man.cgi?query=tftpd#end). But the issue seems more related to the following bug:
Files larger than 33488896 octets (65535 blocks) cannot be transferred without client and server supporting blocksize negotiation (RFC2348).
And the fact that the PXE client doesn't seem to specify the rollover option leading to this kind of log "tftpd[3179]: Block rollover but not allowed." whereas there is no problem when downloading the file with FreeBSD's tftp client (which specifies it and where the number of rollovers is reported: "Received 154190477 bytes during 31.3 seconds in 303419 blocks with 4 rollovers").
I'll try patching tftpd with http://lists.freebsd.org/pipermail/svn-src-head/2011-July/029443.html to see if it changes something.
I'll post information on how to reproduce the problem I'm experiencing in ticket #426 comments sometimes later.
comment:4 Changed 7 months ago by william
- Milestone set to 8.3.0-RELEASE
- Resolution duplicate deleted
- Status changed from closed to reopened
FreeNAS 8.3 should fix that issue, the built-in tftpd in FreeBSD has been patched.
From FreeBSD 8.3 release notes:
A bug in the tftpd(8) daemon has been fixed. It had an interoperability issue when transferring a large file.[r227083]
comment:5 Changed 7 months ago by william
- Resolution set to fixed
- Status changed from reopened to closed

Duplicate of ticket 426. On that ticket, could you provide me with instructions on how to reproduce the issue you're seeing with tftp not being RFC2348 compliant?