Internet Express Version 6.7 for Tru64 UNIX: Internet Express for Tru64 UNIX Administration GuideChapter 10 Proxy Services Administration
The Internet Express Administration utility lets you manage the following Proxy service components:
The Dante SOCKS Server is a circuit-level firewall/proxy server that can be used to provide convenient and secure network connectivity to a wide range of hosts. (The system on which the Dante SOCKS Server runs must have external network connectivity.) Once installed, the Dante SOCKS Server can be made transparent to clients (in most cases) and offers the server administrator detailed access control and logging facilities. SOCKS is a networking proxy protocol that enables hosts on one side of a SOCKS server to gain full access to hosts on the other side of the server, without requiring a direct IP connection. A SOCKS server redirects connection requests from hosts on opposite sides of a SOCKS server, authenticates and authorizes the requests, and establishes a proxy connection to relay data. It is commonly used as a network firewall that enables hosts behind a SOCKS server to gain full access to the Internet, while preventing unauthorized access from the Internet to the internal hosts. The Dante SOCKS Server implements the SOCKS protocol and can function as a firewall between networks. It includes an extension to the SOCKS Version 4 and Version 5 protocols that provides a more generic bind functionality, similar to functionality that non-SOCKS programs expect. It relays TCP and UDP both from outside the network and from inside the network.
The Dante SOCKS Server (/usr/local/sbin/sockd) is a daemon that runs all the time. To control the server, you first stop the running daemon, then proceed to restart the server. To stop and restart the Dante SOCKS Server from the Administration utility:
In a TruCluster environment, the Dante SOCKS Server Administration form displays all SOCKS servers that are running or stopped. When you click on Stop, all servers are stopped. Similarly, when you click on Start, all servers are started. If several servers are in a started and stopped state, clicking on Start will let the running servers continue running while restarting the stopped server. For information on controlling the Dante SOCKS Server outside the Administration utility, see the sockd(8) reference page. You configure the Dante SOCKS Server by editing the /etc/sockd.conf configuration file. This file controls both access controls and logging and is divided into two parts, server settings and rules. To use the Dante SOCKS Server, you must specify valid information in the method, client pass, and pass fields in /etc/sockd.conf. For example, to allow all users to connect without authentication, you could specify:
To allow any connections from area 16 to any other address in area 16, you could specify:
For more information, see the sockd.conf(5) reference page. The configuration file for the SOCKS client library, /etc/socks.conf, allows control over logging and server selection. It is divided into two parts, miscellaneous settings and routes. See the socks.conf(5) reference page for complete information. Documentation for the Dante SOCKS Server is available in the /usr/internet/docs/dante/ directory. Configuration file examples can be found in /usr/internet/docs/dante/example. Additional information about the Dante SOCKS Server can be found at the following Web site:
Squid is a high-performance, proxy/caching server for clients that support FTP, Gopher, and HTTP requests. Because the caching software never needs to fork (or copy) itself (except for FTP), it is faster than most proxy servers. Squid has the following features:
In Internet Express, the Squid subset consists of:
Squid is derived from the ARPA-funded Harvest project. Use the Squid Proxy/Caching Server Administration menu to perform the following tasks:
Because system needs vary, Internet Express does not install a fully configured Squid Proxy/Caching Server. You might need to edit some of the values in the Squid configuration file, /usr/internet/squid/etc/squid.conf, to meet the needs of your system. For example, you might need to edit the cache_mem and cache_swap values in squid.conf and specify the amount of RAM memory and hard disk space, respectively, to devote to caching. You can find guidelines to configure and run Squid on an Internet Express system in the /usr/internet/docs/squid directory. The documentation includes:
To reinitialize the disk cache for the Squid Proxy/Caching Server, follow these steps:
If the disk cache does not exist, the Reinitialize Disk Cache operation creates it for you. (The disk cache is automatically created when you start the Squid Proxy/Caching Server for the first time.) To manage the Squid Proxy/Caching Server from the Administration utility, follow these steps:
The Administration utility lets you control whether Squid will rotate the log files (access.log, cache.log, and store.log) once per day. When you rotate the log file s, each log file in the Squid log directory (usr/internet/squid/logs) is renamed with the appropriate .n suffix. The Rotate Logfiles option lets you specify the maximum number of rotated log files that are saved. Daily and combined status reports are generated after the log files are rotated. You can view these reports using the Display Access Statistics option (see Section : Displaying Access Statistics). To rotate log files, follow these steps:
The Administration utility lets you display a summary of proxy statistics based on data from the current logfile or from data saved when the log files were last rotated (see Section : Rotating Log Files). To display access statistics, follow these steps:
To control the Squid Proxy/Caching Server, follow these steps:
|
||||||||||||||||||||||||||||||||||||||||||||||||