| Port details |
- freebsd-tftp Upcoming replacement for tftp(1) and tftpd(8)
- 1.0 net
 =4      1.0Version of this port present on the latest quarterly branch. - There is no maintainer for this port.
- Any concerns regarding this port should be directed to the FreeBSD Ports mailing list via ports@FreeBSD.org
- Port Added: 2008-01-31 10:15:21
- Last Update: 2018-03-16 20:50:05
- SVN Revision: 464730
- People watching this port, also watch:: zip, smartmontools, tcpdump, ncftp
- License: BSD4CLAUSE
- Description:
- It all started when we got some new routers, which told me the
following when trying to upload configuration or download images
from it: The TFTP server doesn't support the blocksize option.
My curiousity was triggered, it took me some reading of RFCs and
other documentation to find out what was possible and what could
be done. Was plain TFTP very simple in its handshake, TFTP with
options was kind of messy because of its backwards capability: The
first packet returned could either be an acknowledgement of options,
or the first data packet.
Going through the source code of src/libexec/tftpd and going through
the code of src/usr.bin/tftp showed that there was a lot of duplicate
code, and the addition of options would only increase the amount
of duplicate code. After all, both the client and the server can
act as a sender and receiver.
At the end, it ended up with a nearly complete rewrite of the tftp
client and server. It has been tested against the following TFTP
clients and servers:
- Itself (yay!)
- The standard FreeBSD tftp client and server
- The Fedora Core 6 tftp client and server
- Cisco router tftp client
- Extreme Networks tftp client
It supports the following RFCs:
RFC1350 - THE TFTP PROTOCOL (REVISION 2)
RFC2347 - TFTP Option Extension
RFC2348 - TFTP Blocksize Option
RFC2349 - TFTP Timeout Interval and Transfer Size Options
RFC3617 - Uniform Resource Identifier (URI) Scheme and Applicability
Statement for the Trivial File Transfer Protocol (TFTP)
It supports the following unofficial TFTP Options as described at
http://www.compuphase.com/tftp.htm:
blksize2 - Block size restricted to powers of 2, excluding protocol headers
rollover - Block counter roll-over (roll back to zero or to one)
From the tftp program point of view the following things are changed:
- New commands: "blocksize", "blocksize2", "rollover" and "options"
- Development features: "debug" and "packetdrop"
If you try this tftp/tftpd implementation, please let me know if
it works (or doesn't work) and against which implementaion so I can
get a list of confirmed working systems.
cgit ¦ GitHub ¦ GitHub ¦ GitLab ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - Dependency lines:
-
- freebsd-tftp>0:net/freebsd-tftp
- No installation instructions:
- This port has been deleted.
- PKGNAME: there is no package for this port: NO_PACKAGE = Installs software in /usr/libexec and /usr/bin
- Flavors: there is no flavor information for this port.
- distinfo:
- SHA256 (freebsd-tftp-1.0.tar.gz) = 4d177d70e5b34c3ec1da5a0e2d5a3748d8c98dee2453674da5e4eab4f211ad63
SIZE (freebsd-tftp-1.0.tar.gz) = 29263
No package information for this port in our database- Sometimes this happens. Not all ports have packages.
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Library dependencies:
-
- libedit.so.0 : devel/libedit
- There are no ports dependent upon this port
Configuration Options:- No options to configure
- Options name:
- N/A
- USES:
- libedit
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
1.0
16 Mar 2018 20:50:05
  |
bdrewery |
Remove net/freebsd-tftp.
It was imported into base in FreeBSD 9.0 in r207608.
PR: 226610 [immutable base exp-run] |
1.0
24 Nov 2016 14:49:33
|
amdmi3 |
- Add LICENSE
- Add missing USES=libedit
- Use MANPREFIX |
1.0
16 Nov 2016 22:55:39
|
rene |
Reset edwin's ports, he has handed in his commit bit.
With hat: portmgr-secretary |
1.0
02 Mar 2015 23:36:36
|
bapt |
Remove Author from pkg-descr and white space fixes |
1.0
13 May 2014 20:57:33
|
edwin |
Fix for stagify. |
1.0
20 Sep 2013 22:10:25
|
bapt |
Add NO_STAGE all over the place in preparation for the staging support (cat:
net) |
1.0
20 Mar 2011 12:54:45
|
miwi |
- Get Rid MD5 support |
1.0
02 Feb 2008 21:48:37
|
edwin |
NOPACKAGE -> NO_PACKAGE |
1.0
31 Jan 2008 10:15:00
|
edwin |
It all started when we got some new routers, which told me the
following when trying to upload configuration or download images
from it: The TFTP server doesn't support the blocksize option.
My curiousity was triggered, it took me some reading of RFCs and
other documentation to find out what was possible and what could
be done. Was plain TFTP very simple in its handshake, TFTP with
options was kind of messy because of its backwards capability: The
first packet returned could either be an acknowledgement of options,
or the first data packet.
Going through the source code of src/libexec/tftpd and going through
the code of src/usr.bin/tftp showed that there was a lot of duplicate
code, and the addition of options would only increase the amount
of duplicate code. After all, both the client and the server can (Only the first 15 lines of the commit message are shown above  ) |
As an Amazon Associate I earn from qualifying purchases.