File Tunnel v2.3.0

New features

• Tunnel through FTP servers. Instructions are here
• Added a new mode (--upload-download). In this mode, the program will write to a file then wait for it to be deleted by the counterpart (signaling it was processed). This is slower than the regular mode, but uses more standard file operations which may better suit some file systems.

Other improvements

• If the TCP connection is unsuccessful, the initiating connection is now closed.

File Tunnel v2.2.4

Addressed issue #34 when tunneling through RDP (Win client, xrdp server). Thanks @rmnhg!

Added --verbose to print more detailed output.

Experimental builds

exp

Add isolated reading

File Tunnel v2.2.3

Bug fix

• A Linux Virtual Machine using VirtualBox Shared Folder (vboxsf) for the shared files would not establish a file tunnel. Addressed by periodically reading the first 4KB of the file, which forces the associated files streams to realise the file content has changed.

File Tunnel v2.2.2

UDP Improvements

• Added remote UDP forwarding. For example --remote-udp-fwd 8000:10.0.0.50:6000 instructs the remote side to listen on port 8000, and forward data through the tunnel and onto 10.0.0.50:6000 via the local machine.
• Allow multiple UDP listeners on the same endpoint, for example: -U 5000:192.168.1.100:7000 -U 5000:192.168.1.200:8000

File Tunnel v2.2.1

Bug fixes

• Now uses unique Connection IDs, to avoid connections being closed incorrectly when tunnel is bidirectional.
• Address 100% CPU usage on macOS. Thanks @kim0

v2.2.0 with preallocated file support

The purpose of this build is to see if File Tunnel can work with preallocated files, as is being discussed here: #18

File Tunnel v2.2.0

New syntax

The program now uses a new syntax to create the tunnel, which will look familiar to those who tunnel over SSH.

For example:

On your computer, run:
ft.exe -L 5000:192.168.1.50:8888 --write "\\server\share\1.dat" --read "\\server\share\2.dat"

And on the remote computer, run:
ft.exe --read "\\server\share\1.dat" --write "\\server\share\2.dat"

The above commands get the program to listen locally on port 5000, and when it receives a connection it will pass it through the tunnel and onto 192.168.1.50:8888.

Thank you @YourSandwich for suggesting supporting multiple ports.

File Tunnel v2.1.0

New feature

The file tunnel is now more resilient. It is restored automatically after the file server comes back online.

File Tunnel v2.0.2

Minor update

• Bugfix: Some threads were not being closed when a connection was finished. This could lead to high CPU usage when hundreds of connections were closed.