FTP Listing Port Setup
This part of the document will help you in configuring the required FTP Listing port. In this example FTP protocol is used as an example.
Pre -Requisite
- An operational version 8.x virtual appliance
- Knowing the active and passive port details along with # of port instance
- For FTP(s) option, relevant private key, TLS version’s and Cipher details are available.
- Empty ftp proxy policy for port configuration.
Configuring Listining Port
Steps involved:
- Go to Task and select Manage Listing Port menu item
- Click “create” for adding new FTP listing port
- In “Basic Settings” tab, please provide name, protocol to select (in our case FTP), and the port #. In my example I am using 21111 as listing port, please refer the fig a below
- In “FTP Settings” tab, please provide passive port # along with # of passive ports.
Fig A
- For FTP command handling, for this example please select “Support extended FTP command set“ entry, please refer the fig b below for details.
Fig B
- “Advance Section” tab, refer fig c for details.
- Based on your need change the request properties section.
- In “Service Resolution” section, please select corresponding published policy, in our case empty ftp proxy policy we prepared earlier.
Fig C
Working with FTP Proxy Policy
For this example, I will be listing to FTP traffic, once it reaches the gateway, I will first enable streaming followed by SFTP to server assertion, to demonstrate the file was uploaded from local machine to gateway (/home/ssgconfig location). You may choose to use different location based on need and configure the same in this assertion. Also if you need to pass through the file to different FTP server you may leverage the disabled FTP route assertion as needed.
Fig D
- For Configuring Message Streaming, please follow fig E as shown below.
Fig E
- For SFTP to Server, I am using gateway as a file loading location, hence I am using gateway FQDN name for host name, followed by port and connect time out.
- For Command settings, I have selected “Upload To” option and message source as “request”. Please update directory settings and file name as needed. I am using seconds context variable for uniqueness on file name and /home/ssgconfig, since it has the required previllage.
- Also please provide your relevant user credential as needed in “Authentication” section. please follow the instruction as shown in the fig below.
Fig F
Working with FILEZILLA or any other FTP Client
Once the policy is saved and activated, please start your filezilla (or other FTP client), provide the required gateway host name, user id, password along with relevant port # (same as the one configured in Manage listing port section) and click “QuickConnect”.
Once connected, start uploading the files and see the traffic being routed through gateway. You can demonstrate the files being uploaded in the specific location in gateway as configured using filezilla.
Fig G
Demonstrate the file upload
Once the policy is executed, you can view the uploaded file in /home/ssgconfig location (or other location configured as per your need in SFTP to server assertion in previous section). You can demonstrate this using filezilla connecting to your gateway using ssgconfig credentials or directly logging to your gateway followed by privileged scripts (option 3) to /home/ssgconfig location.
Fig H
In my example I used a text file with “homeDepot” followed by time context variable for additional variation in file name.
Reference Materials:
Gateway v8.3 Product configuration guide: