Birchwood Abbey's gate is a $110 µPC configured as A Small Institute
Gate, thus providing a campus VPN on a campus Wi-Fi access point. It
-routes network traffic from its ~wifi~ and ~lan~ interfaces to its
+routes network traffic from its ~wild~ and ~lan~ interfaces to its
~isp~ interface (and back) with NAT. That is all the abbey requires
of its gate, so there is no additional Ansible configuration in this
chapter (yet).
The abbey gate's ~lan~ interface is the PC's built-in Ethernet
interface, connected to the cloister Ethernet, a Gigabit Ethernet
-switch. Its ~wifi~ interface is a USB3.0 Ethernet adapter connected
-with a cross-over cable to the WAN interface of a Think Penguin
-TPE-R1300 (and at one time a Linksys WRT1900AC). The ~isp~ interface
-is another USB3.0 Ethernet adapter connected with a cross-over cable
-to the Ethernet interface of a "cable modem" (a Starlink terminal).
+switch. Its ~wild~ interface is a USB3.0 Ethernet adapter connected
+to a 5-port Gigabit Ethernet switch into which are patched the WAN
+interfaces of two Think Penguin TPE-R1300 (and sometimes a Linksys
+WRT1900AC), as well as a couple IoT things like an Ecowitt hub and a
+HomeAssistant Pi. The ~isp~ interface is another USB3.0 Ethernet
+adapter connected with a cross-over cable to the Ethernet interface of
+a "cable modem" (a Starlink terminal).
The MAC address of each interface is set in =private/vars.yml= (see
[[file:Institute/private/vars.yml][=Institute/private/vars.yml=]]) as the values of the ~gate_lan_mac~,
-~gate_wifi_mac~ and ~gate_isp_mac~ variables.
+~gate_wild_mac~ and ~gate_isp_mac~ variables.
** The Abbey's Starlink Configuration
errs=0
+if ! grep -HnEr $WILD_NET
+then errs=$(( $errs + 1 )); fi
if ! grep -HnEr $PUBLIC_VPN_NET
then errs=$(( $errs + 1 )); fi
if ! grep -HnEr $CAMPUS_VPN_NET
then errs=$(( $errs + 1 )); fi
-if ! grep -HnEr $GATE_WIFI_NET
-then errs=$(( $errs + 1 )); fi
if ! grep -HnE '^[#*].*TODO|\?\?\?' Institute/README.org
then errs=$(( $errs + 1 )); fi