| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
TFTP rollover option can be used to transfer larger files.
|
| |
|
|
|
|
|
| |
PR: bin/148894
Submitted by: olgeni
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
also was inappropriate as it triggered for every EACCESS and ENOTFOUND, not
just the case the -n option is intended to deal with and thus really spammed
us with ~20 messages in the default configuration when booting a diskless
FreeBSD client, introduced with r207608 again.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
setjmp to avoid warnings on the powerpc build...
|
|
|
|
| |
debugging purposes only.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
lot better than what's in the tree now. Edwin tested it at a prior
employer, but can't test it today. I've found that it works a lot
better with the various uboot versions that I've used in my embedded
work. Here's the pkg-descr from the port that describes the changes:
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.
Author: Edwin Groothuis <edwin@FreeBSD.org>
|
|
|
|
|
|
| |
Found by: make manlint
Reviewed by: ru
Approved by: philip (mentor)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Just like bin/ and sbin/, I think setting WARNS to the highest value
possible will make it more attractive for people to fix warnings.
- The WARNS variable is set in the Makefile in the directory of the
application itself, making it more likely that it will be removed out
of curiosity to see what happens.
- New applications will most likely build with WARNS=6 out of the box,
because the author would more likely fix the warnings during
development than lower WARNS.
Unfortunately almost all apps in libexec require a lowered value of
WARNS.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
unique names based on the submitted filename, a strftime(3) format
string and a two digit sequence number.
By default the strftime(3) format string is %Y%m%d (YYYYMMDD), but
this can be changed by the -F option.
PR: bin/106049 (based on patch in that PR)
Approved by: grog@ (mentor)
|
|
|
|
|
| |
PR: 106049
Submitted by: edwin (as part of a larger patch)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Don't use full path in .Nm (we just don't do that).
- Correct some frivolous and poorly rendering language,
such as using possessive case for .Nm or .Fl .
- Use the same capitalization for "user ID" as in setuid(2) and getuid(2).
- Bring SEE ALSO in accord with the text.
MFC after: 5 days
|
|
|
|
|
|
| |
PR: misc/81732
Submitted by: Denis Grudkin
MFC after: 2 weeks
|
|
|
|
|
| |
NI_WITHSCOPEID, and our getaddrinfo(3) does nothing special
for it, now.
|
|
|
|
|
| |
- No need for 'fromlen' to have file scope.
- Remove an unused variable.
|
|
|
|
|
|
| |
"Open Firmware" from IEEE 1275 and OpenFirmware.org (no pun intended).
Ok'ed by: tmm
|
| |
|
|
|
|
|
| |
requires super-user access in order to complete successfully.
Move setgroups(2) to execute before setuid(2) so that it is successful.
|
|
|
|
| |
Submitted by: Andrzej ToboĆ
a <ato@iem.pw.edu.pl>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reducing "/+./" strings to "/"
Reducing "/[^/]+/../" to "/"
o Don't send an OACK when the result of the [RW]RQ is an error.
These changes allow tftpd to interact with pxelinux.bin from the syslinux
package.
Whilst the path reducing code doesn't properly handle situations where the
path component before the "/../" is a symlink to (say) ".", I would suggest
that it does the right thing in terms of the clients perception of what
their path string actually represents. This seems better than using
realpath() and breaking environments where symlinks point outside of the
directory hierarchy that tftpd is configured to allow.
|
|
|
|
| |
- Format return () to resemble the one 5 lines up.
|
|
|
|
|
|
| |
and -U, which allows the umask to be set.
Obtained from: Patton Electronics, Co.
|
|
|
|
|
|
|
| |
in the case when client sends request with RFC2347 options.
Approved by: re
MFC After: 2 weeks
|
|
|
|
|
|
|
|
| |
does not exist.
PR: bin/38303
Submitted by: Woei-Luen, Shyu <m8535@cn.ee.ccu.edu.tw>
the committed patch differs from the submitted one, any inaccuracies are mine.
|
|
|
|
|
|
|
| |
Constness, missing prototypes, non-ansi prototypes, missing
initialisers, unnecessary declarations, shadowing.
Reviewed by: md5
|
| |
|
| |
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
| |
with a back off. This was discovered when Luigi sent me code to
handle this for Etherboot. The Etherboot patch worked okay but
FreeBSD's tftpd had trouble handling it and would fail to transfer
the file since it would abort on send and not retry.
Submitted by: luigi
MFC after: 1 week
|
|
|
|
|
|
|
| |
o Use new-style prototypes and function definitions.
o Fix timeout and justquit to have proper signatures for signal
handlers. Mark the args as __unused.
o remove register
|
|
|
|
|
|
|
|
|
|
| |
negotiation rather than rejecting the request.
Apple OpenFirmware 3.0f3 (the version in my iMac) adds trailing garbage to the
end of an otherwise valid request. Without this change, the requests were
rejected which prevented me from booting.
Reviewed by: obrien
|
|
|
|
| |
Submitted by: peter
|
|
|
|
|
|
|
|
|
|
|
| |
for negotiation of timeout and file size to the tftp protocol. This
is required by some firmware like EFI boot managers (at least on
HP i2000 Itanium servers) in order to boot an image using tftp. The
attached patch implements the RFC, and in doing so also implements
RFC2347; a generic tftp option extension.
PR: 30710
Submitted by: Espen Skoglund <esk@ira.uka.de>
|
| |
|
| |
|
| |
|
|
|
|
| |
- MAN[1-9] -> MAN.
|
| |
|
| |
|
|
|
|
|
|
|
| |
(about 31 MB - 32 MB).
Submitted (partially)
by: Pascal Hofstee <daeron@wit401305.student.utwente.nl>
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Update documentation to reflect new option. Also fix documentation
style and add missing references.
PR: 21268
Submitted by: "Aleksandr A. Babaylov" <babolo@links.ru>
Reviewed by: imp
|