-
-
- When adding an NVMe SSD to a Lenovo ThinkCentre M700 running Proxmox, the network interface names may change due to PCI enumeration shifts. This can cause OPNsense (running as a Proxmox VM) to lose access to its network interfaces. This guide explains how to diagnose and fix this issue.
-
-
Run the following command on the Proxmox host:
ip link show
This will list all network interfaces. If your primary NIC was previously
enp1s0
and is nowenp2s0
, the system has renamed it.
-
-
-
If the network adapter name has changed, update the Proxmox configuration.
-
In proxmox --> pve1 node --> shell: Open the network configuration file:
nano /etc/network/interfaces
Locate the section configuring
vmbr0
, which may look like this:auto vmbr0 iface vmbr0 inet static address 192.168.1.2/24 gateway 192.168.1.1 bridge-ports enp1s0 bridge-stp off bridge-fd 0
Change
enp1s0
toenp2s0
:auto vmbr0 iface vmbr0 inet static address 192.168.1.2/24 gateway 192.168.1.1 bridge-ports enp2s0 bridge-stp off bridge-fd 0
Save and exit (
Ctrl + X
, thenY
, thenEnter
). -
Apply the changes:
systemctl restart networking
If the issue persists, reboot Proxmox:
reboot
-
-
- Go to Datacenter → Your Node (eg pve1) → Network
- Ensure
vmbr0
is usingenp2s0
. - If the network is still down, remove and re-add the network bridge in the Proxmox UI.
-
- Once Proxmox is correctly configured:
- Start the OPNsense VM logseq.order-list-type:: number
- Open the console. logseq.order-list-type:: number
- Select Option 1: Assign Interfaces. logseq.order-list-type:: number
- Reassign LAN and WAN to the correct interfaces. logseq.order-list-type:: number
- Save and exit. logseq.order-list-type:: number
-
Created
February 24, 2025 00:56
-
-
Save lennon101/d4c7542c9a1ae5b2aead30d16f847b1d to your computer and use it in GitHub Desktop.
Fixing Network Issues in Proxmox After Adding an NVMe SSD
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment