1. Understanding Systemd and Network Services

What is Systemd?

Systemd is a system and service manager for Linux operating systems. It initializes the system at boot, manages running processes, and handles service lifecycle (start, stop, restart, etc.). Unlike traditional init systems, systemd is parallelized (starts services concurrently), event-driven (responds to hardware/software events), and unified (manages networks, logs, timers, and more via modular components).

What Are Network Services?

Network services are background processes (daemons) that enable network communication. Examples include:

sshd: Secure Shell service for remote access.
nginx/apache2: Web servers.
docker: Container runtime (networking components).
systemd-resolved: DNS resolver.

Systemd manages these services via units (configuration files) and provides tools to control their behavior.

2. Systemd Units: The Building Blocks

Systemd organizes resources into units, which are configuration files describing services, sockets, devices, mounts, and more. For network services, the most critical unit type is the .service unit.

Key Unit Types for Networking

Unit Type	Extension	Purpose
Service	`.service`	Defines a network service (e.g., `sshd.service`).
Socket	`.socket`	Manages network sockets (enables socket activation).
Network	`.network`	Configures network interfaces (used by `systemd-networkd`).
NetDev	`.netdev`	Defines virtual network devices (e.g., bridges, tunnels).

Anatomy of a `.service` File

A .service file has three main sections:

1. `[Unit]`: Metadata and Dependencies

Describes the service’s purpose and relationships with other units.

[Unit]  
Description=OpenSSH server daemon  
Documentation=man:sshd(8) man:sshd_config(5)  
After=network.target sshd-keygen.target  # Start AFTER these units

2. `[Service]`: Service Behavior

Defines how the service runs (executable, restart policy, etc.).

[Service]  
Type=notify  # Systemd-aware service (sends status updates)  
ExecStart=/usr/sbin/sshd -D $SSHD_OPTS  # Command to start the service  
Restart=on-failure  # Restart if it fails  
RestartSec=5s  # Wait 5s before restarting

3. `[Install]`: Installation Target

Specifies where to install the service (i.e., which target to enable it for).

[Install]  
WantedBy=multi-user.target  # Enable when system boots to multi-user mode

Example: Custom Web Service Unit

Create a simple .service file for a static web server (e.g., myweb.service):

[Unit]  
Description=Custom Static Web Server  
After=network.target  # Ensure network is up first  

[Service]  
Type=simple  
ExecStart=/usr/bin/python3 -m http.server 8080 --directory /var/www/html  
WorkingDirectory=/var/www/html  
User=www-data  
Group=www-data  
Restart=always  # Restart even if it exits successfully  

[Install]  
WantedBy=multi-user.target

Save this to /etc/systemd/system/myweb.service, then reload systemd:

sudo systemctl daemon-reload

3. Managing Network Services with `systemctl`

The systemctl command is systemd’s primary tool for managing units. Below are essential commands for network services.

Basic Service Control

Command	Purpose
`sudo systemctl start <service>`	Start a service immediately (e.g., `sudo systemctl start nginx`).
`sudo systemctl stop <service>`	Stop a running service.
`sudo systemctl restart <service>`	Stop and restart a service (e.g., after config changes).
`sudo systemctl reload <service>`	Reload configuration without stopping (if supported, e.g., `nginx reload`).

Enabling/Disabling Services (Boot Persistence)

Enable: Start the service automatically at boot.

sudo systemctl enable nginx  # Creates symlink in target directory

Disable: Prevent automatic startup.
```
sudo systemctl disable nginx  
```

Check Status:

sudo systemctl is-enabled nginx  # Output: "enabled", "disabled", or "masked"

Checking Service Status

Use systemctl status to inspect a service’s runtime state:

sudo systemctl status nginx

Example output:

● nginx.service - A high performance web server and a reverse proxy server  
     Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)  
     Active: active (running) since Tue 2024-03-12 10:00:00 UTC; 5min ago  
       Docs: man:nginx(8)  
   Main PID: 1234 (nginx)  
      Tasks: 2 (limit: 4915)  
     Memory: 3.5M  
     CGroup: /system.slice/nginx.service  
             ├─1234 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;  
             └─1235 nginx: worker process

Key details:

Active: active (running): Service is healthy.
Loaded: Path to the .service file and enable status.
Main PID: Process ID of the service.

