Chapter 6 – RouteFinder Software
Multi-Tech Systems, Inc. RouteFinderVPN RF760/660/600VPN User Guide (PN S000323D) 80
Proxy > SOCKS Proxy
Proxy > SOCKS Proxy
SOCKS is a universal proxy supported by many client applications. SOCKS5 is an IETF (Internet Engineering Task Force)
approved standard, proxy protocol for TCP/IP-based networking applications. The basic purpose of the protocol is to enable
hosts on one side of a SOCKS server to gain access to hosts on the other side of a SOCKS Server without requiring direct
IP access. When an application client needs to connect to an application server, the client connects to a SOCKS proxy
server. The proxy server connects to the application server on behalf of the client and then relays data between client and
the application server. For the application server, the proxy server is the client.

Differences Between SOCKS and NAT:

• SOCKS allows BIND requests (listening on a port on behalf of a client; however, very few clients support this function)

• SOCKS5 allows user authentication.

• The SOCKS proxy is used for point-to-point connections.

The RouteFinder‘s SOCKS implementation supports the SOCKS v4 and the SOCKS v5 protocol versions. However,
when using SOCKS v4, User Authentication is not possible.
Socks Default Port – 1080. Almost all clients will default to this port setting, so it normally does not need to be configured.
Notes: All changes in Proxy become effective immediately without additional notice.

SOCKS Proxy

Status
To enable SOCKS, check the Status box. Click the Save button.
External Interface
The SOCKS Proxy uses an external interface to send outgoing requests. Select the interface that you want
to use. The options are LAN, WAN, and DMZ. This is the external interface to the Internet.
Internal Interface
Select one or two interfaces on which SOCKS is to accept connections from clients. The options are LAN,
WAN, and DMZ. The interfaces listed here can be used by clients with port 1080 to access the SOCKS
proxy.
User Authentication
To enable User Authentication, check the User Authentication box. If this function is enabled, SOCKS
proxy users must log in with their user names and passwords. User Authentication is available with
SOCKSv5 only. If you are using SOCKSv4, User Authentication is not available.
Authentication Types
Select the method of user authentication. Options are Local, RADIUS, and Sam. If you choose the Local
method, you can choose whether or not local users may use the SOCKS proxy.
If you disable User Authentication, then client applications must be configured with empty user name and
password fields!