Andreas WredeandClaude Fable 5
a7819edbc2
The VM lived on libvirt's default NAT net (192.168.122.50) behind a /etc/libvirt/hooks/network hook that inserted FORWARD accepts above libvirt's REJECT. libvirtd restarts re-inserted its chains on top without firing the hook, silently cutting clients off from HA. Now the VM's NIC (virtio, was e1000) bridges into br0: pinned lease 10.42.0.50 / name 'homeassistant' via van-ap dnsmasq, mDNS discovery works, and no firewall hook can rot. Legacy http://10.42.0.1:8123 kept working via DNAT + same-subnet hairpin masquerade. Hook, libvirt DHCP reservation, and iptables rules removed; domain XML in ha/. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
13 lines
443 B
Plaintext
13 lines
443 B
Plaintext
interface=br0
|
|
bind-dynamic
|
|
except-interface=lo
|
|
domain-needed
|
|
bogus-priv
|
|
dhcp-authoritative
|
|
dhcp-range=10.42.0.10,10.42.0.254,255.255.255.0,12h
|
|
# Home Assistant VM (libvirt ha_van, bridged onto br0) — pinned address, resolves
|
|
# as "homeassistant" via this dnsmasq; HAOS also announces homeassistant.local (mDNS).
|
|
dhcp-host=52:54:00:ad:0a:01,10.42.0.50,homeassistant
|
|
dhcp-option=option:router,10.42.0.1
|
|
dhcp-option=option:dns-server,10.42.0.1
|