Mastering Network Configuration with CLI

Table of Contents

1. Understanding CLI: Basics and Advantages
2. Essential CLI Commands for Network Configuration
   • Linux Networking CLI
   • Windows Networking CLI
   • Cisco IOS CLI for Network Devices
3. Advanced Network Configuration with CLI
   • Automation with Scripts
   • Network Namespaces and VLANs
4. Troubleshooting Network Issues with CLI
5. Best Practices for CLI Network Configuration
6. Tools to Enhance CLI Productivity
7. Conclusion
8. References

Understanding CLI: Basics and Advantages

What is CLI?

The Command-Line Interface (CLI) is a text-based interface that allows users to interact with a system or device by typing commands. Unlike GUIs, which rely on menus and mouse clicks, CLI requires precise command syntax. While this may seem intimidating at first, CLI offers granular control over system behavior—making it ideal for network configuration.

Why CLI for Network Configuration?

• Speed and Efficiency: CLI commands execute instantly, and repetitive tasks can be automated with scripts (e.g., configuring 100 routers with a single script).
• Remote Access: CLI works seamlessly over SSH/Telnet, enabling management of remote devices without GUI tools.
• Precision: Avoids GUI “click fatigue” and reduces human error by enforcing exact syntax.
• Resource Efficiency: CLI uses minimal system resources, critical for low-powered devices (e.g., edge routers).
• Scripting and Automation: Integrates with tools like Bash, PowerShell, or Ansible to automate complex workflows (e.g., VLAN provisioning, firewall rule updates).

Common CLI Environments for Networking

• Linux: Bash/Zsh shell (uses ip, nmcli, netplan).
• Windows: Command Prompt (CMD) and PowerShell (uses netsh, ipconfig, Get-NetIPAddress).
• Network Devices: Proprietary CLIs (e.g., Cisco IOS, Juniper Junos, Arista EOS).

Essential CLI Commands for Network Configuration

Linux Networking CLI

Linux is the backbone of servers and network devices, and its CLI tools are powerful yet standardized. Below are key commands for configuring Linux networks.

1. ip Command (Replaces ifconfig)

The ip command is the modern replacement for ifconfig (deprecated in most Linux distributions). It manages interfaces, IP addresses, routes, and more.

Examples:

• View all interfaces and IPs:

  $ ip addr show  
  # Output snippet:  
  2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000  
      link/ether 00:15:5d:01:23:45 brd ff:ff:ff:ff:ff:ff  
      inet 192.168.1.10/24 brd 192.168.1.255 scope global eth0  
         valid_lft forever preferred_lft forever  

  Here, eth0 has an IP 192.168.1.10/24 (subnet mask 255.255.255.0).

• Assign a static IP to an interface:

  $ sudo ip addr add 10.0.0.5/24 dev eth0  

  (Replace 10.0.0.5/24 with your IP/CIDR and eth0 with your interface.)

• Remove an IP address:

  $ sudo ip addr del 10.0.0.5/24 dev eth0  

• View routing table:

  $ ip route show  
  # Output snippet:  
  default via 192.168.1.1 dev eth0 proto dhcp src 192.168.1.10 metric 100  
  192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.10 metric 100  

2. nmcli (NetworkManager CLI)

nmcli interacts with NetworkManager, the default network management tool in most Linux desktops and servers. It simplifies managing connections (e.g., Wi-Fi, Ethernet, VPN).

Examples:

• View active connections:

  $ nmcli connection show --active  
  NAME    UUID                                  TYPE      DEVICE  
  eth0    5b4d-...-a3f2                        ethernet  eth0  

• Set a static IP for eth0:

  $ sudo nmcli connection modify eth0 \  
    ipv4.addresses 10.0.0.5/24 \  
    ipv4.gateway 10.0.0.1 \  
    ipv4.dns "8.8.8.8,8.8.4.4" \  
    ipv4.method manual  
  $ sudo nmcli connection up eth0  # Apply changes  

3. netplan (Ubuntu/Debian-Specific)

netplan uses YAML files to configure networks (replaces /etc/network/interfaces). Edit the YAML file, then apply with netplan apply.

Example YAML config (/etc/netplan/01-netcfg.yaml):

