- deploy.conf: DNS_RESOLVERS, always 1.1.1.1/8.8.8.8, never a WAN's own DHCP/RA-provided servers (previously whatever Wapana handed out). - ap/99-van-router-dns.conf: global resolved config (fixed DNS, Domains=~., global MulticastDNS=yes — a prerequisite for any per-link mDNS to work at all, not just an on/off toggle). - failover/60-van-wan-dns: NM dispatcher that strips each WAN's DNS/search- domain and disables its mDNS via resolvectl on every connect/lease event (NM's own ipv4/ipv6.ignore-auto-dns can't be set as a config-file default — confirmed rejected as an unknown key — so this enforces it directly instead), retried over ~5s to beat NM's own async DNS commit. Also logs what each WAN advertised, never used, to /run/van-wan-dns/. - ap/21-van-br0.network: MulticastDNS=yes, scoped to the van's own LAN only — .local/mDNS now resolves for ESPHome and other LAN devices without leaking mDNS onto Wapana/Starlink/cellular. - dns/: ZeroTier-managed DNS (zt.wrede.pvt) made reproducible — installed the official zerotier-systemd-manager package (verified against upstream checksums), additive to the above so *.zt.wrede.pvt keeps resolving over the overlay independent of WAN. - ha/esphome.container: ESPHome dashboard as a sibling Podman Quadlet to Home Assistant, same host-network/config-volume pattern. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
17 lines
563 B
SYSTEMD
17 lines
563 B
SYSTEMD
# The LAN gateway IP now lives on the bridge, not on the AP wlan (which is just a
|
|
# bridge member). ConfigureWithoutCarrier keeps 10.42.0.1 up even before any wired
|
|
# device is plugged, exactly as it was on the wlan-only setup.
|
|
[Match]
|
|
Name=br0
|
|
|
|
[Link]
|
|
RequiredForOnline=no
|
|
|
|
[Network]
|
|
Address=10.42.0.1/24
|
|
ConfigureWithoutCarrier=yes
|
|
# Resolve .local (mDNS) for devices on the van's own LAN (ESPHome nodes,
|
|
# etc.) — scoped to br0 only, not the WAN links, since mDNS is link-local
|
|
# and that's the only interface those devices are actually on.
|
|
MulticastDNS=yes
|