4. Configuring Network Services with `systemd-networkd`

systemd-networkd is systemd’s built-in network manager, designed for static and dynamic network configuration. It replaces traditional tools like ifupdown and works alongside systemd-resolved (DNS) and systemd-networkctl (network status tool).

How `systemd-networkd` Works

Reads configuration from /etc/systemd/network/ and /lib/systemd/network/ (vendor defaults).
Uses .network, .netdev, and .link files to configure interfaces, virtual devices, and hardware links.
Prioritizes files lexicographically (e.g., 10-eth0.network runs before 20-wlan0.network).

Step 1: Enable `systemd-networkd`

First, ensure systemd-networkd is active:

sudo systemctl enable --now systemd-networkd  
sudo systemctl enable --now systemd-resolved  # For DNS

Step 2: Configure a Network Interface

Example 1: DHCP on Ethernet (`eth0`)

Create /etc/systemd/network/20-eth0.network:

[Match]  
Name=eth0  # Match interface named "eth0"  

[Network]  
DHCP=yes  # Use DHCP for IPv4/IPv6  
DNS=8.8.8.8 8.8.4.4  # Override DNS servers (optional)

Restart systemd-networkd to apply:

sudo systemctl restart systemd-networkd

Example 2: Static IP on Ethernet (`eth0`)

Create /etc/systemd/network/20-eth0.network:

[Match]  
Name=eth0  

[Network]  
Address=192.168.1.100/24  # Static IP/CIDR  
Gateway=192.168.1.1       # Default gateway  
DNS=1.1.1.1 1.0.0.1       # DNS servers

Example 3: Create a Bridge (for VMs/Containers)

Define the bridge device in /etc/systemd/network/10-bridge.netdev:

[NetDev]  
Name=br0  
Kind=bridge  # Type of virtual device

Configure the bridge interface in /etc/systemd/network/20-bridge.network:

[Match]  
Name=br0  

[Network]  
Address=10.0.0.1/24  
Gateway=10.0.0.254

Attach a physical interface (e.g., eth1) to the bridge in /etc/systemd/network/30-eth1.network:
```
[Match]  
Name=eth1  

[Network]  
Bridge=br0  # Attach eth1 to br0  
```

Verify Network Configuration

Use networkctl to check interface status:

networkctl status eth0  # Detailed status of eth0  
networkctl list         # List all interfaces

5. Advanced Service Management

Masking Services

To permanently disable a service (even if another unit tries to start it), use mask:

sudo systemctl mask NetworkManager  # Prevents NetworkManager from running

Unmask with sudo systemctl unmask NetworkManager.

Socket Activation

Systemd can start a service only when a network request arrives (via .socket units). This reduces resource usage for rarely used services.

Example: sshd.socket listens on port 22; when a connection arrives, it starts sshd.service.

Check socket status:

systemctl status sshd.socket

Dependency Management

Control service order with [Unit] section directives:

After=network.target: Start after network.target (network is up).
Requires=network.target: Fail if network.target is unavailable (hard dependency).
Wants=network.target: Attempt to start network.target but don’t fail if it’s missing (soft dependency).

Timers: Replace Cron with Systemd Timers

Use .timer units to schedule network tasks (e.g., restarting a service nightly).

Example: restart-nginx.timer to restart nginx at 3 AM daily:

[Unit]  
Description=Restart nginx daily  

[Timer]  
OnCalendar=*-*-* 03:00:00  # Daily at 3 AM  
Persistent=true  # Run missed jobs on boot  

[Install]  
WantedBy=timers.target

Enable and start the timer:

sudo systemctl enable --now restart-nginx.timer

6. Troubleshooting Systemd Network Services

Check Service Logs with `journalctl`

Systemd logs all service activity to the journal. Use journalctl to debug:

sudo journalctl -u nginx  # Logs for nginx.service  
sudo journalctl -u nginx -f  # "Follow" real-time logs  
sudo journalctl -u nginx --since "10min ago"  # Logs from last 10 minutes

Inspect Unit Files

View a unit file:

systemctl cat nginx.service  # Show merged config (including drop-ins)

Edit a unit (temporarily):

sudo systemctl edit nginx.service  # Creates a drop-in file in /etc/systemd/system/nginx.service.d/

Fix Common Issues

