This group contains tools to configure all kinds of services in the network. These include name resolution, user authentication, and file services.
You can configure your mail settings in+ if you send your e-mail with sendmail, postfix, or the SMTP server of your provider. You can fetch mail via the fetchmail program, for which you can also enter the details of the POP3 or IMAP server of your provider. Alternatively, use a mail program of your choice, such as KMail or Evolution, to set your access data. In this case, you do not need this module.
To configure your mail with YaST, specify the type of your connection to the Internet in the first dialog. Choose one of the following options:
Select this option if you have a dedicated line to the Internet. Your machine is online permanently, so no dial-up is required. If your system is part of a local network with a central e-mail server, select this option to ensure permanent access to your e-mail messages.
This item is relevant for users who have a computer at home, are not located in a network, and occasionally connect to the Internet.
If you do not have access to the Internet and are not located in a network, you cannot send or receive e-mail.
Activate virus scanning for your incoming and outgoing e-mail with AMaViS by selecting that option. The package is installed automatically as soon as you activate the mail filtering feature. In the following dialogs, specify the outgoing mail server (usually the SMTP server of your provider) and the parameters for incoming mail. Set the diverse POP or IMAP servers for mail reception by various users. Using this dialog, you can also assign aliases, use masquerading, or set up virtual domains. Clickto exit the mail configuration.
Many other network modules are available in YaST.
Configuring a DNS server that is responsible for name resolution is recommended for larger networks. You can use Section 20.2, “Configuration with YaST” (↑Reference). Chapter 20, The Domain Name System (↑Reference) provides background information about DNS.for this as described in
Use this module to configure the hostname and DNS if these settings were not already made while configuring the network devices. Also use it to change the hostname and domain name. If the provider has been configured correctly for DSL, modem, or ISDN access, the list of name servers contains the entries that were extracted automatically from the provider data. If you are located in a local network, you might receive your hostname via DHCP, in which case you should not modify the name.
If you have a Kerberos server in your network for network authentication, use.
With NFS, run a file server that all members of your network can access. This file server can be used to make certain applications, files, and storage space available to users. In Chapter 22, Sharing File Systems with NFS (↑Reference)., you can configure your host as an NFS server and determine the directories to export for general use by the network users. All users with the appropriate permissions can mount these directories in their own file trees. A description of the YaST module and background information about NFS are provided in
If you run NIS server to administer user data on a central place and distribute it to the clients, configure the client here. Detailed information about NIS client and configuration with YaST is available in Section 21.2, “Configuring NIS Clients” (↑Reference).
If you run more than one system, local user administration
(using the files
/etc/shadow) is impractical and requires a
lot of maintenance. In this case, administer user data on a
central server and distribute it to the clients from there. NIS
is one option for this. Detailed information about NIS and its
configuration with YaST is available in Section 21.1.1, “Configuring a NIS Master Server” (↑Reference).
NTP (network time protocol) is a protocol for synchronizing hardware clocks over a network. Information about NTP and instructions for configuring it with YaST are available in Chapter 24, Time Synchronization with NTP (↑Reference).
Configure the network services (such as finger, talk, and ftp) to start when SUSE Linux boots using. These services enable external hosts to connect to your computer. Various parameters can be configured for every service. By default, the master service that manages the individual services (inetd or xinetd) is not started.
When this module starts, choose whether to start inetd or xinetd. The selected daemon can be started with a standard selection of services. Alternatively, compose your own selection of services with, , and .
|Configuring Network Services (xinetd)|
The composition and adjustment of network services on a system is a complex procedure that requires a comprehensive understanding of the concept of Linux services. The default settings are usually sufficient.
Configure Internet proxy client settings in. Click then enter the desired proxy settings. You can test these settings by clicking . A small window informs you whether your proxy settings work correctly. After your settings have been entered and tested, save them by clicking .
To administer your machine remotely from another machine, use Section 1.1.1, “Simple Remote Installation via VNC—Static Network Configuration” (↑Reference).. To maintain your system remotely, use a VNC client, such as krdc, or a Java-enabled browser. Although remote administration using VNC is simple and fast, it is less secure than using SSH, so you should always keep this in mind when using a VNC server. Find detailed information about installing with a VNC client in
Allow remote administration by selectingin . Selecting disables this function. Click to allow access to your computer. Clicking displays network interfaces with open ports in the firewall. Select the desired interface and click to return to the main dialog. Click to complete the configuration.
Useto configure the paths data takes over the network. In most cases, only enter the IP address of the system through which to send all data in . To create more complicated configurations, use .
In a heterogeneous network consisting of Linux and Windows hosts, Samba controls the communication between the two worlds. Information about Samba and the configuration of servers is provided in Chapter 28, Samba (↑Reference).