network:  
  version: 2  
  renderer: networkd  
  ethernets:  
    eth0:  
      addresses: [10.0.0.5/24]  
      gateway4: 10.0.0.1  
      nameservers:  
        addresses: [8.8.8.8, 8.8.4.4]  

Apply with:

$ sudo netplan apply  

Windows Networking CLI

Windows offers both legacy (CMD) and modern (PowerShell) tools for network configuration. PowerShell is preferred for advanced tasks due to its scripting capabilities.

1. PowerShell Commands

PowerShell uses cmdlets (e.g., Get-NetIPAddress, New-NetIPAddress) for network management.

Examples:

• View IP configuration:

  PS> Get-NetIPAddress -AddressFamily IPv4  

• Set a static IP for Ethernet:

  PS> New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress "192.168.1.20" -PrefixLength 24 -DefaultGateway "192.168.1.1"  
  PS> Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses ("8.8.8.8", "8.8.4.4")  

2. netsh (Legacy but Still Useful)

netsh (network shell) is a command-line scripting utility for Windows network configuration.

Example: Set static IP with netsh:

C:\> netsh interface ip set address "Ethernet" static 192.168.1.20 255.255.255.0 192.168.1.1  
C:\> netsh interface ip set dns "Ethernet" static 8.8.8.8  

Cisco IOS CLI for Network Devices

Cisco IOS (Internetwork Operating System) is used on routers, switches, and firewalls. Its CLI has modes (e.g., User EXEC, Privileged EXEC, Global Configuration) to enforce access control.

Key Modes in Cisco IOS

