Access rules of the TFTP server. The server runs while at least one rule exists (the dynamic tftpd entry on UDP port 69 in /ip/service). Each request is checked against the rules in order, and the first rule that matches the client address and the requested file name decides; a request that no rule matches is refused with permission denied!. See TFTP.
| Argument | Type | Description |
|---|
| ip-addresses | object { ip-addresses: alt { ip6: ip6Prefix
, ip: ipRange
}
} | Client addresses the rule applies to: IPv4 addresses, ranges or prefixes, or IPv6 prefixes. Empty (default) means any client. |
| req-filename | string | Requested file name as a regular expression; empty (default) matches any name. Case-sensitive. A value that does not start with ^ must match the whole name (phone\.cfg matches only phone.cfg, .*\.cfg every .cfg name); the anchors are added around the whole value, so write alternatives in a group, (aaa|bbb)\.bin. A value that starts with ^ is used as written. The name is the one the client requests, not the path on the router. In a rule that serves a folder or the requested name, a pattern such as .*, or an empty value, also matches names that lead out of the folder: use a pattern such as [^/.][^/]* that allows no slash and no leading dot. |
| real-filename | string | What the rule serves. Empty (default) serves the requested name itself; a file serves that file for every matching request; a folder is put in front of the requested name (real-filename=tftp answers a request for phone.cfg or /phone.cfg with tftp/phone.cfg). Uploads are written to the same place. The value is used literally: references such as \1 to parts of req-filename are not supported. |
| allow | bool | yes serves matching requests, no refuses them with permission denied!. Default: yes. |
| read-only | bool | With yes, an upload fails with illegal operation. Set no to accept uploads. Default: yes. |
| allow-rollover | bool | Allow transfers of more than 65535 blocks: after block 65535 the router continues with block 0, which the client must support. Without it, such a transfer fails at the limit with illegal operation. Default: no. |
| allow-overwrite | bool | With read-only=no, allow an upload to replace an existing file. Without it, the upload fails with file exists. Default: no. |
| reading-window-size | alt { window-size: enum (none | pipelining) { none:0 }
} |
none (default) - Send each block of a download after the previous one is acknowledged.pipelining - Send several blocks of a download before waiting for acknowledgements, which speeds up downloads. |