# 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.
