This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

CrushFTP can operate in a restricted environment where a front end DMZ server processes protocols and connections, and a secured internal server has access to the file system, database, or other protected resources.

1.) To start a DMZ instance waiting for its configuration from the internal server:

java -jar CrushFTP.jar -dmz 9000

java -jar CrushFTP.jar -dmz 9000 192.168.1.10,10.0.1.5,192.168.1.11

If you specify acceptable IPs, and the IP isn't int he list, the connection is dropped, and a message logged.

2.) Now that the server is configured, you need to configure prefs for this server. Its usually easiest to start with your existing prefs on your internal server and adjust it later on.

So duplicate prefs.XML and call it "prefs_dmztest.XML". The "_dmz1" is part of a specific naming scheme. This server will be identified as "dmztest". So if you wanted another name such as 'extra' you would do "prefs_extra.XML".

3.) Now that the prefs are ready, lets configure the port in CrushFTP that will attach to the DMZ instance and handles things.

Create a new port item, set its protocol to be DMZ:// and configure the IP and port for the DMZ server where the core will be connecting out to the DMZ. The IP is the IP of the DMZ server and the port is the port you used above when you started it. The 'name' field that would normally be optional is required here as that is how it identified what prefs.XML file to use. So the name should match that second part of the filename you made above. In this case 'dmztest'.

4.) Now when you go back to the Server Admin tab, you will notice a new drop down selector to the right of the tabs allowing you to control the instance you are managing.