Symptom	Fix
Service fails to start	Check logs with `journalctl -u <service>`.
Network interface not up	Verify `.network` files; use `networkctl status`.
DNS resolution failing	Check `systemd-resolved` logs: `journalctl -u systemd-resolved`.
Port already in use	Find the conflicting process: `sudo ss -tulpn

7. Best Practices

Use Drop-In Files: Instead of editing original unit files (e.g., /lib/systemd/system/nginx.service), create drop-ins in /etc/systemd/system/nginx.service.d/ to avoid overwrites during package updates.
Minimize Enabled Services: Only enable critical network services (e.g., sshd, nginx) to reduce attack surface.
Test Config Changes: Use systemctl daemon-reload after editing units, and test with systemctl start <service> before enabling.
Monitor with systemd-analyze: Check boot time and service dependencies:
```
systemd-analyze blame  # Show services slowing down boot  
```

8. Conclusion

Systemd is a powerful tool for managing network services in modern Linux environments. By mastering systemctl, .service units, and systemd-networkd, you can configure, control, and troubleshoot services with precision. Remember to leverage logs (journalctl) and status tools (networkctl) to diagnose issues, and follow best practices like using drop-in files to keep configurations maintainable.

With practice, systemd will become an indispensable part of your network administration toolkit.

9. References

Systemd Official Documentation
man systemd.service (Service unit manual)
man systemd-networkd (Network configuration manual)
man journalctl (Log viewing manual)
DigitalOcean: Systemd Essentials

Managing Network Services with Systemd: A Practical Guide

Table of Contents

1. Understanding Systemd and Network Services

What is Systemd?

What Are Network Services?

2. Systemd Units: The Building Blocks

Key Unit Types for Networking

Anatomy of a `.service` File

1. `[Unit]`: Metadata and Dependencies

2. `[Service]`: Service Behavior

3. `[Install]`: Installation Target

Example: Custom Web Service Unit

3. Managing Network Services with `systemctl`

Basic Service Control

Enabling/Disabling Services (Boot Persistence)

Checking Service Status

4. Configuring Network Services with `systemd-networkd`

How `systemd-networkd` Works

Step 1: Enable `systemd-networkd`

Step 2: Configure a Network Interface

Example 1: DHCP on Ethernet (`eth0`)

Example 2: Static IP on Ethernet (`eth0`)

Example 3: Create a Bridge (for VMs/Containers)

Verify Network Configuration

5. Advanced Service Management

Masking Services

Socket Activation

Dependency Management

Timers: Replace Cron with Systemd Timers

6. Troubleshooting Systemd Network Services

Check Service Logs with `journalctl`

Inspect Unit Files

Fix Common Issues

7. Best Practices

8. Conclusion

9. References

Table of Contents

1. Understanding Systemd and Network Services

What is Systemd?

What Are Network Services?

2. Systemd Units: The Building Blocks

Key Unit Types for Networking

Anatomy of a .service File

1. [Unit]: Metadata and Dependencies

2. [Service]: Service Behavior

3. [Install]: Installation Target

Example: Custom Web Service Unit

3. Managing Network Services with systemctl

Basic Service Control

Enabling/Disabling Services (Boot Persistence)

Checking Service Status

4. Configuring Network Services with systemd-networkd

How systemd-networkd Works

Step 1: Enable systemd-networkd

Step 2: Configure a Network Interface

Example 1: DHCP on Ethernet (eth0)

Example 2: Static IP on Ethernet (eth0)

Example 3: Create a Bridge (for VMs/Containers)

Verify Network Configuration

5. Advanced Service Management

Masking Services

Socket Activation

Dependency Management

Timers: Replace Cron with Systemd Timers

6. Troubleshooting Systemd Network Services

Check Service Logs with journalctl

Inspect Unit Files

Fix Common Issues

7. Best Practices

8. Conclusion

9. References

Anatomy of a `.service` File

1. `[Unit]`: Metadata and Dependencies

2. `[Service]`: Service Behavior

3. `[Install]`: Installation Target

3. Managing Network Services with `systemctl`

4. Configuring Network Services with `systemd-networkd`

How `systemd-networkd` Works

Step 1: Enable `systemd-networkd`

Example 1: DHCP on Ethernet (`eth0`)

Example 2: Static IP on Ethernet (`eth0`)

Check Service Logs with `journalctl`