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. Click
to exit the mail configuration.![]() | LDAP-Based Mail Server Configuration |
---|---|
The mail server module of SUSE Linux Enterprise Server only works if the users, groups, and the DNS and DHCP services are managed with LDAP. |
The mail server module allows configuration of SUSE Linux Enterprise Server as a mail server. YaST assists with the following steps of the configuration process:
Configures the identification of the local mail server and the maximum size of incoming or outgoing messages and the type of mail transport.
Configures the type of local mail delivery.
Configures special transport routes for mail depending on its target address.
Configures the SPAM protection settings of the mail server. This activates the tool AMaViS. Set up the type and strictness of the SPAM check.
Determines from which networks the mail server cannot be used for sending nonlocal mail.
Configures mail pick-up from external mail accounts over various protocols.
This determines for which domains the mail server should be responsible. At least one master domain must be configured if the server should not run as a null client used exclusively for sending mail without receiving any.
Distinguish among three domain types:
Main or master domain of the local mail server
All users who can receive mail in a master domain can also receive
mail in a local domain. In the case of a message within the local
domain, only the portion before the @
is
evaluated.
Only users with an explicit address within a virtual domain receive mail. Virtual mail addresses are set up in the user management module of YaST.
Many other network modules are available in YaST
.Use this to set up a custom DHCP server in only a few steps. Chapter 35, DHCP provides basic knowledge about the subject and a step-by-step description of the configuration process.
Configuring a DNS server that is responsible for name resolution is recommended for larger networks. You can use Section 34.2, “Configuration with YaST”. Chapter 34, The Domain Name System provides background information about DNS.
for this as described inUse 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.
To run your own Web server, configure Apache in Chapter 41, The Apache HTTP Server.
. Find more information in
When booting and in small networks, you can use
/etc/hosts
. For more
information, read
Section 31.6.1.6, “
/etc/hosts
”.
If you have a Kerberos server in your network for network authentication, use A detailed description of the client configuration with YaST is available in Section 47.6, “Configuring a Kerberos Client with YaST”.
.If using LDAP for user authentication in the network, configure the client in Section 37.6, “Configuring an LDAP Client with YaST”.
. Information about LDAP and a detailed description of the client configuration with YaST are available inThe LDAP server can keep various data in a central directory and distribute it to all clients in your network. Mostly it is used to store shared contact information but its function is not limited to that. An LDAP server can be used also for authentication. Information about LDAP and a detailed description of the server configuration with YaST are available in Chapter 37, LDAP—A Directory Service.
With NFS client, mount directories provided by NFS server in your own file trees. Use Chapter 39, Sharing File Systems with NFS.
to configure your system to access an NFS server in the network. A description of the YaST module and background information about NFS are provided inWith 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 39, Sharing File Systems with NFS.
, 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 inIf 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 36.2, “Configuring NIS Clients”.
If you run more than one system, local user administration (using the
files /etc/passwd
and
/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 36.1.1, “Configuring a NIS Master Server”.
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 33, Time Synchronization with NTP.
Configure the network services (such as finger, talk, and ftp) to start when SUSE Linux Enterprise 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 4.1.1, “Simple Remote Installation via VNC—Static Network Configuration”.
. 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 inAllow remote administration by selecting
in . 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. module is highly recommended for configuring VNC on your machine. Although the SaX2 interface also allows you to set remote access properties, it is not a substitute for YaST. It only enables you to configure your X server as a host for VNC sessions. For more information, refer toUse
to 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 38, Samba.
With service location protocol (SLP), you can configure clients in your network without knowledge of server names and services that these servers provide. Detailed information about SLP servers and configuration with YaST are described in Chapter 32, SLP Services in the Network.
A TFTP server in not an FTP server. While an FTP server uses the File Transfer Protocol (FTP), a TFTP server uses the much simpler Trivial File Transfer Protocol (TFTP) without security features. TFTP servers are usually used to boot diskless workstations, X terminals, and routers. Detailed information about TFTP servers and configuration with YaST are described in Section 4.3.2, “Setting Up a TFTP Server”.
WOL (wake on LAN) refers to the possibility of waking up a computer from standby mode over the network using special packages. It only works with motherboards that support this functionality in their BIOS. WOL configuration with YaST is described in Section 4.3.7, “Wake on LAN”.
In a heterogeneous network consisting of Linux and Windows hosts, Samba controls the communication between the two worlds. With the Chapter 38, Samba.
module, you can configure your computer as member of a Windows domain. Find information about Samba and the configuration of clients in