Your browser does not allow this site to store cookies and other data. Some functionality on this site may not work without them. See Privacy Policy for details on how we would use cookies.


Requirements for Transparent FTP Tunneling

Transparent FTP tunneling is completely transparent from the user's point of view, and no changes are needed in the FTP configuration. The existing FTP client and FTP server are kept running.

Transparent FTP tunneling only supports tunneling the FTP protocol, not any other applications. For tunneling of TCP-based applications, use the transparent TCP tunneling functionality, see Transparent TCP Tunneling.

The destination host must have a Secure Shell Server installed. Also note that the host key for the server must already be saved as a known host key. To save the host key, connect to the server with sshg3 and save the host key sent by the server. For instructions, see First Login to a Remote Host.

When enabling transparent FTP tunneling, consider also how the server host keys will be handled. You can choose between strict host key checking and accepting even unknown keys for the current session. For configuration instructions, see Managing Host Keys.


Consider carefully before enabling Accept unknown host keys. Disabling the host-key checks can make you vulnerable to a man-in-the-middle attack.

When a global configuration file exists, and it includes the filter-engine element, those settings are applied. On Unix, the global configuration is stored as /etc/ssh2/ssh-broker-config.xml, and on Windows as "<INSTALLDIR>\SSH Tectia Broker\ssh-broker-config.xml", where <INSTALLDIR> indicates the Tectia installation directory on Windows (see Directory Paths).