| At line 3 changed one line |
| When a connection comes into the DMZ server over SFTP/FTP(es)/HTTP(s)/WebDAV(s), the DMZ server talks to the internal server on an existing connection it already has from the internal server. This communication is over a SSL socket always initiated from the internal to the DMZ. The protocol the DMZ then uses inside this secure connection is HTTP. The internal server then attaches the connection to the first HTTP (not HTTPS) port internally that it finds in its list of ports. |
| Quick video showing the steps described below: [https://youtu.be/qIe6Hyi4R9E] |
| At line 5 added 2 lines |
| When a connection comes into the DMZ server over SFTP/FTP(es)/HTTP(s)/WebDAV(s), the DMZ server talks to the internal server on an existing connection it already has from the internal server. This communication is over a SSL socket and is always initiated from the internal to the DMZ. The protocol the DMZ then uses inside this secure connection is HTTP. The internal server then attaches the connection to the first HTTP (not HTTPS) port internally that it finds in its list of ports. |
|
| At line 10 changed one line |
| java -jar CrushFTP.jar -dmz 9000 |
| /C:/real_path_to/CrushFTP9/Java/bin/java.exe" -jar CrushFTP.jar -dmz 9000 |
| At line 12 changed one line |
| java -jar CrushFTP.jar -dmz 9000,10000 |
| }}} |
| On Windows, if portable Java runtime is placed inside the CrushFTP installation folder, use |
| {{{ |
| /C:/real_path_to/CrushFTP9/Java/bin/java.exe" -jar CrushFTP.jar -dmz 9000 |
| }}} |
| To install the service , use the __-dmzi__ parameter instead |
| {{{ |
| /C:/real_path_to/CrushFTP9_PC/java/bin/java.exe" -jar CrushFTP.jar -dmzi 9000 |
| At line 23 added 3 lines |
| or |
|
| .\Java\bin\java.exe -jar CrushFTP.jar -dmzi 9000 |
| At line 28 added 12 lines |
| On Linux/UNIX will need to remove or comment the line |
| {{{ |
| $NOHUP $JAVA -Ddir=$CRUSH_DIR -Xmx1024M -jar plugins/lib/CrushFTPJarProxy.jar -d & >/dev/null 2>&1 |
| }}} |
|
| and uncomment the |
| {{{ |
| #$NOHUP $JAVA -Ddir=$CRUSH_DIR -Xmx512M -jar CrushFTP.jar -dmz 9000 & >/dev/null 2>&1 |
| }}} |
| line in the init script file __crushftp_init.sh__ then start or install normally. |
|
|
| At line 22 changed one line |
| 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 identifies what prefs.XML file to use. So the name should match that second part of the filename you made above. In this case 'dmztest'. When the port starts, it sends the prefs_dmztest.XML over the network to the DMZ server, and its kept in memory on the DMZ server. There will be outgoing port connections from the internal server to the DMZ server on the port specified. There will also be outgoing connections from the internal server to the DMZ server on the port + 1. (9001 in the example.) So those two outgoing ports must be allowed on any firewall configurations. |
| 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 identifies what prefs.XML file to use. So the name should match that second part of the filename you made above. In this case 'dmztest'. When the port starts, it sends the prefs_dmztest.XML over the network to the DMZ server, and its kept in memory on the DMZ server. There will be outgoing port connections from the internal server to the DMZ server on the port specified. |
| At line 32 changed one line |
| Create a new remote item using the third button down in the middle of the virtual file system area. Configure it exactly as shown in the screenshot. Don't change the IP or port, just leave it as the screenshot shows. Then give it full permissions with the checkboxes on the left after you save. |
| Create a new remote item using the third button down in the middle of the virtual file system area. Configure it exactly as shown in the screenshot using the username of '{username}' and password of {password}'. Don't change the IP or port, just leave it as the screenshot shows. Then give it full permissions with the checkboxes on the right after you save. |
| At line 53 changed one line |
| java -jar CrushFTP.jar -dmzi |
| java -jar CrushFTP.jar -dmzi 9000 |
| At line 55 changed one line |
| Then alter the new service\wrapper.conf file including your -d and 9000 parameters for the app. |
| Then alter the new service\wrapper.conf file and change the "plugins/lib/CrushFTPJarProxy.jar" to be "CrushFTP.jar". |
| \\ |
| ----\\ |
| (Internal details of the protocols methodologies)\\ |
| !DMZv1 protocol methodology: |
| Opens a read and write socket. Two sockets for all queue messages between servers. Initiated from internal server to DMZ. Then it opens 50 data sockets for whenever they might be needed, they are available for quick usage not needing any additional delay to request one. This would be for things like a login, dir listings, upload, download...etc. All user protocol type interactions. We only let these sockets remain unused for a maximum of 8 seconds, then we discard them to make sure a firewall hasn't possible dropped a socket and we go to use it and don't realize its been killed by the firewall. When he socket count drops below 50, we add more. So its a continuous cycle of adding and dropping sockets and discarding sockets that are used and so on. *LOTS* of new socket activity.\\ |
|
| !DMZv2 methodology |
| This protocol was discontinued. It attempted to route DMZv1 through a SSH tunnel between servers which revealed inefficiencies and bugs in SSH tunneling.\\ |
|
| !DMZv3 methodology: |
| There are 4 sockets. Read/write tunnel sockets for system type actions, and read/write tunnel sockets for data type actions. No other sockets are created. All other activity is tunneled inside of those 4 sockets between the Internal and DMZ host. the tunnel is not a reverse tunnel, so architecturally it functions the same as the way DMZv1 does. v3 has the DMZv1 protocol running inside of it, but it doesn't discard sockets since it knows it can trust the tunnel not to timeout or discard sockets. So that part of the protocol still functions the same. DMZv3 also handles disconnections on the sockets. If any of the 4 sockets get disconnected, it re-establishes the connection and resends any part of the tunneled messages that didn't make it across. So its added automatic retry and robustness to this. The dmz_tmp folder for this tunneling is due to the fact we can't stop or slow down the entire socket in the event one of the destination sockets on t he other side can't accept the data or has timed out. We instead buffer this to disk temporarily and then consume it the first moment we can. The expectation here is that the DMZ's internal communication pipe is faster than the internal or external communications that clients are doing.\\ |
