Network Configuration

Modified

2026-05-14

Static IP Configuration

The ML workstation uses a static IP address configured through netplan.

Configuration File

Location: /etc/netplan/99-static-ip-bips.yaml

Important: The filename uses a 99- prefix to ensure it takes precedence and prevents the configuration from being overwritten during system upgrades. Ubuntu system updates typically modify lower-numbered netplan files (like 01-network-manager-all.yaml), but will preserve custom high-numbered configurations.

Current Configuration

network:
  ethernets:
    enp68s0:
      dhcp4: false
      dhcp6: false
      addresses:
      - 10.10.11.155/16
      nameservers:
        addresses:
        - 10.10.11.140
        search: []
      routes:
      - to: default
        via: 10.10.11.200
  version: 2

Network Details:

  • Interface: enp68s0
  • IP Address: 10.10.11.155
  • Subnet: /16 (255.255.0.0)
  • Gateway: 10.10.11.200
  • DNS Server: 10.10.11.140

Applying Configuration Changes

After modifying the netplan configuration:

# Test the configuration (will revert after 120 seconds if connection is lost)
sudo netplan try

# Apply the configuration permanently
sudo netplan apply

Troubleshooting

If network connectivity is lost:

  1. Via console access:

    # Check current configuration
    ip addr show
    ip route show
    
    # Revert to DHCP if needed
    sudo mv /etc/netplan/99-static-ip-bips.yaml /etc/netplan/99-static-ip-bips.yaml.bak
    sudo netplan apply
  2. Check interface name:

    # List all network interfaces
    ip link show

    Interface names can change after hardware changes or kernel updates.

  3. Verify netplan configuration:

    # Check for syntax errors
    sudo netplan --debug generate

Backup Files

The directory contains backup files from previous configurations:

  • 90-NM-882f7758-7f5f-409c-a167-7769e9ece53d.yaml.bak - Previous NetworkManager configuration
  • _static-ip-bips.yaml.bak - Previous static IP configuration

Best Practices

  1. Always use high-numbered prefixes (90-99) for custom configurations
  2. Keep backups of working configurations before making changes
  3. Use netplan try before netplan apply to test changes safely
  4. Document any IP changes in team communication channels