View Attach (1) Info

Add new attachment

Only authorized users are allowed to upload new attachments.

List of attachments

Kind Attachment Name Size Version Date Modified Author Change note
png
 tunnels.png 78.2 kB 3 09-Oct-2016 18:14 Ben Spink

This page (revision-5) was last changed on 09-Oct-2016 18:14 by Ben Spink

This page was created on 09-Oct-2016 18:14 by Ben Spink

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 3 changed one line
In my example I am giving the user access via VNC to a machine in the network.
The user manager [tunnels|UserManagerTunnels] configuration lets you grant access the items defined here.
At line 5 removed 2 lines
The user manager configuration lets you grant access to [tunnels] you have defined in the server prefs to be available to a user.
At line 6 added 19 lines
----
HTTP Tunnels allow for accelerated transfers. This is done by utilizing a multiplier in the HTTP tunnel. The multiplier is limited to 1 for non [enterprise|http://www.crushftp.com/enterprise.html] licenses.
As network latency increases, the maximum theoretical bandwidth of a connection goes down. This decrease is very significant. Using the HTTP tunnel multiplier, this can be overcome.
Typical maximum bandwidth from CA to NY in the USA is about 6Mbit.\\
Typical maximum bandwidth from Europe to the East coast of the USA is about 4Mbit.\\
Typical maximum bandwidth from Australia to the East coast of the USA is about 2Mbit.\\
(These speeds can vary somewhat as a fewer number of network connection hops would change the ping time for the connection.)\\
\\
In the tunnel, you just configure the multiplier needed to reach your maximum speed. So if you only get 3Mbit, and your bandwidth maximum is 50Mbit, then enter a multiplier of 17 for the max. Entering a multiplier of 20, or 30 won't hurt, but it won't benefit you either as your ISP still limits your maximum speed.
Now, any connection going through the tunnel will be sped up 17x its normal speed.
FTP, and HTTP are ideal for use inside the tunnel. The tunnel should use HTTPS from client to server to make it secure. The tunnel listens for connections on localhost on the client machine, and delivers them to localhost on the server machine. So the client can use their normal FTP client and connect to the tunnel, and not only are they secure now, but they are also accelerated.
If the client uses the WebInterface of CrushFTP, they don't need to know anything about the tunnel at all. They just do the upload using the "advanced" button and that will use a Java applet to tunnel the data to the other side. They get a nice modern WebInterface and see their upload or download go at full speed!
Version Date Modified Size Author Changes ... Change note
5 09-Oct-2016 18:14 2.673 kB Ben Spink to previous
4 09-Oct-2016 18:14 2.755 kB Ben Spink to previous | to last
3 09-Oct-2016 18:14 0.854 kB Ben Spink to previous | to last
2 09-Oct-2016 18:14 0.878 kB Ben Spink to previous | to last
1 09-Oct-2016 18:14 0.619 kB Ben Spink to last
« This page (revision-5) was last changed on 09-Oct-2016 18:14 by Ben Spink
G’day (anonymous guest)

OLD WIKI!!!#

New: CrushFTPv9#

OLD WIKI!!!#


CrushFTP8 | What's New

Referenced by
LeftMenu
UserManagerTunnels

JSPWiki