Template hostapd interface/SSIDs/5GHz radio lines; guard against other-host hardcodes

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KqhjP7nud5gdBg25zCiRk9

ap/20-van-br0.netdev

@@ -1,5 +1,5 @@
 # LAN bridge: joins the AP Wi-Fi radios (added by hostapd, once in AP mode) and the
-# wired LAN ports (enx00e04c331140 + onboard eth0, added by networkd) into one
+# wired LAN ports (the LAN_IFACE port + onboard eth0, added by networkd) into one
 # 10.42.1.0/24 segment. STP off: all members are leaf ports, no loops (don't cable
 # the two wired ports to the same switch), and it avoids the forwarding delay that
 # would otherwise stall the first DHCP handshake on a freshly-plugged client.

ap/hostapd-2g.conf

@@ -1,4 +1,4 @@
-interface=wlx3c3332002066
+interface=@WIFI_2G_IFACE@
 # Second, independent hostapd instance (hostapd-2g.service) — 2.4GHz band of the same
 # VanLink network, bridged into the same br0 segment as the 5GHz AP and the wired port.
 # Separate process on purpose: a USB wedge on one radio must never take down the other.
@@ -8,7 +8,7 @@ ctrl_interface=/var/run/hostapd
 driver=nl80211
 # Same SSID + PSK as 5GHz: dual-band clients pick a band themselves, 2.4-only IoT
 # devices just join. Rename here (e.g. VanLink-2G) if band pinning is ever needed.
-ssid=VanLink2-2G
+ssid=@AP_SSID_2G@
 country_code=CA
 ieee80211d=1
 hw_mode=g

ap/hostapd.conf

@@ -8,7 +8,7 @@ bridge=br0
 # stays "running" but stops serving after a USB glitch.
 ctrl_interface=/var/run/hostapd
 driver=nl80211
-ssid=VanLink2
+ssid=@AP_SSID_5G@
 country_code=CA
 ieee80211d=1
 hw_mode=a
@@ -19,10 +19,7 @@ wmm_enabled=1
 ieee80211n=1
 ieee80211ac=1
 ieee80211ax=1
-ht_capab=[HT20][SHORT-GI-20][HT40+][HT40-]
-vht_capab=[MAX-MPDU-11454][RXLDPC][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][SU-BEAMFORMEE]
-he_su_beamformee=1
-he_mu_edca_qos_info_param_count=0
+@AP_5G_RADIO@
 auth_algs=1
 wpa=2
 wpa_passphrase=1foot11foot11