r-tftpd is a tftp server with RFC 7440 "windowsize" support and it can relay tftp requests to http servers.
It allows RRQ (read) requests; WRQ support is incomplete and
exists only for testing purposes.
-
RRQ: yesWRQ: only for testing purposes; e.g. accepts only the data but does not store it. No window size support either- implements only the "octet" ("binary") transfer mode; "netascii" and "mail" are not supported
- block ids will wrap around from 65535 to 0
-
RFC 2347 "TFTP Option Extension":
- can be disabled (for testing purposes) by the
--no-rfc2347flag
- can be disabled (for testing purposes) by the
-
RFC 7440 "TFTP Windowsize Option"
- only for
RRQ, but not forWRQ
- only for
Usage: r-tftpd [OPTIONS]
Options:
-s, --systemd use systemd fd propagation
-p, --port <PORT> port to listen on [default: 69]
-l, --listen <IP> ip address to listen on [default: ::]
-m, --max-connections <NUM> maximum number of connections [default: 64]
-t, --timeout <TIMEOUT> timeout in seconds during tftp transfers [default: 3]
-f, --fallback <URI> fallback uri
-L, --log-format <FMT> log format [default: default] [possible values: default, compact, full, json]
-C, --cache-dir <DIR> directory used for cache files
--no-rfc2347 disable RFC 2347 (OACK) support; only useful for testing some clients
--wrq-devnull accept WRQ but throw it away; only useful for testing some clients
--disable-proxy disable proxy support
-h, --help Print help information
-V, --version Print version information
make
cargo buildor
cargo install r-tftpdsee r-tftp.spec for ways how to customize it by using makefile variables.
cd /var/lib/tftpboot && r-tftpd --port 1234Listening on privileged ports (e.g. the standard 69 one) requires the
CAP_NET_BIND_SERVICE capability (see man 7 capabilities).
see contrib/
"r-tftpd" supports relaying of tftp requests to other servers. It allows pseudo virtual hosting by creating (dead) symlinks pointing to an url.
http://+https://
Schemes accept the following, "plus" sign separated modifiers:
-
nocache: downloaded resources will not be cached; by default usual http caching mechanisms (Cache-Control,Etag, ...) are applied and resources are kept locally. They are not accessible on disk but created byO_TMPFILE.The cache is cleared periodically
-
nocompress: resources are requested withidentityencoding; by default, compression is enabled. When compression is enabled, the whole file must be downloaded when starting the transaction because its size can not be determined else.
Without compression, Content-Length information are used and tftp
upload and http download happen in parallel, This helps to avoid
tftp timeouts
$ tree
.
├── domain1 -> http+nocache://domain1.example.org/
├── domain2 -> http+nocompress://domain2.example.org/
├── existing
├── remote-file -> http+nocompress+nocache://domain3.example.org/some-file
└── subdir
└── file
$ r-tftp --fallback http://fallback.example.org/
| requested path | returned resource | flags |
|---|---|---|
existing |
local existing file |
|
subdir/file |
local subdir/file |
|
domain1/foo |
remote http://domain1.example.org/foo |
without caching |
domain2/bar |
remote http://domain2.example.org/bar |
without http compression |
remote-file |
remote http://fallback.example.org/remote-file |
without http compression nor caching |
not-here |
remote http://fallback.example.org/not-here |
GPL-3.0 or later