Andreas WredeandClaude Sonnet 5
8efb8dba5f
- 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>
33 lines
1.4 KiB
Plaintext
33 lines
1.4 KiB
Plaintext
# deploy.conf — hardware-instance identifiers for this Pi's vanlink deployment.
|
|
#
|
|
# These are the values that change when a USB Wi-Fi dongle, LAN adapter, or
|
|
# modem gets physically swapped (MAC-derived interface names are stable per
|
|
# physical device, but change when the device changes). Edit here and run
|
|
# `sudo ./deploy.sh` — it substitutes @TOKEN@ placeholders in the repo's
|
|
# config templates with these values before installing them.
|
|
#
|
|
# Find a new device's interface name after plugging it in: `iw dev` (wifi) or
|
|
# `ip -br link` (wired). USB vendor ID: `lsusb`.
|
|
# Preview a rendered file without deploying: `sudo ./deploy.sh render <file>`
|
|
|
|
# 5GHz AP radio (currently: Realtek RTL8852BU, driver rtw89_8852bu)
|
|
WIFI_5G_IFACE=wlxc83a35a4ee55
|
|
|
|
# 2.4GHz AP radio (currently: D-Link DWA-171, RTL8821CU, driver rtw88_8821cu)
|
|
WIFI_2G_IFACE=wlx3c3332002066
|
|
|
|
# Wired LAN port, USB-attached gigabit adapter (RTL8153-family)
|
|
LAN_USB_IFACE=enx00e04c331140
|
|
|
|
# Starlink dish uplink, USB-attached gigabit adapter (RTL8153-family)
|
|
STARLINK_IFACE=enxd8ec5eeb3512
|
|
|
|
# Cellular modem USB vendor ID (Quectel EC25-AF)
|
|
MODEM_USB_VENDOR=2c7c
|
|
|
|
# Fixed upstream DNS resolvers — this router always uses these, never a WAN's
|
|
# own DHCP/RA-provided servers (NetworkManager is told to ignore those
|
|
# entirely; see ap/van-wan-dns.conf + ap/99-van-router-dns.conf). Keeps
|
|
# resolution identical on Wapana, Starlink, or cellular.
|
|
DNS_RESOLVERS="1.1.1.1 8.8.8.8"
|