At line 1 changed one line |
The CrushTunnel process can be integrated into an existing workflow using a standalone machine acting as the tunnel provider, or programmatically through your own code. |
!Start a Single Tunnel |
At line 3 changed one line |
Here is a stand alone example: |
The CrushTunnel process can be integrated into an existing workflow using a standalone machine acting as the tunnel provider, or programmatically through your own code. CrushTunnel.jar can be found in the CrushFTP WebInterface folder. |
At line 5 added 2 lines |
Here is a stand alone example (one long line): |
|
At line 6 changed one line |
java -Dcrushtunnel.pasv.ip=71.123.244.10 -Dcrushtunnel.pasv.port.start=2000 -Dcrushtunnel.pasv.port.stop=2100 -Djava.awt.headless=true -cp CrushTunnel.jar com.crushftp.tunnel.AutoChannelProxy protocol=https host=www.crushftp.com port=443 username=demo password=demo localport=2121 |
java -cp CrushTunnel.jar com.crushftp.tunnel2.Tunnel2 protocol=https host=www.crushftp.com port=443 username=demo password=demo |
At line 11 changed one line |
The tunnel adds some overhead to the transaction, so its suited best for large transfers where it can accelerate them avoiding latency issues. Small files do not benefit from the tunnel other than being inside the encrypted network. |
---- |
!Start a Tunnel in Code |
To programmatically start the tunnel, include the CrushTunnel.jar file, and do something similar to the following: |
At line 13 changed one line |
To programmatically start the tunnel, include the CrushTunnel.jar file. |
{{{ |
com.crushtunnel.gui.Common.trustEverything(); //ignore SSL validation issues…bad for prod use |
com.crushftp.tunnel2.Tunnel2 t = new com.crushftp.tunnel2.Tunnel2("https://www.crushftp.com:443/", "demo", "demo", false); |
t.startThreads(); |
//tunnel is now open and ready. Connections to it over FTP on 127.0.0.1 will be proxied securely through the tunnel to the CrushFTP FTP server side. |
|
//to stop it later on |
t.stopThisTunnel(); |
}}} |
|
---- |
!Install as a Service on Windows for an Always on Tunnel |
|
Run CrushTunnel.jar in command line client mode.\\ |
{{{ |
java -jar CrushTunnel.jar |
}}} |
|
Now issue the service tunnel command to install as a service. The parameters are: protocol host port user pass. Example:\\ |
{{{ |
service tunnel https www.CrushFTP.com 443 demo demo |
}}} |
|
Your done, type "quit" to exit the CrushClient command line. |
---- |
__Command Line JNLP Launch__\\ |
You could also launch a specific tunnel from the command line using Java WebStart. |
|
{{{ |
<?xml version="1.0" encoding="UTF-8"?> |
<jnlp spec="1.0+" codebase="https://www.crushftp.com"> |
<information> |
<title>CrushTunnel</title> |
<vendor>Ben Spink</vendor> |
<offline-allowed/> |
<shortcut online="true"> |
<desktop/> |
</shortcut> |
</information> |
<security><all-permissions/></security> |
<resources> |
<j2se version="1.2+" /><jar href="/WebInterface/CrushTunnel.jar"/> |
</resources> |
<application-desc main-class="com.crushftp.tunnel2.Tunnel2"> |
<argument>protocol=https</argument> |
<argument>host=www.crushftp.com</argument> |
<argument>port=443</argument> |
<argument>username=demo</argument> |
<argument>password=demo</argument> |
</application-desc> |
</jnlp> |
|
|
}}} |