# 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 ` SKIP_COCKPIT=1 # 5GHz AP radio (currently: Realtek RTL8822CE built-in on FriendlyElec R5C, driver rtl88x2ce) WIFI_5G_IFACE=wlan1 # 2.4GHz AP radio (currently: D-Link DWA-171, RTL8821CU, driver rtl8821cu) WIFI_2G_IFACE=wlan2 # Wired LAN port, USB-attached gigabit adapter (RTL8153-family) LAN_USB_IFACE=eth0 # Starlink dish uplink, USB-attached gigabit adapter (RTL8153-family) #STARLINK_IFACE=enxd8ec5eeb3512 # White Belkin dongle #STARLINK_IFACE=enx6c1ff7d210a5 # UGreen 8-port hub's built-in Ethernet (ASIX AX88179B) STARLINK_IFACE=eth1 # 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" # IP address configuration for this router # When deploying to different hardware, change GATEWAY_IP, DHCP_RANGE_START/END, and GATEWAY_NETWORK. # Pi 5 (main): 10.42.0.1/24 with DHCP 10.42.0.10-254 # R5C (failover): 10.42.1.1/24 with DHCP 10.42.1.10-254 GATEWAY_IP="10.42.1.1" GATEWAY_PREFIX="24" GATEWAY_NETWORK="10.42.1.0/24" DHCP_RANGE_START="10.42.1.10" DHCP_RANGE_END="10.42.1.254"