How to Configure Network Settings on a SUSE Server
How to Configure Network Settings on a SUSE Server
Managing network configuration on a SUSE server can be done in several ways, depending on your environment and level of expertise. SUSE provides flexible tools ranging from an intuitive graphical interface to powerful command-line utilities and direct configuration file editing.
On systems such as SUSE Linux Enterprise Server (SLES) and openSUSE, network configuration is typically handled using:
YaST (Yet another Setup Tool) – Recommended for most users
Command-line tools such as Wicked or NetworkManager
Manual editing of configuration files in
/etc/sysconfig/network/
This article explains each method and when to use it.
1. Using YaST (Recommended Method)
YaST provides a user-friendly, menu-driven (or graphical) interface for configuring system settings, including networking. It is the preferred method for most administrators because it reduces configuration errors and automatically manages related settings.
Steps to Configure Network with YaST
Open YaST
sudo yastNavigate to Network Settings
Go to:
System→Network Settings
Select and Edit Interface
In the Overview tab, select the interface (e.g.,
eth0)Click Edit
Configure IP Address
Choose:
Dynamic Address (DHCP), or
Statically Assigned IP Address
For static configuration, enter:
IP address
Subnet mask
Default gateway
Configure Hostname and DNS
Go to the Hostname/DNS tab
Enter hostname and DNS server addresses
Configure Routing
Use the Routing tab to define:
Default gateway
Static routes
Apply Changes
Click OK to save and apply the configuration
Why use YaST?
Guided interface
Reduces misconfiguration
Ideal for system administrators who prefer structured workflows
2. Using the Command Line Interface (CLI)
For advanced users, automation, or headless servers, command-line tools provide more granular control. The specific tool depends on the network management service in use.
A. Using Wicked (Default on SLES)
wicked is the default network management framework on SUSE Linux Enterprise Server.
View Current Configuration
Bring Interface Up or Down
Reload All Configurations
Wicked is commonly used in enterprise server environments where stable, predictable networking is required.
B. Using NetworkManager (Default on openSUSE Desktop)
NetworkManager is typically used in desktop environments like openSUSE Leap or SLED.
View Existing Connections
Configure a Static IP Address
Activate the Connection
Why use CLI tools?
Ideal for remote administration
Suitable for scripting and automation
Preferred in production server environments
3. Manual Configuration File Editing
For full control, administrators can directly edit configuration files located in:
Example: Configure eth0 with a Static IP
eth0 with a Static IPEdit the Interface File
Modify Parameters
Note: The gateway can also be defined in:
/etc/sysconfig/network/ifroute-eth0
Restart the Network Service
or:
When to use manual configuration:
Automated deployments
Advanced routing or bonding setups
Fine-tuned enterprise configurations
Choosing the Right Method
YaST
Most administrators
Beginner to Intermediate
Wicked CLI
Enterprise servers
Intermediate to Advanced
NetworkManager (nmcli)
Desktop systems
Intermediate
Manual file editing
Automation & advanced setups
Advanced
Conclusion
Network configuration on a SUSE server is flexible and adaptable to different administrative styles.
Use YaST for a guided, reliable configuration experience.
Use Wicked or NetworkManager CLI tools for scripting and remote management.
Use manual configuration files when you need precision and automation control.
Understanding all three approaches ensures you can effectively manage networking across both enterprise and community SUSE environments.
Last updated