Differences

This shows you the differences between two versions of the page.

--- sysadmin:vm:setup_network [2025/12/15 14:29] – created mlivolsi
+++ sysadmin:vm:setup_network [2025/12/15 14:31] (current) – mlivolsi
@@ Line 350: / Line 350: @@
 This will restart NetworkManager whenever your system resumes, causing br0 to reacquire its IP.
-️⃣ Use a dispatcher script
-If you don’t want to restart NetworkManager completely, you can write a dispatcher script that just brings up the bridge interface.
-Create:
-bash
-CopyEdit
-sudo mkdir -p /etc/NetworkManager/dispatcher.d
-sudo nano /etc/NetworkManager/dispatcher.d/99-bridge-reup
-Paste:
-bash
-CopyEdit
-#!/bin/bash
-IF=$1
-STATUS=$2
-if [ "$STATUS" = "up" ]; then
-    # Reapply bridge configuration
-    nmcli con up br0
-fi
-Then make it executable:
-bash
-CopyEdit
-sudo chmod +x /etc/NetworkManager/dispatcher.d/99-bridge-reup
-️⃣ Manually bring up br0 after resume
-If you don't want automated scripts, you can run manually:
-bash
-CopyEdit
-sudo nmcli con up br0
-or
-bash
-CopyEdit
-sudo ifdown br0 && sudo ifup br0
-(depends on your network configuration system.)
-️⃣ Check your nmcli bridge config
-Sometimes the problem is that your bridge configuration does not have autoconnect enabled.
-Check:
-bash
-CopyEdit
-nmcli con show br0
-Look for autoconnect: yes. If it is no, fix:
-bash
-CopyEdit
-nmcli con modify br0 connection.autoconnect yes
-💡 Additional check: Disable suspend on the NIC
-Some NICs (e.g., Intel) have power saving that disables wake properly. You can try:
-bash
-CopyEdit
-sudo ethtool -s enp3s0 wol g
-(If you use Wake-on-LAN or want it to remain responsive.)
-✅ Summary recommendation
-On Linux Mint with NetworkManager, solution 1 (restart NetworkManager after resume) usually works most reliably.