
| -help | Show basic help text | |
| -port <n> | Connect using port <n> instead of port 21 |
| dir | directory list (full details) | |
| ls | directory list (names only) | |
| cd | change to a directory | |
| cdup | move up one directory | |
| lcd | change local directory | |
| pwd | print current working directory | |
| ascii | Set transfer type to 'ASCII' | |
| image | Set transfer type to 'image' or 'binary' | |
| get | Get a file | |
| put | Send a file | |
| mget | Get multiple files | |
| mput | Put multiple files | |
| prompt | Toggle mget/mput prompting on or off | |
| delete | Delete afile | |
| mkdir | Make directory | |
| rmdir | Remove directory | |
| rename | rename a file on the server | |
| quote | Send a command to the FTP server directly | |
| quit | Quit | |
| shell | Shell to DOS | |
| xfermode | Set default transfer mode - see section below |
The program captures Ctrl-Break and Ctrl-C. If you use Ctrl-Break
during a file transfer or directory listing the current
operation will stop (prematurely) and you will be returned to the
command line after a brief delay. If you use Ctrl-Break or
Ctrl-C at the command line the program will end.
The shell command should be used with care. With
the shell command you can do local directory listings, rename local
files, look inside of files, and do most normal things. Keep in mind
that while you are at the DOS command prompt the mTCP code
is not servicing the socket connection - if you stay in DOS too
long you might lose your connection to the FTP server.
The xfer mode command requires a little explanation.
In the beginning of time FTP servers always sent data by
doing a connect to the FTP client, which was listening for the
incoming connection on a default port. The FTP server in
NCSA telnet does this. I'll call this 'Classic' mode and you
can tell this FTP client to handle data transfers this way.
'Classic' mode is only useful for ancient FTP servers that
can't do anything else. Most modern FTP servers will not
connect to an FTP client on the default ports, and most
firewalls/routers wouldn't allow it anyway.
'Port' mode is the current default for many
clients. Instead of having the FTP server connect to the
client on default
ports, the client will tell the FTP server exactly what port it should
use for the connection. This is slightly better than
Classic mode, and should be usable on more FTP servers, firewalls and
routers.
'Passive' mode is probably the best and most compatible mode
to use with modern FTP servers. It turns things
around by making the client connect to the FTP server to make data
connections instead of having the FTP server connect to the
client. (From the standpoint of the FTP server it is
'passive' and it waits for a connection from the client.) This will
work
with almost any firewall and router. This is the mode I'd
recommend using too.
Performance depends on your hardware, but here are some rough observations:
Created January
18th, 2009, Last updated September 25th, 2009
(C)opyright Michael B.
Brutman, mbbrutman@yahoo.com