How to Configure Network Settings in Linux

🕐 2025-03-29 ✍️ Moyi Foreign Trade

Configuring Linux /etc/network/interfaces

Edit the /etc/network/interfaces file:

# nano /etc/network/interfaces

The default configuration file looks like this:

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

First, check your network card information:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000

3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000

Start configuring

Using DHCP for automatic configuration

If you want the interface to automatically obtain an IP address at boot, use the following configuration:

auto enp0s3
iface enp0s3 inet dhcp

This makes the enp0s3 interface automatically use DHCP to configure network settings at boot.

Static IP configuration

For static IP configuration, you need to specify the IP address, subnet mask, and gateway. For example:

auto enp0s8
iface enp0s8 inet static
    address 192.168.1.102
    netmask 255.255.255.0
    gateway 192.168.1.1
    dns-nameservers 8.8.8.8 8.8.4.4

How to Configure Network in Linux: Pre-Operation Checklist

The worst thing about technical tutorials is copying commands while ignoring environment differences. Different system versions, web servers, plugin combinations, and permission settings all affect the final result. Before you start, it is a good idea to record your current configuration and, if necessary, take a snapshot or backup. That way, even if a step goes wrong, you can roll back quickly.

Things to confirm before you start

System and software versions: Confirm the versions of Windows, Debian, Nginx, Apache, WordPress, or related tools.
Permissions: When credentials, certificates, or configuration files are involved, first confirm that your current user has sufficient permissions.
Backups: Before modifying configuration files, make a copy of the original; for WordPress sites, back up the database as well.
Testing: Verify after every change — do not wait until everything is modified to start troubleshooting.

Troubleshooting approach

When you hit an error, first figure out which layer it occurs in: browser, DNS, server, application, plugin, or permissions. Breaking the problem down is more effective than repeatedly searching for the whole error message. For issues like WordPress, Nginx, certificates, and proxies, logs are usually more reliable than the front-end page.

If the paths or menus in a tutorial do not match your environment, trust what your current system shows and locate the equivalent feature by keywords. Windows Control Panel, WordPress plugin menus, and cloud console entry points in particular often change with version updates.

Follow-up maintenance tips

Completing one fix does not mean the problem is gone forever. Keep a record of key commands, modified files, modification times, and verification results. When you later migrate servers, upgrade plugins, or change themes, these records will save you a lot of debugging time.