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
dmz_port.png 54.9 kB 2 25-Oct-2018 04:31 Ben Spink
png
dmz_publickey.png 13.9 kB 1 25-Oct-2018 04:31 Ben Spink
png
dmz_selector.png 30.3 kB 1 25-Oct-2018 04:31 Ben Spink
png
dmz_user.png 57.6 kB 3 25-Oct-2018 04:31 Ben Spink

This page (revision-31) was last changed on 24-Mar-2020 03:28 by Ben Spink

This page was created on 25-Oct-2018 04:31 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 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.)
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.
Version Date Modified Size Author Changes ... Change note
31 24-Mar-2020 03:28 7.887 kB Ben Spink to previous
30 26-Feb-2020 16:31 5.528 kB Halmágyi Árpád to previous | to last
29 21-Jan-2020 11:00 5.527 kB Halmágyi Árpád to previous | to last
28 21-Feb-2019 19:23 5.416 kB Ada Csaba to previous | to last
27 21-Feb-2019 19:23 5.414 kB Ada Csaba to previous | to last
26 25-Oct-2018 04:31 4.72 kB Ben Spink to previous | to last
25 25-Oct-2018 04:31 4.639 kB Ben Spink to previous | to last
24 25-Oct-2018 04:31 4.654 kB Ben Spink to previous | to last
23 25-Oct-2018 04:31 4.644 kB Ben Spink to previous | to last
22 25-Oct-2018 04:31 4.648 kB Halmágyi Árpád to previous | to last
21 25-Oct-2018 04:31 4.64 kB Ben Spink to previous | to last
« This page (revision-31) was last changed on 24-Mar-2020 03:28 by Ben Spink
G’day (anonymous guest)
CrushFTP9 | What's New
JSPWiki