Zarządzanie interfejsami sieciowymi

Think of your computer's network interface as its "ID card" for communicating on a network. It's the hardware or software component that allows your device to connect to a network, whether wired (Ethernet) or wireless (Wi-Fi).

Every network interaction, like browsing a website or sending an email, goes through one of these interfaces.

The first step in managing interfaces is knowing which ones you have! The ip command is your primary tool in modern Linux systems. Use ip link show to list all network interfaces.

You'll often see interfaces like lo (loopback), eth0 (Ethernet), or wlan0 (Wi-Fi).

Let's break down the ip link show output:

• lo: The loopback interface, used for internal communication.
• eth0: A common name for the first Ethernet adapter.
• UP: Indicates the interface is active.
• mtu: Maximum Transmission Unit, the largest packet size it can handle.
• link/ether: Shows the MAC address, a unique hardware identifier.

You can enable or disable network interfaces. Disabling an interface effectively takes it offline, preventing any network traffic through it. This is useful for troubleshooting or security.

Use ip link set dev [interface_name] up to enable and down to disable.

While ip link show gives you physical layer info, you need ip addr show (or ip a for short) to see IP addresses assigned to interfaces. This command reveals Layer 3 (Network Layer) details.

An IP address allows your device to be located and communicate with other devices on a network.

You can assign an IP address to an interface on the fly using ip addr add. This change is temporary and will be lost upon reboot or network service restart.

The format is ip addr add [IP_address]/[CIDR_prefix] dev [interface_name].

Just as you can add an IP address, you can also remove it. This is useful if you've made a mistake or need to reconfigure an interface's addressing.

Use ip addr del [IP_address]/[CIDR_prefix] dev [interface_name] to remove an address.

The ip commands we've used so far apply changes immediately, but these changes are not persistent. This means they will be lost when the system reboots or the network service restarts.

For a stable network setup, you need to save your configurations in specific files or through a network management service.

Linux distributions typically use configuration files to store network settings persistently. The exact location and format can vary, but common approaches include:

• Debian/Ubuntu: /etc/network/interfaces
• CentOS/RHEL: Files in /etc/sysconfig/network-scripts/
• Modern systems: NetworkManager or Netplan configurations (e.g., .yaml files in /etc/netplan/)

These files are read at boot time or when network services are restarted.

You've learned how to inspect and temporarily modify network interfaces using the ip command. Let's test your understanding.

In this lesson, you learned how to manage Linux network interfaces using the powerful ip command. We covered:

• Listing interfaces with ip link show.
• Activating/deactivating interfaces with ip link set.
• Viewing and assigning temporary IP addresses with ip addr.
• The importance of persistent configuration files for permanent changes.

Mastering these commands is crucial for any Linux network administrator or developer!