vanlink/ap/22-van-lan.network at 21c8870c0d369f025f8f9fc2fb0e86424307bdc1 - vanlink - Gitea: Git with a cup of tea

andreas/vanlink

Files

T

Andreas WredeandClaude Sonnet 5 5d88e1b30c deploy: hardware-instance templating, wlan0 boot watchdog, deploy-time warnings in Cockpit

- deploy.conf templates interface names/USB IDs (@TOKEN@ substitution) across
  ap/* configs so a dongle swap only needs deploy.conf edited, not the repo
  configs themselves; drops ap/rtw88.conf (old 2.4GHz dongle retired for the
  DWA-171, which needs no such power-save override).
- failover/van-wlan-watchdog: recovers wlan0 from NM's post-boot no-secrets
  wedge (a boot-time supplicant race, not a real credential failure).
- deploy.sh: warn() collects dependency/config warnings (missing python3-gps,
  python3-paho-mqtt, mobile-broadband-provider-info, grpcurl, gpsd; netplan
  drift; unedited example configs) into /var/lib/vanlink/deploy-warnings.json,
  rendered as an amber Cockpit card so they're visible without reading deploy
  output.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-08-01 11:25:11 -04:00

12 lines

310 B

SYSTEMD

Raw Blame History

 # Wired LAN port: enslaved to br0 so anything plugged in lands on 10.42.0.0/24 and
 # gets DHCP/DNS from the same dnsmasq as Wi-Fi clients. NM must leave this device
 # alone (see van-ap-unmanaged.conf) for networkd to own it here.
 [Match]
 Name=@LAN_USB_IFACE@
 [Link]
 RequiredForOnline=no
 [Network]
 Bridge=br0