Configuring a chain of SOCKS proxies when you have an environment with upstream Proxy.

To configure a chain of SOCKS proxies you will need to define the upstream proxy as a SOCKS gateway and then forward to it using policy.

CLI command to create a SOCKS gateway:

#(config socks-gateways) create gateway
gateway_alias gateway_host SOCKS_port [group=group_name] [version={4 | 5 [user=username {password=password | encrypted-password=encrypted_password}]

e.g. 

ProxyA#(config socks-gateways) create DMZ_SOCKS_Proxy x.x.x.x 1080 (replace x.x.x.x with the DMZ Proxy IP address)

#(config socks-gateways) failure-mode {open | closed}
Sets the default failure mode (that can be overridden by policy).

Then using VPM, add a Forwarding Rule to send all SOCKS traffic to the SOCKS gateway. To be more specific about which particular traffic you would like forwarded to this gateway you will need to define specific source, destination, or service type triggers.

SOCKS client ---> ProxyA (Internal proxy) ---> ProxyB (DMZ proxy) ---> WWW (Server)

For more information about using the SOCKS gateway, please refer to to the Configuration and Management Guide (CMG) for the version of SGOS that you are running. 

Reference to CLI commands and Reference to UI