• User EXEC Mode (>): Basic monitoring (e.g., ping, show commands). Access with telnet/ssh and credentials.
• Privileged EXEC Mode (#): Advanced monitoring and configuration. Enter with enable and enable password.
• Global Configuration Mode ((config)#): Modify system-wide settings. Enter with configure terminal from Privileged EXEC.
• Interface Configuration Mode ((config-if)#): Configure specific interfaces (e.g., GigabitEthernet0/1).

Essential Cisco IOS Commands

• View Interface Status:

  Router> enable  
  Router# show ip interface brief  
  Interface              IP-Address      OK? Method Status                Protocol  
  GigabitEthernet0/0     192.168.1.1     YES manual up                    up  
  GigabitEthernet0/1     unassigned      YES unset  down                  down  

• Configure an Interface with Static IP:

  Router# configure terminal  
  Router(config)# interface GigabitEthernet0/0  
  Router(config-if)# ip address 192.168.1.1 255.255.255.0  
  Router(config-if)# no shutdown  # Enable the interface  
  Router(config-if)# exit  
  Router(config)# exit  
  Router# write memory  # Save config to flash (persists after reboot)  

• Set Default Gateway (Router):

  Router(config)# ip route 0.0.0.0 0.0.0.0 203.0.113.1  # Route all traffic to 203.0.113.1  

Advanced Network Configuration with CLI

Automation with Scripts

CLI shines when combined with scripting. Below are examples of automating network tasks.

Bash Script for Linux IP Configuration

A script to set a static IP, gateway, and DNS on multiple Linux servers:

#!/bin/bash  
# Set static IP for eth0  
INTERFACE="eth0"  
IP="10.0.0.10/24"  
GATEWAY="10.0.0.1"  
DNS="8.8.8.8,8.8.4.4"  

sudo ip addr add $IP dev $INTERFACE  
sudo ip route add default via $GATEWAY dev $INTERFACE  
echo "nameserver $DNS" | sudo tee /etc/resolv.conf > /dev/null  
echo "Configured $INTERFACE with IP $IP"  

Ansible for Network Device Automation

Ansible uses YAML playbooks to automate configuration across multiple devices (Cisco, Juniper, Arista).

Example Ansible Playbook to Configure Cisco Interfaces:

- name: Configure Cisco Interfaces  
  hosts: cisco_routers  
  gather_facts: no  
  tasks:  
    - name: Set IP on GigabitEthernet0/0  
      ios_config:  
        lines:  
          - ip address 192.168.1.1 255.255.255.0  
          - no shutdown  
        parents: interface GigabitEthernet0/0  
    - name: Save config  
      ios_command:  
        commands: write memory  

Network Namespaces and VLANs

• Linux Network Namespaces: Isolate network stacks (e.g., simulate multiple networks on a single host).

  $ sudo ip netns add ns1  # Create namespace  
  $ sudo ip link add veth0 type veth peer name veth1  # Create virtual Ethernet pair  
  $ sudo ip link set veth1 netns ns1  # Assign veth1 to ns1  
  $ sudo ip addr add 10.0.0.1/24 dev veth0  # Assign IP to host side  
  $ sudo ip netns exec ns1 ip addr add 10.0.0.2/24 dev veth1  # Assign IP to namespace side  

• VLAN Configuration (Cisco IOS): Create and assign VLANs to interfaces.

  Switch(config)# vlan 10  
  Switch(config-vlan)# name SALES  
  Switch(config-vlan)# exit  
  Switch(config)# interface GigabitEthernet0/1  
  Switch(config-if)# switchport mode access  
  Switch(config-if)# switchport access vlan 10  
  Switch(config-if)# no shutdown  

Troubleshooting Network Issues with CLI

CLI is invaluable for diagnosing network problems. Below are key tools and commands.

1. ping and traceroute

• ping: Test connectivity to a host (ICMP echo request).

  $ ping google.com -c 4  # Send 4 packets  
  64 bytes from 142.250.185.14: icmp_seq=1 ttl=118 time=12.3 ms  

• traceroute: Trace the path packets take to a destination (identifies hops with latency).

  $ traceroute google.com  
  1  router.local (192.168.1.1)  1.234 ms  
  2  10.0.0.1 (10.0.0.1)  5.678 ms  
  3  203.0.113.1 (203.0.113.1)  10.123 ms  

2. mtr (Combines ping and traceroute)

mtr provides real-time latency and packet loss data for each hop.

$ mtr google.com  

3. ss (Replaces netstat)

ss displays active network connections, ports, and sockets.

$ ss -tuln  # Show TCP/UDP listeners  
State   Recv-Q  Send-Q    Local Address:Port     Peer Address:Port  
LISTEN  0       128           0.0.0.0:22            0.0.0.0:*  
LISTEN  0       100         127.0.0.1:25            0.0.0.0:*  

4. tcpdump (Packet Capture)

Capture and analyze network packets to debug issues like misconfigured firewalls or malformed traffic.

$ sudo tcpdump -i eth0 port 80  # Capture HTTP traffic on eth0  

Best Practices for CLI Network Configuration

1. Document Changes: Log every command (e.g., history > config_changes_20240520.txt) and note the purpose.
2. Use Privileged Access Sparingly: In Cisco IOS, use enable only when necessary; in Linux, use sudo for specific commands.
3. Test in a Lab First: Avoid configuring production devices directly—test changes in a lab environment.
4. Version Control Scripts: Store automation scripts in Git to track changes and roll back if needed.
5. Backup Configurations:
   • Linux: Backup /etc/netplan/ or /etc/network/interfaces.
   • Cisco: copy running-config startup-config (save to flash) or copy running-config tftp: (backup to TFTP server).
6. Avoid Manual Edits on Critical Systems: Use tools like Ansible to enforce consistency and reduce human error.

Tools to Enhance CLI Productivity

• Tab Completion: Press Tab to auto-complete commands (works in Bash, PowerShell, Cisco IOS).
• History Search: Use Ctrl+R in Bash to search command history (e.g., Ctrl+R ping finds recent ping commands).
• Terminal Multiplexers: tmux or screen let you manage multiple CLI sessions in one window (critical for remote work).
• SSH Clients: Tools like MobaXterm (Windows) or Termius (cross-platform) offer session management and SSH key integration.
• Network-Specific Tools:
  • Netmiko: Python library for SSH connections to network devices (simplifies scripting).
  • NAPALM: Network Automation and Programmability Abstraction Layer with Multivendor support.
  • Ansible Networking Modules: Pre-built modules for Cisco, Juniper, and Arista devices.

Conclusion

Mastering CLI network configuration transforms you from a passive user to an active controller of your network. While GUIs have their place, CLI offers unmatched speed, precision, and automation—essential for scaling and securing modern networks. Start small: practice ip commands on Linux, configure a Cisco switch in a lab, or write a simple PowerShell script. Over time, you’ll build the muscle memory and confidence to tackle even the most complex network tasks.

References

• Linux ip Command Man Page
• Cisco IOS Configuration Guide
• Microsoft PowerShell Networking Cmdlets
• Ansible Networking Documentation
• Netmiko Library