From 8be72bc93148a40233d6b002846c22f5b0e8d5f9 Mon Sep 17 00:00:00 2001 From: Jose Date: Sun, 25 Jan 2026 11:19:52 +0100 Subject: [PATCH] =?UTF-8?q?docs=20=F0=9F=93=9D:=20Fix=20typo=20and=20updat?= =?UTF-8?q?e=20bridge=20layout?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Corrected a minor typo in the README.md file and improved the visual clarity of the bridge layout. --- README.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 9fc9467..b42671a 100644 --- a/README.md +++ b/README.md @@ -83,7 +83,7 @@ If a bridge is built on a bond (e.g., `bond0`), every slave is treated as a cand - If `wol_mode` is `'d'`, the role ensures WOL is disabled. 7. **Deploy systemd template** – Copies `templates/wol@.service.j2` to `/etc/systemd/system/wol@.service`. The template contains `ExecStart=/usr/sbin/ethtool -s %I wol {{ wol_mode }}`. -8. **Enable service per interface** – For every interface, the role starts the unit +8. **Enable service per interface** – For every interface, the role starts the unit `wol@.service` and enables it to run on boot. 9. **Report** – A final summary is printed, optionally listing MAC addresses if `wol_report_mac` is `true`. @@ -117,7 +117,8 @@ is `true`. - vmbr2 ``` -> **Result** – All three bridges are processed; the physical NICs that belong to each bridge receive the configured WOL mode. +> **Result** – All three bridges are processed; the physical NICs that belong to each bridge +> receive the configured WOL mode. ### Disable WOL @@ -151,10 +152,12 @@ is `true`. ## Common Proxmox Scenarios | Scenario | Bridge / NIC Layout | What the role does | -|----------|---------------------|--------------------| +|----------|-------------------|------------------| | **Standard vmbr0** | `eno1` → `vmbr0` | Enables WOL on `eno1`. | | **Bonded NICs** | `eno1`, `eno2` → `bond0` → `vmbr0` | Detects `bond0` and sets WOL on *both* slaves. | -| **Multiple Bridges** | `eno1` → `vmbr0`
`eno2` → `vmbr1`
`eno3`, `eno4` → `bond0` → `vmbr2` | One role run configures all three bridges automatically. | +| **Multiple Bridges** | `eno1` → `vmbr0` \ +`eno2` → `vmbr1` \ +`eno3`, `eno4` → `bond0` → `vmbr2` | One role run configures all three bridges automatically. | --- @@ -162,7 +165,7 @@ is `true`. | Problem | Likely Cause | Fix | |---------|--------------|-----| -| **No interfaces found that support WOL** | BIOS WOL disabled, NIC driver doesn’t expose the feature, or interface isn’t a physical NIC. | Enable WOL in BIOS, run `ethtool ` manually, verify `ansible -m setup | grep ansible_interfaces`. | +| **No interfaces found that support WOL** | BIOS WOL disabled, NIC driver doesn’t expose the feature, or interface isn’t a physical NIC. | Enable WOL in BIOS, run `ansible -m setup \| grep ansible_interfaces`. | | **Unable to detect bridge backing NIC(s)** | Bridge doesn’t exist or the NIC isn’t a member of it. | Verify with `bridge link show` / `brctl show`. | | **WOL not persisting after reboot** | `wol@.service` isn’t enabled, or `ethtool` isn’t installed. | Ensure the role ran successfully, check `/etc/systemd/system/wol@.service` and `systemctl status wol@.service`. | | **Bond0 not detected** | Bond configuration file missing or wrong. | Check `/proc/net/bonding/bond0`. |