Forward all Traffic from a TCP proxy to a SOCKS Next-hop Proxy

Last updated
Save as PDF

You can forward all web traffic coming in over a TCP proxy listener port on Web Gateway to a next-hop proxy that follows the SOCKS protocol, even if this traffic is not coming in under SOCKS.

To implement the forwarding of web traffic in this way, you need to create a rule.

Import the Next-Hop Proxy rule set from the library.
Prepare the creation of a new rule in this rule set.
1. Select the imported rule set and click Unlock View to access the complete rules view.
2. Copy the rule that is contained by default in this rule set and paste the copy next to the original rule as a starting point for configuring a new rule.
3. Select the copied rule and click Edit.
Create the rule in the Edit Rule window.
1. Specify a name for the new rule, for example, Forward traffic from a TCP proxy to a SOCKS next-hop proxy.
2. Configure the following rule criteria: Proxy.Port equals 9012.
3. Leave Continue as the rule action.
4. Configure settings for the Enable Next-Hop Proxy event.
  Using these settings, the event enables a new next-hop proxy that runs under the SOCKS protocol.
  - Select the event and click Edit.
  - In the Edit Event window under Settings, click Add.
  - In the Add Settings window, specify a name for the new settings, for example, SOCKS Next-Hop.
  - Under Settings Content, select the default Internal Proxies list and click Edit.
  - In the Edit List window, click the Add icon under List Content to add a next-hop proxy.
  - In the Add Next-Hop Proxy window, configure the new next-hop proxy:
    - Identifier, for example, Lara
    - IP address and port, for example, 10.140.39.233 and 1080
    - SOCKS protocol version, for example, SOCKS v5.
      You can leave the default values for the remaining settings options.
5. Close all windows.
  The new rule appears in the Next-Hop Proxy rule set with the values that you configured.
Click Save Changes.

If any web traffic is coming in on the TCP proxy listener port, it is now forwarded to the SOCKS next-hop proxy.