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   #accept a connection from any IP on port 9000 to receive settings and run

java -jar CrushFTP.jar -dmz 9000 192.168.1.10,10.0.1.5,192.168.1.11   #accept a connection from these IPs on port 9000 and run

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_dmz1.XML". The "_dmz1" is part of a specific naming scheme. This server will be identified as "dmz1". 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.