Missing Default Route After Network Change

Step 1: Confirm the Default Route is Missing

# Linux
ip route show
# A healthy output includes a line like:
# default via 192.168.1.1 dev eth0 proto dhcp src 192.168.1.100 metric 100

# If the default line is absent, you have no default route.

# macOS
netstat -rn | grep default
# Should show: default  192.168.1.1  UGScg  en0

# Windows
route print | findstr "0.0.0.0"
# Should show: 0.0.0.0   0.0.0.0   192.168.1.1   ...

Step 2: Verify Local Gateway is Reachable

# Find the gateway from the local interface
ip route show | grep "link src"
# Or read the subnet: ip addr show eth0

# Ping the gateway
ping -c4 192.168.1.1

# If the gateway is also unreachable, the problem is at Layer 2 (cable, switch, VLAN)

Step 3: Check DHCP Client Status

# If the interface uses DHCP, confirm the client is running and received a lease
systemctl status dhclient
# or for systemd-networkd:
networkctl status eth0

# Renew the DHCP lease
sudo dhclient -r eth0   # release
sudo dhclient eth0      # renew

# Verify the route was added after renewal:
ip route show | grep default

Step 4: Examine Network Configuration Files

# For static configuration, check the file that was edited:
# Debian/Ubuntu (interfaces):
cat /etc/network/interfaces | grep gateway

# Ubuntu Netplan:
cat /etc/netplan/*.yaml | grep gateway4

# RHEL/CentOS (nmcli):
nmcli connection show eth0 | grep IP4.GATEWAY
# or
cat /etc/sysconfig/network-scripts/ifcfg-eth0 | grep GATEWAY

Step 5: Test with a Temporary Manual Route

# Add a temporary default route to verify this is the issue
sudo ip route add default via 192.168.1.1 dev eth0

# Test connectivity
ping -c4 8.8.8.8
curl -I https://example.com

# If it works, the issue was the missing route — now make it permanent

Fix: Add the Default Route Immediately

# Linux — temporary fix (lost on reboot)
sudo ip route add default via 192.168.1.1 dev eth0

# Verify
ip route show | grep default
ping -c4 8.8.8.8

Fix: Make it Permanent — Debian/Ubuntu (interfaces)

# /etc/network/interfaces
sudo nano /etc/network/interfaces

# Ensure the following stanza is present:
# iface eth0 inet static
#   address 192.168.1.100
#   netmask 255.255.255.0
#   gateway 192.168.1.1

sudo systemctl restart networking

Fix: Make it Permanent — Ubuntu Netplan

# /etc/netplan/01-netcfg.yaml
network:
  version: 2
  ethernets:
    eth0:
      addresses:
        - 192.168.1.100/24
      routes:
        - to: default
          via: 192.168.1.1
      nameservers:
        addresses: [8.8.8.8, 1.1.1.1]

sudo netplan apply
ip route show | grep default

Fix: Make it Permanent — RHEL/CentOS (nmcli)

sudo nmcli connection modify eth0 ipv4.gateway 192.168.1.1
sudo nmcli connection up eth0

Fix: Re-enable DHCP

# If DHCP should be used:
# Debian/Ubuntu
sudo dhclient eth0

# RHEL/CentOS
sudo nmcli connection modify eth0 ipv4.method auto
sudo nmcli connection up eth0

• Use configuration management (Ansible, Chef, Puppet) to manage network files — human-edited files are error-prone
• Validate network configuration with netplan generate (Ubuntu) or nmcli connection verify before applying
• Test connectivity immediately after any network change: ping 8.8.8.8 and curl -I https://example.com
• For cloud instances, enable instance monitoring that alerts on loss of outbound internet connectivity within 60 seconds
• Keep a console or out-of-band access path (BMC, cloud serial console) available so misconfigured network changes can be reversed without needing the broken network connection