This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another.
IT Modernization. SAP Solutions. AI and Analytics. Hybrid Cloud Solutions. Nonstop IT. Exit Federal Government. Partner Program. Find a Partner. If the computer you are installing is part of a network which already is connected to the Internet, the only thing to do is to link your machine to the network.
If you are installing a machine that is directly connected to the Internet, the hardware and the access to the Internet Service Provider ISP needs to be set up. Please refer to the checklists below to make sure you have all the necessary data ready before starting to configure the Internet access.
When your computer is directly connected to the Internet, you first need to configure the hardware that is used for this task. This can either be an internal device such as an ISDN card or an external device for example, a modem. In most cases it is detected automatically.
Next, you need to enter the data provided by your ISP such as login credentials, gateway, or name server, for example. You should have received a data sheet from your ISP where all the necessary data is listed. Partner Program.
Find a Partner. Become a Partner. Open Source Projects. SUSE Italia. SUSE Israel. SUSE Luxembourg. SUSE Nederland. SUSE Polska. SUSE Suomi. The coexistence on one system is guaranteed where there is a dual stack implementation of both protocols. That still leaves the question of how an IPv6 enabled host should communicate with an IPv4 host and how IPv6 packets should be transported by the current networks, which are predominantly IPv4-based. The best solutions offer tunneling and compatibility addresses see Section IPv6 hosts that are more or less isolated in the worldwide IPv4 network can communicate through tunnels: IPv6 packets are encapsulated as IPv4 packets to move them across an IPv4 network.
Such a connection between two IPv4 hosts is called a tunnel. To achieve this, packets must include the IPv6 destination address or the corresponding prefix and the IPv4 address of the remote host at the receiving end of the tunnel.
A basic tunnel can be configured manually according to an agreement between the hosts' administrators. This is also called static tunneling. However, the configuration and maintenance of static tunnels is often too labor-intensive to use them for daily communication needs. Therefore, IPv6 provides for three different methods of dynamic tunneling :. IPv6 packets are automatically encapsulated as IPv4 packets and sent over an IPv4 network capable of multicasting.
This makes it possible to determine the receiving end of the IPv4 tunnel automatically. However, this method does not scale very well and is also hampered because IP multicasting is far from widespread on the Internet. Therefore, it only provides a solution for smaller corporate or institutional networks where multicasting can be enabled. The specifications for this method are laid down in RFC However, several problems have been reported regarding the communication between those isolated IPv6 hosts and the Internet.
The method is described in RFC This method relies on special servers that provide dedicated tunnels for IPv6 hosts. It is described in RFC To configure IPv6, you normally do not need to make any changes on the individual workstations. IPv6 is enabled by default. To enable it temporarily until the next reboot, enter modprobe -i ipv6 as root.
It is impossible to unload the IPv6 module after it has been loaded. Because of the autoconfiguration concept of IPv6, the network card is assigned an address in the link-local network. Normally, no routing table management takes place on a workstation.
The network routers can be queried by the workstation, using the router advertisement protocol , for what prefix and gateways should be implemented. The radvd program can be used to set up an IPv6 router.
This program informs the workstations which prefix to use for the IPv6 addresses and which routers. The above overview does not cover the topic of IPv6 comprehensively.
For a more in-depth look at the newer protocol, refer to the following online documentation and books:. In Linux, this conversion is usually carried out by a special type of software known as bind. The machine that takes care of this conversion is called a name server.
The names make up a hierarchical system in which each name component is separated by a period. The name hierarchy is, however, independent of the IP address hierarchy described above. Consider a complete name, such as jupiter. A full name, called a fully qualified domain name FQDN , consists of a host name and a domain name example. The latter also includes the top level domain or TLD com. TLD assignment has become quite confusing for historical reasons.
Traditionally, three-letter domain names are used in the USA. In the rest of the world, the two-letter ISO national codes are the standard. In addition to that, longer TLDs were introduced in that represent certain spheres of activity for example,.
This quickly proved to be impractical in the face of the rapidly growing number of computers connected to the Internet. For this reason, a decentralized database was developed to store the host names in a widely distributed manner.
This database, similar to the name server, does not have the data pertaining to all hosts in the Internet readily available, but can dispatch requests to other name servers.
The top of the hierarchy is occupied by root name servers. Each root name server knows about the name servers responsible for a given top level domain. DNS can do more than resolve host names. The name server also knows which host is receiving e-mails for an entire domain—the mail exchanger MX.
For your machine to resolve an IP address, it must know about at least one name server and its IP address. Easily specify such a name server using YaST. The protocol whois is closely related to DNS. With this program, quickly find out who is responsible for a given domain. If you already use the. For more information, see the host.
There are many supported networking types on Linux. Most of them use different device names and the configuration files are spread over several locations in the file system. For a detailed overview of the aspects of manual network configuration, see Section All network interfaces with link up with a network cable connected are automatically configured. Additional hardware can be configured any time on the installed system.
The following sections describe the network configuration for all types of network connections supported by SUSE Linux Enterprise Server.
After they have been detected, you need to manually configure the interface. For more information, see Section The Overview tab contains information about installed network interfaces and configurations. Any properly detected network card is listed with its name. You can manually configure new cards, remove or change their configuration in this dialog.
To manually configure a card that was not automatically detected, see Section To change the configuration of an already configured card, see Section The Routing tab is used for the configuration of routing.
These settings are applicable for all network interfaces. In the Network Setup Method choose the way network connections are managed.
If you want a NetworkManager desktop applet to manage connections for all interfaces, choose NetworkManager Service. NetworkManager is well suited for switching between multiple wired and wireless networks. If you do not run a desktop environment, or if your computer is a Xen server, virtual system, or provides network services such as DHCP or DNS in your network, use the Wicked Service method.
It is possible to use IPv6 together with IPv4. By default, IPv6 is enabled. However, in networks not using IPv6 protocol, response times can be faster with IPv6 protocol disabled.
If IPv6 is disabled, the kernel no longer loads the IPv6 module automatically. This setting will be applied after reboot. If left empty, it defaults to the hardware address of the network interface.
However, if you are running several virtual machines using the same network interface and, therefore, the same hardware address, specify a unique free-form identifier here. Make the option field empty for not sending any host name. The Network Card Setup dialog appears in which to adjust the card configuration using the General , Address and Hardware tabs.
Both IPv4 and IPv6 addresses are supported. If possible, the first network card with link that is available during the installation is automatically configured to use automatic address setup via DHCP.
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:. Select a card from the list of detected cards in the Overview tab of the YaST network card configuration module and click Edit. Enter the IP Address. Both IPv4 and IPv6 addresses can be used. Enter the network mask in Subnet Mask.
During activation of a network interface, wicked checks for a carrier and only applies the IP configuration when a link has been detected. 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 To configure a gateway, proceed as described in Section These so-called aliases or labels, respectively, work with IPv4 only.
With IPv6 they will be ignored. Using iproute2 network interfaces can have one or more addresses. Do not include the interface name in the alias name. It is possible to change the device name of the network card when it is used. It is also possible to determine whether the network card should be identified by udev via its hardware MAC address or via the bus ID. The latter option is preferable in large servers to simplify hotplugging of cards.
To set these options with YaST, proceed as follows:. Go to the General tab. The current device name is shown in Udev Rules. Click Change. To change the device name, check the Change Device Name option and edit the name. For some network cards, several kernel drivers may be available.
If the card is already configured, YaST allows you to select a kernel driver to be used from a list of available suitable drivers. It is also possible to specify options for the kernel driver. Select the kernel driver to be used in Module Name. If more options are used, they should be space-separated. If you use the method with wicked , you can configure your device to either start during boot, on cable connection, on card detection, manually, or never.
To change device start-up, proceed as follows:. In the General tab, select the desired entry from Device Activation. Choose At Boot Time to start the device during the system boot.
With On Cable Connection , the interface is watched for any existing physical connection. With On Hotplug , the interface is set when available. It is similar to the At Boot Time option, and only differs in that no error occurs if the interface is not present at boot time. Choose Manually to control the interface manually with ifup.
Choose Never to not start the device. The On NFSroot is similar to At Boot Time , but the interface does not shut down with the systemctl stop network command; the network service also cares about the wicked service if wicked is active.
On diskless systems where the root partition is mounted via network as an NFS share, you need to be careful when configuring the network device with which the NFS share is accessible. When shutting down or rebooting the system, the default processing order is to turn off network connections, then unmount the root partition. With NFS root, this order causes problems as the root partition cannot be cleanly unmounted as the network connection to the NFS share is already not activated.
To prevent the system from deactivating the relevant network device, open the network device configuration tab as described in Section You can set a maximum transmission unit MTU for the interface. MTU refers to the largest allowed packet size in bytes.
A higher MTU brings higher bandwidth efficiency. However, large packets can block up a slow interface for some time, increasing the lag for further packets. For more information about FCoE, see Section Without having to perform the detailed firewall setup as described in Section Proceed as follows:.
In the Overview tab, select a card from the list of detected cards and click Edit. Enter the General tab of the Network Settings dialog. Determine the Firewall Zone to which your interface should be assigned. The following options are available:. This option is available only if the firewall is disabled and the firewall does not run.
Only use this option if your machine is part of a greater network that is protected by an outer firewall. This option is available only if the firewall is enabled. The firewall is running and the interface is automatically assigned to a firewall zone. The zone which contains the keyword any or the external zone will be used for such an interface. The firewall is running, but does not enforce any rules to protect this interface. Use this option if your machine is part of a greater network that is protected by an outer firewall.
It is also useful for the interfaces connected to the internal network, when the machine has more network interfaces. A demilitarized zone is an additional line of defense in front of an internal network and the hostile Internet. Hosts assigned to this zone can be reached from the internal network and from the Internet, but cannot access the internal network.
The firewall is running on this interface and fully protects it against other—presumably hostile—network traffic. This is the default option. If a network card is not detected correctly, the card is not included in the list of detected cards. If you are sure that your system includes a driver for your card, you can configure it manually.
To configure an undetected network card or a special device proceed as follows:. In the Hardware dialog, set the Device Type of the interface from the available options and Configuration Name. If the network card is a USB device, activate the respective check box and exit this dialog with Next. Otherwise, you can define the kernel Module Name to be used for the card and its Options , if necessary. In Ethtool Options , you can set ethtool options used by ifup for the interface. For information about available options, see the ethtool manual page.
Configure any needed options, such as the IP address, device activation or firewall zone for the interface in the General , Address , and Hardware tabs. For more information about the configuration options, see Section If you selected Wireless as the device type of the interface, configure the wireless connection in the next dialog. If you did not change the network configuration during installation and the Ethernet card was already available, a host name was automatically generated for your computer and DHCP was activated.
The same applies to the name service information your host needs to integrate into a network environment. If DHCP is used for network address setup, the list of domain name servers is automatically filled with the appropriate data. If a static setup is preferred, set these values manually.
To change the name of your computer and adjust the name server search list, proceed as follows:. Enter the Hostname. Note that the host name is global and applies to all network interfaces. You should disable this behavior if you connect to different networks, because they may assign different host names and changing the host name at runtime may confuse the graphical desktop. Assign Hostname to Loopback IP associates your host name with This is a useful option if you want to have the host name resolvable at all times, even without active network.
If the Use Default Policy option is selected, the configuration is handled by the netconfig script which merges the data defined statically with YaST or in the configuration files with data obtained dynamically from the DHCP client or NetworkManager. This default policy is usually sufficient. However, this file can be edited manually. If the Custom Policy option is selected, a Custom Policy Rule string defining the merge policy should be specified.
The string consists of a comma-separated list of interface names to be considered a valid source of settings. Except for complete interface names, basic wild cards to match multiple interfaces are allowed, as well. For more information, see the man page of netconfig 8 man 8 netconfig. Enter the Name Servers and fill in the Domain Search list.
Name servers must be specified by IP addresses, such as Names specified in the Domain Search tab are domain names used for resolving host names without a specified domain.
If more than one Domain Search is used, separate domains with commas or white space. It is also possible to edit the host name using YaST from the command line. To change the host name, use the following command:. To make your machine communicate with other machines and other networks, routing information must be given to make network traffic take the correct path. If DHCP is used, this information is automatically provided.
If a static setup is used, this data must be added manually. The default gateway matches every possible destination, but if a routing table entry exists that matches the required address, this will be used instead of the default route via the Default Gateway.
More entries can be entered in the Routing Table. Select the Device through which the traffic to the defined network will be routed the minus sign stands for any device. To omit any of these values, use the minus sign -. To enter a default gateway into the table, use default in the Destination field. If more default routes are used, it is possible to specify the metric option to determine which route has a higher priority.
The route with the highest metric is used as default. If the network device is disconnected, its route will be removed and the next one will be used. YaST can be used to configure all of them. Enter the device numbers for the read, write and control channels example device number format: 0.
Then click next. In the Network Address Setup dialog, specify the IP address and netmask for the new interface and leave the network configuration by clicking Next and OK.
0コメント