Implement and troubleshoot SOCKS

Products

• ProxySG Software - SGOS
• ISG Proxy

Issue/Introduction

SOCKS servers provide application-level firewall protection for an enterprise. Use SOCKS gateways to forward traffic.

The ProxySG implementation of SOCKS includes:

• A SOCKS proxy server that supports both SOCKSv4/4a and SOCKSv5, running on the ProxySG appliance.

• Support for forwarding through SOCKS gateways.

Ref. doc.: About SOCKS Gateways

Environment

Release: SG/ASG/ISG-Proxy

Resolution

Please refer to the Tech. Article with the URL below, for the recommended implementation guidance, to intercept SOCKs traffic on ProxySG.

How To Intercept SOCKS Traffic and Use The ProxySG as a SOCKS Proxy

Concerning the customer's request for guidance on how to implement the policy for SOCKS traffic, please refer to the steps below.

• SOCKS Authentication: Determines the method of authentication for accessing the proxy through SOCKS. Create a SOCKS authentication layer, to implement this.

To enable SOCKS debug log, please refer to the Tech. Article with the URL below, for guidance.

How to enable socks debug log

There are also a number of other SOCKS related statistics that you can check, depending on your implementation. Please see the snippet below, for guidance.

Importantly, with SOCKS correctly implemented on the Proxy, the customer would always have turn on PCAP and policy trace, and with the issue reproduced, to troubleshoot any access-related challenge. For SOCKS Protocol filter reference, please refer to the non-Broadcom resource with the URL below.

WireShark_URL_SOCKS

With the PCAP/Policy trace alongside the SOCKS debug log and the Gateway stats, from the Proxy, the customer should be able to see what the challenge is, with the traffic. 

Should further technical intervention be required, please, Technical Support will require that you share the snippets for the implementation done as well as the diagnostic data shared in this update, with the updated sysinfo file and the entire eventlog.