User manual NOVELL LINUX ENTERPRISE SERVER 11 ADMINISTRATION

[. . . ] SUSE Linux Enterprise Server 11 March 23, 2009 www. novell. com Administration Guide Administration Guide All content is copyright © 2006- 2009 Novell, Inc. Legal Notice This manual is protected under Novell intellectual property rights. By reproducing, duplicating or distributing this manual you explicitly agree to conform to the terms and conditions of this license agreement. This manual may be freely reproduced, duplicated and distributed either as such or as part of a bundled package in electronic and/or printed format, provided however that the following conditions are fulfilled: That this copyright notice and the names of authors and contributors appear clearly and distinctively on all reproduced, duplicated and distributed copies. [. . . ] Both IPv4 and IPv6 addresses are supported. The network card can have No IP Address (which is useful for bonding devices), a Statically Assigned IP Address (IPv4 or IPv6) or a Dynamic Address assigned via DHCP and/or Zeroconf. If using Dynamic Address, select whether to use DHCP Version 4 Only (for IPv4), DHCP Version 6 Only (for IPv6) or DHCP Both Version 4 and 6. Basic Networking 219 If possible, the first network card with link that is available during the installation is automatically configured to use automatic address setup via DHCP. On SUSE Linux Enterprise Desktop, where NetworkManager is active by default, all network cards are configured. NOTE: IBM System z and DHCP On IBM System z platforms, DHCP-based address configuration is only supported with network cards that have a MAC address. This is only the case with OSA and OSA Express cards. DHCP should also be used if you are using a DSL line but with no static IP assigned by the ISP (Internet Service Provider). If you decide to use DHCP, configure the details in DHCP Client Options in the Global Options tab of the Network Settings dialog of the YaST network card configuration module. Specify whether the DHCP client should ask the server to always broadcast its responses in Request Broadcast Response. This option may be needed if your machine is a mobile client moving between networks. If you have a virtual host setup where different hosts communicate through the same interface, an DHCP Client Identifier is necessary to distinguish them. DHCP is a good choice for client configuration but it is not ideal for server configuration. To set a static IP address, proceed as follows: 1 Select a card from the list of detected cards in the Overview tab of the YaST network card configuration module and click Edit. 2 In the Address tab, choose Statically Assigned IP Address. Both IPv4 and IPv6 addresses can be used. If the IPv6 address is used, use Subnet Mask for prefix length in format /64. Optionally, you can enter a fully qualified Hostname for this address, which will be written to the /etc/hosts configuration file. 5 To activate the configuration, click OK. 220 Administration Guide If you use the static address, the name servers and default gateway are not configured automatically. To configure name servers, proceed as described in Section "Configuring Hostname and DNS" (page 225). To configure a gateway, proceed as described in Section "Configuring Routing" (page 227). Configuring Aliases One network device can have multiple IP addresses, called aliases. To set an alias for your network card, proceed as follows: 1 Select a card from the list of detected cards in the Overview tab of the YaST network card configuration module and click Edit. 2 In the Address > Additional Addresses tab, click Add. [. . . ] First, two ACLs are defined, then http_access options use these ACLs to grant access from the CGI script to Squid. The first ACL is the most important, because the cache manager tries to communicate with Squid over the cache_object protocol. acl manager proto cache_object acl localhost src 127. 0. 0. 1/255. 255. 255. 255 434 Administration Guide The following rules give Apache the access rights to Squid: http_access allow manager localhost http_access deny manager These rules assume that the Web server and Squid are running on the same machine. If the communication between the cache manager and Squid originates at the Web server on another computer, include an extra ACL as in Example 29. 2, "Access Rules" (page 435). Example 29. 2 Access Rules acl manager proto cache_object acl localhost src 127. 0. 0. 1/255. 255. 255. 255 acl webserver src 192. 168. 1. 7/255. 255. 255. 255 # webserver IP Then add the rules in Example 29. 3, "Access Rules" (page 435) to permit access from the Web server. [. . . ]