Chapter 3 – RouteFinder Software Operation
Multi-Tech RouteFinder RF650VPN User Guide
119
SOCKS
From Proxies|SOCKS you can configure the SOCKS5 proxy service. SOCKS is a universal proxy
that is supported by many client applications. Some examples are instant messaging clients such as ICQ
or AIM, FTP clients and RealAudio. SOCKS can act as a proxy when establishing FTP connections for
clients, and SOCKS can also accept incoming connections with the TPC or UDP protocol (listening). This
makes SOCKS useful on firewalls that use NAT, as SOCKS can
compensate for the disadvantages of NAT. The differences between SOCKS and NAT are that SOCKS
also allows BIND requests (listening on a port on behalf of a client - but only very few clients support this
function) and that SOCKS5 allows user authentication. The SOCKS proxy is used for point-to-point
connections.
The RouteFinder's SOCKS implementation supports the SOCKSv4 ant the SOCKSv4 protocol versions.
However, when using the SOCKSv4 protocol, no user authentication is possible.
The default port for SOCKS is 1080. Almost all clients will default to this port setting, so it normally does
not need to be configured.
Note: All changes in Proxies becomes effective immediately without additional notice.
Note: If SOCKS5 clients that do not resolve DNS names themselves are being used, the proxy service
SOCKS
requires a valid name server. SOCKS4 clients always resolve DNS names themselves.
Configure SOCKS Proxy
1. Open the
SOCKS
menu in the
Proxies
directory.
2. Click the
Enable
button next to
Status
; the
SOCKS
proxy is enabled.
3. Configure the
SOCKS proxy
via the entry and select menus:
External Interface
: Select the interface which the SOCKS proxy is to use to send outgoing
requests (select
LAN
,
WAN
, or
DMZ
). Normally, this is the external interface to the Internet.
Internal Interface(s)
: Select the interfaces on which the SOCKS proxy is to accept connections
from clients (select
LAN
,
WAN
, and/or
DMZ
). The interfaces listed here can be used by clients with port
1080 to access the
SOCKS
proxy.
User authentication: if this function is enabled, SOCKS proxy users must log in with their user name
and password. As this function only works with SOCKSv5, the protocol version SOCKSv4 is not
available if User authentication is enabled.
Authentication types: here you select the method of user authentication (local, radius, or sam). If
you choose the local method, you can determine whether local users may use the SOCKS proxy.