Files
felhom.eu/documentation/audits/omv-vm-2026-10-15/B1-bridge-timeline.txt
T
admin 340804f9af
gates / gates (push) Successful in 6m53s
Felhom in a VM on OpenMediaVault 8 (KVM plugin): tried on an exact copy of the pilot's box; Hungarian guide; R-1068..R-1073; capability A23
On demo-hp: OMV 8.5.11-1 + openmediavault-kvm 8.3.4 in a VM, every OMV step done in its web pages
(headless browser). Public ISO 1.29.0 on the whole passed NVMe, BIOS firmware, bound and claimed as
throwaway customer Tester4, Vaultwarden + Jellyfin, local backups, two OMV restarts (clean guest
shutdown, AutoStart back in 1 min 52 s). Guest memory 7,863 MiB of 12 GiB.
Traps for the guide: the bridge changes OMV's IP; the plugin boots the disk first (wipe the NVMe);
the host-disk list offers OMV's own disk. Rows: one-disk Jellyfin refusal (R-1068), virtio disk not
formattable (R-1069), tunnel-less OS-update alarm (R-1070), NAS films for Jellyfin (R-1071, operator),
mixed formal/informal backup text (R-1072), no SMART in a VM (R-1073, operator). Register 157 -> 163.
Everything removed; Tester 1 back ONLINE. Customer Tester4 waits for the operator's delete.

Claude-Session: https://claude.ai/code/session_012qRErfCoiTkvDK9N5XHbzb
2026-10-15 19:24:59 +02:00

16 lines
1.7 KiB
Plaintext

# B1 — the network bridge, done in the OMV web page (Hálózat → Interfészek), 2026-10-15 (UTC)
15:27:42 before: ens18 DHCP 192.168.0.119 (MAC bc:24:11:69:24:25), in OMV's own list -> B1-network-before.txt
15:28 Létrehozás → Híd: the „Interfészek" list was EMPTY while ens18 had its own setting (OMV offers only unused cards)
15:29 ens18 deleted (Törlés, not applied) → the list then offered „ens18 [bc:24:11:69:24:25]"
15:29 br0 saved: member ens18, IPv4 DHCP, MAC cím empty (the default)
15:30:22 Alkalmaz pressed (with the Megerősítés tick)
15:30:49 http://192.168.0.119 stopped answering (27 s later); the browser stayed on „Kérjük várjon a konfigurációs változások érvénybe lépéséig..." for good
15:31-33 br0 got MAC 42:6a:75:de:79:02 (generated) and a NEW address 192.168.0.121 -> B1-network-after-bridge-nomac.txt
the console banner still said „ens18: 192.168.0.119" (stale) -> screens/omv-30-after-bridge.png, omv-31-real-ip.png
15:33:59 fix attempt: br0 edited, „MAC cím" = the card's MAC bc:24:11:69:24:25, Alkalmaz at 15:34:19
15:34:25 .121 stopped answering; br0 then had the card's MAC but a THIRD address 192.168.0.123 (not .119)
reason: systemd-networkd asks DHCP with its own client ID (DUID), not only the MAC, so the router sees a new client
the console banner said „br0: 192.168.0.121" (stale again) -> screens/omv-32-after-mac.png
15:46 http://omv-sim.local resolved to 192.168.0.123 (OMV's avahi answers mDNS) — the working way to find OMV again
RESULT: the bridge works; OMV's address CHANGES; the old browser tab hangs; the screen text is stale; <name>.local or the router's list finds it.