"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
-<!-- 2026-05-09 Sat 15:42 -->
+<!-- 2026-06-15 Mon 11:36 -->
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Birchwood Abbey Networks</title>
the <code>abbey-</code> prefix on their names. These roles are applied <i>after</i>
the generic institutional roles (again, documented <a href="Institute/README.html">here</a>).
</p>
-<div id="outline-container-orgd8fe5bc" class="outline-2">
-<h2 id="orgd8fe5bc"><span class="section-number-2">1.</span> Overview</h2>
+<div id="outline-container-orgdf0fc51" class="outline-2">
+<h2 id="orgdf0fc51"><span class="section-number-2">1.</span> Overview</h2>
<div class="outline-text-2" id="text-1">
<p>
A Small Institute makes security and privacy top priorities but
philosophy, attitude.
</p>
-<pre class="example" id="orgc79cdd3">
+<pre class="example" id="org20143e3">
|
=
_|||_
</pre>
</div>
</div>
-<div id="outline-container-orgb63becf" class="outline-2">
-<h2 id="orgb63becf"><span class="section-number-2">2.</span> The Abbey Particulars</h2>
+<div id="outline-container-orgfefeb4b" class="outline-2">
+<h2 id="orgfefeb4b"><span class="section-number-2">2.</span> The Abbey Particulars</h2>
<div class="outline-text-2" id="text-2">
<p>
The abbey's public particulars are included below. They are the
</p>
</div>
</div>
-<div id="outline-container-org145e273" class="outline-2">
-<h2 id="org145e273"><span class="section-number-2">3.</span> The Abbey Front Role</h2>
+<div id="outline-container-org61e7e2f" class="outline-2">
+<h2 id="org61e7e2f"><span class="section-number-2">3.</span> The Abbey Front Role</h2>
<div class="outline-text-2" id="text-3">
<p>
Birchwood Abbey's front door is a Digital Ocean Droplet configured as
Dovecot-IMAPd, and hosting a VPN with WireGuard™.
</p>
</div>
-<div id="outline-container-orgecba136" class="outline-3">
-<h3 id="orgecba136"><span class="section-number-3">3.1.</span> Install Emacs</h3>
+<div id="outline-container-orge2eecd3" class="outline-3">
+<h3 id="orge2eecd3"><span class="section-number-3">3.1.</span> Install Emacs</h3>
<div class="outline-text-3" id="text-3-1">
<p>
The monks of the abbey are masters of the staff (bo) and Emacs.
</div>
</div>
</div>
-<div id="outline-container-org7f78165" class="outline-3">
-<h3 id="org7f78165"><span class="section-number-3">3.2.</span> Configure Public Email Aliases</h3>
+<div id="outline-container-org6046b11" class="outline-3">
+<h3 id="org6046b11"><span class="section-number-3">3.2.</span> Configure Public Email Aliases</h3>
<div class="outline-text-3" id="text-3-2">
<p>
The abbey uses several additional email aliases. These are the public
</div>
</div>
</div>
-<div id="outline-container-org8137534" class="outline-3">
-<h3 id="org8137534"><span class="section-number-3">3.3.</span> Configure Git Daemon on Front</h3>
+<div id="outline-container-orga8d1da5" class="outline-3">
+<h3 id="orga8d1da5"><span class="section-number-3">3.3.</span> Configure Git Daemon on Front</h3>
<div class="outline-text-3" id="text-3-3">
<p>
The abbey publishes member Git repositories with <code>git daemon</code>. If
The <code>git daemon</code> is run by SystemD per the <q>git-daemon.service</q> file.
The <code>git-daemon(1)</code> manual page explains the options in detail. The
<code>--base-path</code> option should agree with <code>$projectroot</code> in the
-<q>/etc/gitweb.conf</q> file installed <a href="#org70b1318">here</a>.
+<q>/etc/gitweb.conf</q> file installed <a href="#org10727a5">here</a>.
</p>
<p>
</div>
<div class="org-src-container">
-<code>gitd-tasks</code><pre class="src src-conf" id="org493cb93"><code>- name: Install git.
+<code>gitd-tasks</code><pre class="src src-conf" id="org06b38f9"><code>- name: Install git.
become: yes
<span class="org-variable-name">apt: pkg</span>=git
</div>
<div class="org-src-container">
-<code>gitd-handlers</code><pre class="src src-conf" id="org9b2b9d6"><code>- name: Reload systemd.
+<code>gitd-handlers</code><pre class="src src-conf" id="orgfeefd5b"><code>- name: Reload systemd.
become: yes
systemd:
daemon-reload: yes
</div>
</div>
</div>
-<div id="outline-container-orgfd43e59" class="outline-3">
-<h3 id="orgfd43e59"><span class="section-number-3">3.4.</span> Configure Gitweb on Front</h3>
+<div id="outline-container-org979eb52" class="outline-3">
+<h3 id="org979eb52"><span class="section-number-3">3.4.</span> Configure Gitweb on Front</h3>
<div class="outline-text-3" id="text-3-4">
<p>
The abbey provides an HTML interface to members' public Git
</p>
<div class="org-src-container">
-<code>apache-gitweb</code><pre class="src src-conf" id="org5965c9d"><code>Alias /gitweb-static/ /usr/share/gitweb/static/
+<code>apache-gitweb</code><pre class="src src-conf" id="orgcb3acd3"><code>Alias /gitweb-static/ /usr/share/gitweb/static/
<Directory <span class="org-string">"/usr/share/gitweb/static/"</span>>
Options MultiViews
</Directory>
</div>
<div class="org-src-container">
-<code>gitweb-tasks</code><pre class="src src-conf" id="org70b1318"><code>- name: Enable Apache2 rewrite module.
+<code>gitweb-tasks</code><pre class="src src-conf" id="org10727a5"><code>- name: Enable Apache2 rewrite module.
become: yes
<span class="org-variable-name">apache2_module: name</span>=rewrite
notify: Restart Apache2.
</div>
<div class="org-src-container">
-<code>gitweb-handlers</code><pre class="src src-conf" id="org1fae2ca"><code>- name: Restart Apache2.
+<code>gitweb-handlers</code><pre class="src src-conf" id="org91fc95f"><code>- name: Restart Apache2.
become: yes
systemd:
service: apache2
</div>
</div>
</div>
-<div id="outline-container-org7ce6bc6" class="outline-3">
-<h3 id="org7ce6bc6"><span class="section-number-3">3.5.</span> Configure Apache for Abbey Documentation</h3>
+<div id="outline-container-org19a796c" class="outline-3">
+<h3 id="org19a796c"><span class="section-number-3">3.5.</span> Configure Apache for Abbey Documentation</h3>
<div class="outline-text-3" id="text-3-5">
<p>
Some of the directives added to the <q>-vhost.conf</q> file are needed by
</p>
<div class="org-src-container">
-<code>apache-abbey</code><pre class="src src-conf" id="orga0b66d8"><code><Directory {{ docroot }}/Abbey/>
+<code>apache-abbey</code><pre class="src src-conf" id="org31bda87"><code><Directory {{ docroot }}/Abbey/>
AllowOverride Indexes FileInfo
Options +Indexes +FollowSymLinks
</Directory>
</div>
</div>
</div>
-<div id="outline-container-org5b3280a" class="outline-3">
-<h3 id="org5b3280a"><span class="section-number-3">3.6.</span> Configure Photos URLs on Front</h3>
+<div id="outline-container-orgb30dc78" class="outline-3">
+<h3 id="orgb30dc78"><span class="section-number-3">3.6.</span> Configure Photos URLs on Front</h3>
<div class="outline-text-3" id="text-3-6">
<p>
Some of the directives added to the <q>-vhost.conf</q> file map the abbey's
</p>
<div class="org-src-container">
-<code>apache-photos</code><pre class="src src-conf" id="orgc24d82d"><code>RedirectMatch /Photos$ /Photos/
+<code>apache-photos</code><pre class="src src-conf" id="orgcd3caa8"><code>RedirectMatch /Photos$ /Photos/
RedirectMatch /Photos/(20[0-9][0-9])_([0-9][0-9])_([0-9][0-9])$ \
/Photos/$1_$2_$3/
AliasMatch /Photos/(20[0-9][0-9])_([0-9][0-9])_([0-9][0-9])/(.+)$ \
</div>
</div>
</div>
-<div id="outline-container-org1db8a1f" class="outline-3">
-<h3 id="org1db8a1f"><span class="section-number-3">3.7.</span> Configure Matt's Alter Ego</h3>
+<div id="outline-container-org7c3d2bc" class="outline-3">
+<h3 id="org7c3d2bc"><span class="section-number-3">3.7.</span> Configure Matt's Alter Ego</h3>
<div class="outline-text-3" id="text-3-7">
<p>
Many years ago Matt's evil twin, Friar Puck, released a "pucked"
</p>
<div class="org-src-container">
-<code>apache-pucked</code><pre class="src src-conf" id="org217bddf"><code>RedirectMatch /~puck$ /~matt
+<code>apache-pucked</code><pre class="src src-conf" id="org4ea331b"><code>RedirectMatch /~puck$ /~matt
RedirectMatch /~puck/(.*) /~matt/$1
</code></pre>
</div>
</p>
</div>
</div>
-<div id="outline-container-org668872c" class="outline-3">
-<h3 id="org668872c"><span class="section-number-3">3.8.</span> Configure Tellurion Expiration on Front</h3>
+<div id="outline-container-org489c5e2" class="outline-3">
+<h3 id="org489c5e2"><span class="section-number-3">3.8.</span> Configure Tellurion Expiration on Front</h3>
<div class="outline-text-3" id="text-3-8">
<p>
The abbey's <q>tellurion.png</q> is updated every 15 minutes on the quarter
</p>
<div class="org-src-container">
-<code>apache-tellurion</code><pre class="src src-conf" id="org7f77900"><code><Directory {{ docroot }}/Tellurion/>
+<code>apache-tellurion</code><pre class="src src-conf" id="orgac933e1"><code><Directory {{ docroot }}/Tellurion/>
ExpiresActive On
ExpiresByType image/png <span class="org-string">"modification plus 15 minutes"</span>
</Directory>
</div>
<div class="org-src-container">
-<code>tellurion-tasks</code><pre class="src src-conf" id="orgc049d99"><code>- name: Enable Apache2 expires module.
+<code>tellurion-tasks</code><pre class="src src-conf" id="org216b972"><code>- name: Enable Apache2 expires module.
become: yes
<span class="org-variable-name">apache2_module: name</span>=expires
notify: Restart Apache2.
</div>
</div>
</div>
-<div id="outline-container-orgb2d16a7" class="outline-3">
-<h3 id="orgb2d16a7"><span class="section-number-3">3.9.</span> Configure Apache on Front</h3>
+<div id="outline-container-orgbc3eea0" class="outline-3">
+<h3 id="orgbc3eea0"><span class="section-number-3">3.9.</span> Configure Apache on Front</h3>
<div class="outline-text-3" id="text-3-9">
<p>
The abbey needs to add some Apache2 configuration directives to the
</p>
<p>
-The following task adds the <a href="#org5965c9d"><code>apache-gitweb</code></a>, <a href="#orga0b66d8"><code>apache-abbey</code></a>,
-<a href="#orgc24d82d"><code>apache-photos</code></a>, <a href="#org217bddf"><code>apache-pucked</code></a> and <a href="#org7f77900"><code>apache-tellurion</code></a> directives
+The following task adds the <a href="#orgcb3acd3"><code>apache-gitweb</code></a>, <a href="#org31bda87"><code>apache-abbey</code></a>,
+<a href="#orgcd3caa8"><code>apache-photos</code></a>, <a href="#org4ea331b"><code>apache-pucked</code></a> and <a href="#orgac933e1"><code>apache-tellurion</code></a> directives
described above to the <q>-vhost.conf</q> file, and includes
<q>options-ssl-apache.conf</q> from <q>/etc/letsencrypt/</q>. The rest of the
-Let's Encrypt configuration is discussed in the following <a href="#org0e5fcbc">Install
+Let's Encrypt configuration is discussed in the following <a href="#org644e0b0">Install
Let's Encrypt</a> section.
</p>
</div>
</div>
</div>
-<div id="outline-container-orgfb296d2" class="outline-3">
-<h3 id="orgfb296d2"><span class="section-number-3">3.10.</span> Configure Apache Log Archival</h3>
+<div id="outline-container-orge172b3c" class="outline-3">
+<h3 id="orge172b3c"><span class="section-number-3">3.10.</span> Configure Apache Log Archival</h3>
<div class="outline-text-3" id="text-3-10">
<p>
These tasks hack Apache's <code>logrotate(8)</code> configuration to rotate
</div>
</div>
</div>
-<div id="outline-container-org0e5fcbc" class="outline-3">
-<h3 id="org0e5fcbc"><span class="section-number-3">3.11.</span> Install Let's Encrypt</h3>
+<div id="outline-container-org644e0b0" class="outline-3">
+<h3 id="org644e0b0"><span class="section-number-3">3.11.</span> Install Let's Encrypt</h3>
<div class="outline-text-3" id="text-3-11">
<p>
The abbey uses a Let's Encrypt certificate to authenticate its public
entered as shown below).
</p>
-<pre class="example" id="org6b7f5ea">
+<pre class="example" id="org3ca1ebb">
$ sudo apt install python3-certbot-apache
$ sudo certbot --apache -d birchwood-abbey.net
...
</div>
</div>
</div>
-<div id="outline-container-org442cfd4" class="outline-3">
-<h3 id="org442cfd4"><span class="section-number-3">3.12.</span> Restart Servers Caching Let's Encrypt</h3>
+<div id="outline-container-orgeb1017f" class="outline-3">
+<h3 id="orgeb1017f"><span class="section-number-3">3.12.</span> Restart Servers Caching Let's Encrypt</h3>
<div class="outline-text-3" id="text-3-12">
<div class="org-src-container">
<a href="roles_t/abbey-front/tasks/main.yml"><q>roles_t/abbey-front/tasks/main.yml</q></a><pre class="src src-conf"><code>- name: Install Certbot hook.
</div>
</div>
</div>
-<div id="outline-container-org159a670" class="outline-3">
-<h3 id="org159a670"><span class="section-number-3">3.13.</span> Rotate Let's Encrypt Log</h3>
+<div id="outline-container-org128dac7" class="outline-3">
+<h3 id="org128dac7"><span class="section-number-3">3.13.</span> Rotate Let's Encrypt Log</h3>
<div class="outline-text-3" id="text-3-13">
<p>
The following task arranges to rotate Certbot's logs files.
</div>
</div>
</div>
-<div id="outline-container-orgce3c556" class="outline-3">
-<h3 id="orgce3c556"><span class="section-number-3">3.14.</span> Archive Let's Encrypt Data</h3>
+<div id="outline-container-orgeeeef16" class="outline-3">
+<h3 id="orgeeeef16"><span class="section-number-3">3.14.</span> Archive Let's Encrypt Data</h3>
<div class="outline-text-3" id="text-3-14">
<p>
A backup copy of Let's Encrypt's data (<q>/etc/letsencrypt/</q>) is sent to
</div>
</div>
</div>
-<div id="outline-container-orgbf2cbb7" class="outline-2">
-<h2 id="orgbf2cbb7"><span class="section-number-2">4.</span> The Abbey Core Role</h2>
+<div id="outline-container-org63f6fba" class="outline-2">
+<h2 id="org63f6fba"><span class="section-number-2">4.</span> The Abbey Core Role</h2>
<div class="outline-text-2" id="text-4">
<p>
Birchwood Abbey's core is a mini-PC (System76 Meerkat) configured as A
NTP, DNS and DHCP.
</p>
</div>
-<div id="outline-container-org68bc9a9" class="outline-3">
-<h3 id="org68bc9a9"><span class="section-number-3">4.1.</span> Include Abbey Variables</h3>
+<div id="outline-container-orgdb074fd" class="outline-3">
+<h3 id="orgdb074fd"><span class="section-number-3">4.1.</span> Include Abbey Variables</h3>
<div class="outline-text-3" id="text-4-1">
<p>
In this abbey specific document, most abbey particulars are not
</div>
</div>
</div>
-<div id="outline-container-orgcc5d654" class="outline-3">
-<h3 id="orgcc5d654"><span class="section-number-3">4.2.</span> Install Additional Packages</h3>
+<div id="outline-container-org145464d" class="outline-3">
+<h3 id="org145464d"><span class="section-number-3">4.2.</span> Install Additional Packages</h3>
<div class="outline-text-3" id="text-4-2">
<p>
The scripts that maintain the abbey's web site use a number of
</div>
</div>
</div>
-<div id="outline-container-org12d916b" class="outline-3">
-<h3 id="org12d916b"><span class="section-number-3">4.3.</span> Configure Private Email Aliases</h3>
+<div id="outline-container-orge26cd94" class="outline-3">
+<h3 id="orge26cd94"><span class="section-number-3">4.3.</span> Configure Private Email Aliases</h3>
<div class="outline-text-3" id="text-4-3">
<p>
The abbey uses several additional email aliases. These are the campus
</div>
</div>
</div>
-<div id="outline-container-orgfcd695d" class="outline-3">
-<h3 id="orgfcd695d"><span class="section-number-3">4.4.</span> Configure Git Daemon on Core</h3>
+<div id="outline-container-orgfa1a4c8" class="outline-3">
+<h3 id="orgfa1a4c8"><span class="section-number-3">4.4.</span> Configure Git Daemon on Core</h3>
<div class="outline-text-3" id="text-4-4">
<p>
These tasks are identical to those executed on Front, for similar Git
services on Front and Core. This allows changes to be tested on Core
-before they are pushed to Front. See <a href="#org8137534">3.3</a>
+before they are pushed to Front. See <a href="#orga8d1da5">3.3</a>
for more information.
</p>
</div>
</div>
</div>
-<div id="outline-container-orgb823c17" class="outline-3">
-<h3 id="orgb823c17"><span class="section-number-3">4.5.</span> Configure Gitweb on Core</h3>
+<div id="outline-container-orgf2e2386" class="outline-3">
+<h3 id="orgf2e2386"><span class="section-number-3">4.5.</span> Configure Gitweb on Core</h3>
<div class="outline-text-3" id="text-4-5">
<p>
These tasks are identical to those executed on Front, for similar
Gitweb services on Front and Core. This allows changes to be tested
-on Core before they are pushed to Front. See <a href="#orgfd43e59">Configure Gitweb on
+on Core before they are pushed to Front. See <a href="#org979eb52">Configure Gitweb on
Front</a> for more information.
</p>
</div>
</div>
</div>
-<div id="outline-container-org7da27ca" class="outline-3">
-<h3 id="org7da27ca"><span class="section-number-3">4.6.</span> Configure Tellurion Expiration on Core</h3>
+<div id="outline-container-org6e6ef71" class="outline-3">
+<h3 id="org6e6ef71"><span class="section-number-3">4.6.</span> Configure Tellurion Expiration on Core</h3>
<div class="outline-text-3" id="text-4-6">
<p>
-The <code>apache-tellurion</code> directives are defined <a href="#org7f77900">here</a> and included in the
-Apache configuration below. The <code>tellurion-tasks</code> are defined <a href="#orgc049d99">here</a>
+The <code>apache-tellurion</code> directives are defined <a href="#orgac933e1">here</a> and included in the
+Apache configuration below. The <code>tellurion-tasks</code> are defined <a href="#org216b972">here</a>
and included by the following code block.
</p>
</div>
</div>
</div>
-<div id="outline-container-orgcad5462" class="outline-3">
-<h3 id="orgcad5462"><span class="section-number-3">4.7.</span> Configure Apache on Core</h3>
+<div id="outline-container-org749e098" class="outline-3">
+<h3 id="org749e098"><span class="section-number-3">4.7.</span> Configure Apache on Core</h3>
<div class="outline-text-3" id="text-4-7">
<p>
The Apache2 configuration on Core specifies three web sites (live,
test, and campus). The live and test sites must operate just like the
-site on Front. Their configurations include the same <a href="#org5965c9d"><code>apache-gitweb</code></a>,
-<a href="#orga0b66d8"><code>apache-abbey</code></a>, <a href="#orgc24d82d"><code>apache-photos</code></a>, <a href="#org217bddf"><code>apache-pucked</code></a> and
-<a href="#org7f77900"><code>apache-tellurion</code></a> directives used on Front.
+site on Front. Their configurations include the same <a href="#orgcb3acd3"><code>apache-gitweb</code></a>,
+<a href="#org31bda87"><code>apache-abbey</code></a>, <a href="#orgcd3caa8"><code>apache-photos</code></a>, <a href="#org4ea331b"><code>apache-pucked</code></a> and
+<a href="#orgac933e1"><code>apache-tellurion</code></a> directives used on Front.
</p>
<div class="org-src-container">
</div>
</div>
</div>
-<div id="outline-container-org042c3ee" class="outline-3">
-<h3 id="org042c3ee"><span class="section-number-3">4.8.</span> Configure Documentation URLs</h3>
+<div id="outline-container-org975825c" class="outline-3">
+<h3 id="org975825c"><span class="section-number-3">4.8.</span> Configure Documentation URLs</h3>
<div class="outline-text-3" id="text-4-8">
<p>
The institute serves its <q>/usr/share/doc/</q> on the house (campus) web
site. This is a debugging convenience, making some HTML documentation
more accessible, especially the documentation of software installed on
Core and not on typical desktop clients. Also included: the Apache2
-directives that enable user Git publishing with Gitweb (defined <a href="#org5965c9d">here</a>).
+directives that enable user Git publishing with Gitweb (defined <a href="#orgcb3acd3">here</a>).
</p>
<div class="org-src-container">
</div>
</div>
</div>
-<div id="outline-container-orgfa7526b" class="outline-3">
-<h3 id="orgfa7526b"><span class="section-number-3">4.9.</span> Install Apt Cacher</h3>
+<div id="outline-container-org432d8ca" class="outline-3">
+<h3 id="org432d8ca"><span class="section-number-3">4.9.</span> Install Apt Cacher</h3>
<div class="outline-text-3" id="text-4-9">
<p>
The abbey uses the Apt-Cacher:TNG package cache on Core. The
</div>
</div>
</div>
-<div id="outline-container-orge15057a" class="outline-3">
-<h3 id="orge15057a"><span class="section-number-3">4.10.</span> Use Cloister Apt Cache</h3>
+<div id="outline-container-org574d3a7" class="outline-3">
+<h3 id="org574d3a7"><span class="section-number-3">4.10.</span> Use Cloister Apt Cache</h3>
<div class="outline-text-3" id="text-4-10">
<p>
Core itself will benefit from using the package cache, but should
</div>
</div>
</div>
-<div id="outline-container-org4924f3f" class="outline-3">
-<h3 id="org4924f3f"><span class="section-number-3">4.11.</span> Configure NAGIOS</h3>
+<div id="outline-container-org386225a" class="outline-3">
+<h3 id="org386225a"><span class="section-number-3">4.11.</span> Configure NAGIOS</h3>
<div class="outline-text-3" id="text-4-11">
<p>
A small institute uses <code>nagios4</code> to monitor the health of its network,
Raspberry Pis.
</p>
</div>
-<div id="outline-container-org414d2ee" class="outline-4">
-<h4 id="org414d2ee"><span class="section-number-4">4.11.1.</span> Monitoring The Home Disk</h4>
+<div id="outline-container-org1ad5033" class="outline-4">
+<h4 id="org1ad5033"><span class="section-number-4">4.11.1.</span> Monitoring The Home Disk</h4>
<div class="outline-text-4" id="text-4-11-1">
<p>
The abbey adds monitoring of the space remaining on the volume at
</div>
</div>
</div>
-<div id="outline-container-orgd9d0404" class="outline-4">
-<h4 id="orgd9d0404"><span class="section-number-4">4.11.2.</span> Custom NAGIOS Monitor <code>abbey_pisensors</code></h4>
+<div id="outline-container-orgbe4b03c" class="outline-4">
+<h4 id="orgbe4b03c"><span class="section-number-4">4.11.2.</span> Custom NAGIOS Monitor <code>abbey_pisensors</code></h4>
<div class="outline-text-4" id="text-4-11-2">
<p>
The <code>check_sensors</code> plugin is included in the package
</div>
</div>
</div>
-<div id="outline-container-org9545a84" class="outline-4">
-<h4 id="org9545a84"><span class="section-number-4">4.11.3.</span> Stolen NAGIOS Monitor <code>check_mdstat</code></h4>
+<div id="outline-container-org0a4387d" class="outline-4">
+<h4 id="org0a4387d"><span class="section-number-4">4.11.3.</span> Stolen NAGIOS Monitor <code>check_mdstat</code></h4>
<div class="outline-text-4" id="text-4-11-3">
<p>
This <code>check_mdstat</code> plugin was copied from the NAGIOS Exchange (<a href="https://exchange.nagios.org/directory/plugins/operating-systems/linux/check_mdstat/details/">here</a>).
</div>
</div>
</div>
-<div id="outline-container-org42df1ba" class="outline-4">
-<h4 id="org42df1ba"><span class="section-number-4">4.11.4.</span> Configure NAGIOS Monitoring of The Cloister</h4>
+<div id="outline-container-org929e541" class="outline-4">
+<h4 id="org929e541"><span class="section-number-4">4.11.4.</span> Configure NAGIOS Monitoring of The Cloister</h4>
<div class="outline-text-4" id="text-4-11-4">
<p>
The abbey adds monitoring for more servers: Dantooine, Kessel and Ord
are idiosyncratically in flux.
</p>
</div>
-<div id="outline-container-org4f11f77" class="outline-5">
-<h5 id="org4f11f77"><span class="section-number-5">4.11.4.1.</span> Cloister Network Addresses</h5>
+<div id="outline-container-org5df52d4" class="outline-5">
+<h5 id="org5df52d4"><span class="section-number-5">4.11.4.1.</span> Cloister Network Addresses</h5>
<div class="outline-text-5" id="text-4-11-4-1">
<p>
The IP addresses of all three hosts are nice to use in the NAGIOS
</div>
</div>
</div>
-<div id="outline-container-org5f30805" class="outline-5">
-<h5 id="org5f30805"><span class="section-number-5">4.11.4.2.</span> Install NAGIOS Configurations</h5>
+<div id="outline-container-org20d0954" class="outline-5">
+<h5 id="org20d0954"><span class="section-number-5">4.11.4.2.</span> Install NAGIOS Configurations</h5>
<div class="outline-text-5" id="text-4-11-4-2">
<p>
The following task installs each host's NAGIOS configuration.
</div>
</div>
</div>
-<div id="outline-container-org356f783" class="outline-5">
-<h5 id="org356f783"><span class="section-number-5">4.11.4.3.</span> NAGIOS Monitoring of Dantooine</h5>
+<div id="outline-container-org6082040" class="outline-5">
+<h5 id="org6082040"><span class="section-number-5">4.11.4.3.</span> NAGIOS Monitoring of Dantooine</h5>
<div class="outline-text-5" id="text-4-11-4-3">
<div class="org-src-container">
<a href="roles_t/abbey-core/templates/nagios-dantooine.cfg"><q>roles_t/abbey-core/templates/nagios-dantooine.cfg</q></a><pre class="src src-conf"><code><span class="org-type">define host</span> {
</div>
</div>
</div>
-<div id="outline-container-org039d217" class="outline-5">
-<h5 id="org039d217"><span class="section-number-5">4.11.4.4.</span> NAGIOS Monitoring of Kessel</h5>
+<div id="outline-container-org7af1241" class="outline-5">
+<h5 id="org7af1241"><span class="section-number-5">4.11.4.4.</span> NAGIOS Monitoring of Kessel</h5>
<div class="outline-text-5" id="text-4-11-4-4">
<div class="org-src-container">
<a href="roles_t/abbey-core/templates/nagios-kessel.cfg"><q>roles_t/abbey-core/templates/nagios-kessel.cfg</q></a><pre class="src src-conf"><code><span class="org-type">define host</span> {
</div>
</div>
</div>
-<div id="outline-container-orgae4d84f" class="outline-5">
-<h5 id="orgae4d84f"><span class="section-number-5">4.11.4.5.</span> NAGIOS Monitoring of Ord-Mantell</h5>
+<div id="outline-container-orga937353" class="outline-5">
+<h5 id="orga937353"><span class="section-number-5">4.11.4.5.</span> NAGIOS Monitoring of Ord-Mantell</h5>
<div class="outline-text-5" id="text-4-11-4-5">
<div class="org-src-container">
<a href="roles_t/abbey-core/templates/nagios-ord-mantell.cfg"><q>roles_t/abbey-core/templates/nagios-ord-mantell.cfg</q></a><pre class="src src-conf"><code><span class="org-type">define host</span> {
</div>
</div>
</div>
-<div id="outline-container-org67864f4" class="outline-3">
-<h3 id="org67864f4"><span class="section-number-3">4.12.</span> Install Munin</h3>
+<div id="outline-container-orgd91a2ac" class="outline-3">
+<h3 id="orgd91a2ac"><span class="section-number-3">4.12.</span> Install Munin</h3>
<div class="outline-text-3" id="text-4-12">
<p>
The abbey is experimenting with Munin. NAGIOS is all about notifying
</div>
</div>
</div>
-<div id="outline-container-org227d64c" class="outline-3">
-<h3 id="org227d64c"><span class="section-number-3">4.13.</span> Install Analog</h3>
+<div id="outline-container-org206ad10" class="outline-3">
+<h3 id="org206ad10"><span class="section-number-3">4.13.</span> Install Analog</h3>
<div class="outline-text-3" id="text-4-13">
<p>
The abbey's public web site's access and error logs are emailed
</div>
</div>
</div>
-<div id="outline-container-orgf8de97a" class="outline-3">
-<h3 id="orgf8de97a"><span class="section-number-3">4.14.</span> Add Monkey to Web Server Group</h3>
+<div id="outline-container-orgf9037f5" class="outline-3">
+<h3 id="orgf9037f5"><span class="section-number-3">4.14.</span> Add Monkey to Web Server Group</h3>
<div class="outline-text-3" id="text-4-14">
<p>
Monkey needs to be in <code>www-data</code> so that it can run
</div>
</div>
</div>
-<div id="outline-container-org61acd41" class="outline-3">
-<h3 id="org61acd41"><span class="section-number-3">4.15.</span> Install netpbm For Photo Processing</h3>
+<div id="outline-container-org20f0e64" class="outline-3">
+<h3 id="org20f0e64"><span class="section-number-3">4.15.</span> Install netpbm For Photo Processing</h3>
<div class="outline-text-3" id="text-4-15">
<p>
Monkey's photo processing scripts use <code>netpbm</code> commands like
</div>
</div>
</div>
-<div id="outline-container-org0e51592" class="outline-2">
-<h2 id="org0e51592"><span class="section-number-2">5.</span> The Abbey Gate Role</h2>
+<div id="outline-container-org0d93f4e" class="outline-2">
+<h2 id="org0d93f4e"><span class="section-number-2">5.</span> The Abbey Gate Role</h2>
<div class="outline-text-2" id="text-5">
<p>
Birchwood Abbey's gate is a $110 µPC configured as A Small Institute
Ecowitt hub.
</p>
</div>
-<div id="outline-container-org6bb57a5" class="outline-3">
-<h3 id="org6bb57a5"><span class="section-number-3">5.1.</span> The Abbey Gate's Network Interfaces</h3>
+<div id="outline-container-org9f0a2e5" class="outline-3">
+<h3 id="org9f0a2e5"><span class="section-number-3">5.1.</span> The Abbey Gate's Network Interfaces</h3>
<div class="outline-text-3" id="text-5-1">
<p>
The abbey gate's <code>lan</code> interface is the PC's built-in Ethernet
</p>
</div>
</div>
-<div id="outline-container-orgd354da1" class="outline-3">
-<h3 id="orgd354da1"><span class="section-number-3">5.2.</span> The Abbey's IoT Network</h3>
+<div id="outline-container-org13f89d5" class="outline-3">
+<h3 id="org13f89d5"><span class="section-number-3">5.2.</span> The Abbey's IoT Network</h3>
<div class="outline-text-3" id="text-5-2">
<p>
To allow masquerading between the private subnets and <code>wild</code>, the
following <code>iptables(8)</code> rules are added. They are very similar to the
<code>nat</code> and <code>filter</code> table rules used by a small institute to masquerade
-its <code>lan</code> to its <code>isp</code> (see the <a href="Institute/README.html#orgcdebc22">UFW Rules</a> of a Small Institute).
+its <code>lan</code> to its <code>isp</code> (see the <a href="Institute/README.html#org7ed94c5">UFW Rules</a> of a Small Institute).
The campus WireGuard™ subnet is not included because the campus Wi-Fi
hosts should be routing to the wild subnet directly and are assumed to
be masquerading as their access point(s).
</p>
<div class="org-src-container">
-<code>iot-nat</code><pre class="src src-conf" id="orgcffe50d"><code>-A POSTROUTING -s {{ private_net_cidr }} -o wild -j MASQUERADE
+<code>iot-nat</code><pre class="src src-conf" id="org43eea42"><code>-A POSTROUTING -s {{ private_net_cidr }} -o wild -j MASQUERADE
-A POSTROUTING -s {{ public_wg_net_cidr }} -o wild -j MASQUERADE
</code></pre>
</div>
<div class="org-src-container">
-<code>iot-forward</code><pre class="src src-conf" id="org9eb6bed"><code>-A ufw-before-forward -i lan -o wild -j ACCEPT
+<code>iot-forward</code><pre class="src src-conf" id="orgb73458e"><code>-A ufw-before-forward -i lan -o wild -j ACCEPT
-A ufw-before-forward -i wg0 -o wild -j ACCEPT
</code></pre>
</div>
</p>
</div>
</div>
-<div id="outline-container-org4d5de24" class="outline-3">
-<h3 id="org4d5de24"><span class="section-number-3">5.3.</span> Configure UFW for IoT</h3>
+<div id="outline-container-org4a03b5f" class="outline-3">
+<h3 id="org4a03b5f"><span class="section-number-3">5.3.</span> Configure UFW for IoT</h3>
<div class="outline-text-3" id="text-5-3">
<p>
The following task installs the additional rules in <q>before.rules</q> (as
-in <a href="Institute/README.html#org52994f0">Configure UFW</a>).
+in <a href="Institute/README.html#orgbffa8a8">Configure UFW</a>).
</p>
<div class="org-src-container">
</div>
</div>
</div>
-<div id="outline-container-org4a2989c" class="outline-3">
-<h3 id="org4a2989c"><span class="section-number-3">5.4.</span> The Abbey's Starlink Configuration</h3>
+<div id="outline-container-orgd5fdc3e" class="outline-3">
+<h3 id="orgd5fdc3e"><span class="section-number-3">5.4.</span> The Abbey's Starlink Configuration</h3>
<div class="outline-text-3" id="text-5-4">
<p>
The abbey connects to Starlink via Ethernet, and disables Starlink's
</p>
</div>
</div>
-<div id="outline-container-orgf544c16" class="outline-3">
-<h3 id="orgf544c16"><span class="section-number-3">5.5.</span> Alternate ISPs</h3>
+<div id="outline-container-org43a8569" class="outline-3">
+<h3 id="org43a8569"><span class="section-number-3">5.5.</span> Alternate ISPs</h3>
<div class="outline-text-3" id="text-5-5">
<p>
The abbey used to use a cell phone on a USB tether to get Internet
</div>
</div>
</div>
-<div id="outline-container-org10ccaff" class="outline-2">
-<h2 id="org10ccaff"><span class="section-number-2">6.</span> The Abbey Cloister Role</h2>
+<div id="outline-container-orgac62669" class="outline-2">
+<h2 id="orgac62669"><span class="section-number-2">6.</span> The Abbey Cloister Role</h2>
<div class="outline-text-2" id="text-6">
<p>
Birchwood Abbey's cloister is a small institute campus. The <code>campus</code>
<p>
Wireless clients are issued keys for the cloister VPN by the <code>./abbey
client</code> command which is currently identical to the <code>./inst client</code>
-command (described in <a href="Institute/README.html#orgf253523">The Client Command</a>). The wireless, cloistered
+command (described in <a href="Institute/README.html#org7f55798">The Client Command</a>). The wireless, cloistered
hosts never roam, are not associated with a member, and so are
"campus" clients, issued keys with commands like this:
</p>
S+6HaTnOwwhWgUGXjSBcPAvifKw+j8BDTRfq534gNW4=
</pre>
</div>
-<div id="outline-container-org61c12ec" class="outline-3">
-<h3 id="org61c12ec"><span class="section-number-3">6.1.</span> Use Cloister Apt Cache</h3>
+<div id="outline-container-org9b087eb" class="outline-3">
+<h3 id="org9b087eb"><span class="section-number-3">6.1.</span> Use Cloister Apt Cache</h3>
<div class="outline-text-3" id="text-6-1">
<p>
The Apt-Cacher:TNG program does not work well on the frontier, so is
</div>
</div>
</div>
-<div id="outline-container-orga2d6911" class="outline-3">
-<h3 id="orga2d6911"><span class="section-number-3">6.2.</span> Configure Cloister NRPE</h3>
+<div id="outline-container-org1a12f16" class="outline-3">
+<h3 id="org1a12f16"><span class="section-number-3">6.2.</span> Configure Cloister NRPE</h3>
<div class="outline-text-3" id="text-6-2">
<p>
Each cloistered host is a small institute campus host and thus is
already running an NRPE server (a NAGIOS Remote Plugin Executor
-server) with a custom <code>inst_sensors</code> monitor (described in <a href="Institute/README.html#org0d2271c">Configure
+server) with a custom <code>inst_sensors</code> monitor (described in <a href="Institute/README.html#org9fbfb95">Configure
NRPE</a> of <a href="Institute/README.html">A Small Institute</a>). The abbey adds one complication: yet
another <code>check_sensors</code> variant, <code>abbey_pisensors</code>, installed on
Raspberry Pis (architecture <code>aarch64</code>) only.
</div>
</div>
</div>
-<div id="outline-container-org4230b2d" class="outline-3">
-<h3 id="org4230b2d"><span class="section-number-3">6.3.</span> Install Munin Node</h3>
+<div id="outline-container-orgbab71f3" class="outline-3">
+<h3 id="orgbab71f3"><span class="section-number-3">6.3.</span> Install Munin Node</h3>
<div class="outline-text-3" id="text-6-3">
<p>
Each cloistered host is a Munin node.
<div class="org-src-container">
<a href="roles_t/abbey-cloister/tasks/main.yml"><q>roles_t/abbey-cloister/tasks/main.yml</q></a><pre class="src src-conf"><code>- name: Configure {{ inventory_hostname }} sensors(1).
+ become: yes
copy:
content: |
chip <span class="org-string">"iwlwifi_1-virtual-0"</span>
</div>
</div>
</div>
-<div id="outline-container-orgccc2391" class="outline-3">
-<h3 id="orgccc2391"><span class="section-number-3">6.4.</span> Install Emacs</h3>
+<div id="outline-container-orgaace948" class="outline-3">
+<h3 id="orgaace948"><span class="section-number-3">6.4.</span> Install Emacs</h3>
<div class="outline-text-3" id="text-6-4">
<p>
The monks of the abbey are masters of the staff and Emacs.
</div>
</div>
</div>
-<div id="outline-container-org19320d3" class="outline-2">
-<h2 id="org19320d3"><span class="section-number-2">7.</span> The Abbey Weather Role</h2>
+<div id="outline-container-org09b8c64" class="outline-2">
+<h2 id="org09b8c64"><span class="section-number-2">7.</span> The Abbey Weather Role</h2>
<div class="outline-text-2" id="text-7">
<p>
Birchwood Abbey now uses Home Assistant to record and display weather
</p>
</div>
</div>
-<div id="outline-container-orgdf2e3d4" class="outline-2">
-<h2 id="orgdf2e3d4"><span class="section-number-2">8.</span> The Abbey DVR Role</h2>
+<div id="outline-container-org742159c" class="outline-2">
+<h2 id="org742159c"><span class="section-number-2">8.</span> The Abbey DVR Role</h2>
<div class="outline-text-2" id="text-8">
<p>
The abbey uses AgentDVR to record video from PoE IP HD security
configuration and recordings in <q>/home/agentdvr/</q>.
</p>
</div>
-<div id="outline-container-org85c2ea3" class="outline-3">
-<h3 id="org85c2ea3"><span class="section-number-3">8.1.</span> Install AgentDVR</h3>
+<div id="outline-container-org12aca9d" class="outline-3">
+<h3 id="org12aca9d"><span class="section-number-3">8.1.</span> Install AgentDVR</h3>
<div class="outline-text-3" id="text-8-1">
<p>
AgentDVR is installed according to the iSpy web site's latest
<code>agentdvr</code> account if it has (temporary) authorization.
</p>
</div>
-<div id="outline-container-orgf8d1694" class="outline-4">
-<h4 id="orgf8d1694"><span class="section-number-4">8.1.1.</span> Prepare for AgentDVR Installation</h4>
+<div id="outline-container-orgf4607c8" class="outline-4">
+<h4 id="orgf4607c8"><span class="section-number-4">8.1.1.</span> Prepare for AgentDVR Installation</h4>
<div class="outline-text-4" id="text-8-1-1">
<p>
The following commands are manually executed to create the <code>agentdvr</code>
</div>
</div>
</div>
-<div id="outline-container-org4af08dc" class="outline-4">
-<h4 id="org4af08dc"><span class="section-number-4">8.1.2.</span> Execute AgentDVR Installation</h4>
+<div id="outline-container-orgd971989" class="outline-4">
+<h4 id="orgd971989"><span class="section-number-4">8.1.2.</span> Execute AgentDVR Installation</h4>
<div class="outline-text-4" id="text-8-1-2">
<p>
With the above preparations, the system administrator can get a shell
</p>
</div>
</div>
-<div id="outline-container-org7cb6c63" class="outline-4">
-<h4 id="org7cb6c63"><span class="section-number-4">8.1.3.</span> Complete AgentDVR Installation</h4>
+<div id="outline-container-org4fc3b53" class="outline-4">
+<h4 id="org4fc3b53"><span class="section-number-4">8.1.3.</span> Complete AgentDVR Installation</h4>
<div class="outline-text-4" id="text-8-1-3">
<p>
When Ansible is run a second time, after the installation script, it
</div>
</div>
</div>
-<div id="outline-container-orgef2a47d" class="outline-3">
-<h3 id="orgef2a47d"><span class="section-number-3">8.2.</span> Configure User <code>agentdvr</code></h3>
+<div id="outline-container-org759c49e" class="outline-3">
+<h3 id="org759c49e"><span class="section-number-3">8.2.</span> Configure User <code>agentdvr</code></h3>
<div class="outline-text-3" id="text-8-2">
<p>
AgentDVR runs as the system user <code>agentdvr</code>, which is configured here.
</div>
</div>
</div>
-<div id="outline-container-org1d5c6a5" class="outline-3">
-<h3 id="org1d5c6a5"><span class="section-number-3">8.3.</span> Test For <q>AgentDVR/</q></h3>
+<div id="outline-container-orgf1edd1c" class="outline-3">
+<h3 id="orgf1edd1c"><span class="section-number-3">8.3.</span> Test For <q>AgentDVR/</q></h3>
<div class="outline-text-3" id="text-8-3">
<p>
The following task probes for the <q>/home/agentdvr/AgentDVR/</q>
</div>
</div>
</div>
-<div id="outline-container-orge834b35" class="outline-3">
-<h3 id="orge834b35"><span class="section-number-3">8.4.</span> Create AgentDVR Service</h3>
+<div id="outline-container-org579399b" class="outline-3">
+<h3 id="org579399b"><span class="section-number-3">8.4.</span> Create AgentDVR Service</h3>
<div class="outline-text-3" id="text-8-4">
<p>
This service definition came from the template downloaded (from <a href="https://raw.githubusercontent.com/ispysoftware/agent-install-scripts/main/v2/AgentDVR.service">here</a>)
</div>
</div>
</div>
-<div id="outline-container-org302cbc2" class="outline-3">
-<h3 id="org302cbc2"><span class="section-number-3">8.5.</span> Create AgentDVR Storage</h3>
+<div id="outline-container-org0b6c39a" class="outline-3">
+<h3 id="org0b6c39a"><span class="section-number-3">8.5.</span> Create AgentDVR Storage</h3>
<div class="outline-text-3" id="text-8-5">
<p>
The abbey uses a separate volume to store surveillance recordings,
</div>
</div>
</div>
-<div id="outline-container-org6a98471" class="outline-3">
-<h3 id="org6a98471"><span class="section-number-3">8.6.</span> Install Custom NAGIOS Monitor <code>abbey_dvr</code></h3>
+<div id="outline-container-org28c6abe" class="outline-3">
+<h3 id="org28c6abe"><span class="section-number-3">8.6.</span> Install Custom NAGIOS Monitor <code>abbey_dvr</code></h3>
<div class="outline-text-3" id="text-8-6">
<p>
DVR hosts install a custom NRPE plugin named <code>abbey_dvr</code> to monitor
</div>
</div>
</div>
-<div id="outline-container-org068505d" class="outline-3">
-<h3 id="org068505d"><span class="section-number-3">8.7.</span> Configure IP Cameras</h3>
+<div id="outline-container-orgad089ed" class="outline-3">
+<h3 id="orgad089ed"><span class="section-number-3">8.7.</span> Configure IP Cameras</h3>
<div class="outline-text-3" id="text-8-7">
<p>
-A new security camera is setup as described in <a href="#orgbcbd35c">Cloistering</a>, after
+A new security camera is setup as described in <a href="#orgc20b3b8">Cloistering</a>, after
which the camera should be accessible by name on the abbey networks.
Assuming <code>ping -c1 new</code> works, the camera's web interface will be
accessible at <code>http://new/</code>.
</ul>
</div>
</div>
-<div id="outline-container-org79c420e" class="outline-3">
-<h3 id="org79c420e"><span class="section-number-3">8.8.</span> Configure AgentDVR's Cameras</h3>
+<div id="outline-container-orgcc5db8a" class="outline-3">
+<h3 id="orgcc5db8a"><span class="section-number-3">8.8.</span> Configure AgentDVR's Cameras</h3>
<div class="outline-text-3" id="text-8-8">
<p>
After Ansible has configured and started the AgentDVR service, its web
</p>
</div>
</div>
-<div id="outline-container-org8759686" class="outline-3">
-<h3 id="org8759686"><span class="section-number-3">8.9.</span> Configure AgentDVR's Default Storage</h3>
+<div id="outline-container-orgd37f859" class="outline-3">
+<h3 id="orgd37f859"><span class="section-number-3">8.9.</span> Configure AgentDVR's Default Storage</h3>
<div class="outline-text-3" id="text-8-9">
<p>
AgentDVR's web interface is also used to configure a default storage
</p>
</div>
</div>
-<div id="outline-container-org9eb2379" class="outline-3">
-<h3 id="org9eb2379"><span class="section-number-3">8.10.</span> Configure AgentDVR's Recordings</h3>
+<div id="outline-container-orge1900a4" class="outline-3">
+<h3 id="orge1900a4"><span class="section-number-3">8.10.</span> Configure AgentDVR's Recordings</h3>
<div class="outline-text-3" id="text-8-10">
<p>
After a default storage location has been configured, AgentDVR's
</ul>
</div>
</div>
-<div id="outline-container-org38942e9" class="outline-3">
-<h3 id="org38942e9"><span class="section-number-3">8.11.</span> Restore AgentDVR</h3>
+<div id="outline-container-org915face" class="outline-3">
+<h3 id="org915face"><span class="section-number-3">8.11.</span> Restore AgentDVR</h3>
<div class="outline-text-3" id="text-8-11">
<p>
When restoring <q>/home/</q> from a backup copy, the user accounts are
</div>
</div>
</div>
-<div id="outline-container-org1f83e98" class="outline-2">
-<h2 id="org1f83e98"><span class="section-number-2">9.</span> The Abbey TVR Role</h2>
+<div id="outline-container-org1e6f4fb" class="outline-2">
+<h2 id="org1e6f4fb"><span class="section-number-2">9.</span> The Abbey TVR Role</h2>
<div class="outline-text-2" id="text-9">
<p>
The abbey has a few TV tuners and a subscription to <a href="https://schedulesdirect.org/">Schedules Direct</a>
</p>
<p>
-A new TVR machine needs only <a href="#orgbcbd35c">Cloistering</a> to prepare it for
+A new TVR machine needs only <a href="#orgc20b3b8">Cloistering</a> to prepare it for
Ansible. As part of that process, it should be added to the <code>tvrs</code>
group in the <q>hosts</q> file. An existing server can become a TVR
machine by adding it to the <code>tvrs</code> group.
</p>
</div>
-<div id="outline-container-org69fdfc9" class="outline-3">
-<h3 id="org69fdfc9"><span class="section-number-3">9.1.</span> Include Abbey Variables</h3>
+<div id="outline-container-org8f330eb" class="outline-3">
+<h3 id="org8f330eb"><span class="section-number-3">9.1.</span> Include Abbey Variables</h3>
<div class="outline-text-3" id="text-9-1">
<p>
Private variables in <q>private/vars-abbey.yml</q> are needed, as in the
</div>
</div>
</div>
-<div id="outline-container-orgc734da1" class="outline-3">
-<h3 id="orgc734da1"><span class="section-number-3">9.2.</span> Manually Build and Install MythTV</h3>
+<div id="outline-container-org5a2568d" class="outline-3">
+<h3 id="org5a2568d"><span class="section-number-3">9.2.</span> Manually Build and Install MythTV</h3>
<div class="outline-text-3" id="text-9-2">
<p>
Neither Debian nor the MythTV project provide binary packages of
</div>
</div>
</div>
-<div id="outline-container-org68f3641" class="outline-3">
-<h3 id="org68f3641"><span class="section-number-3">9.3.</span> Restore MythTV</h3>
+<div id="outline-container-org09c94ba" class="outline-3">
+<h3 id="org09c94ba"><span class="section-number-3">9.3.</span> Restore MythTV</h3>
<div class="outline-text-3" id="text-9-3">
<p>
Restoring MythTV from a backup copy to a fresh TVR host:
</ul>
</div>
</div>
-<div id="outline-container-org54142b3" class="outline-3">
-<h3 id="org54142b3"><span class="section-number-3">9.4.</span> Manually Load DB Timezone Info</h3>
+<div id="outline-container-orgf40f575" class="outline-3">
+<h3 id="orgf40f575"><span class="section-number-3">9.4.</span> Manually Load DB Timezone Info</h3>
<div class="outline-text-3" id="text-9-4">
<p>
Starting with MythTV version 0.26, the time zone tables must be loaded
</div>
</div>
</div>
-<div id="outline-container-org7c6c1f3" class="outline-3">
-<h3 id="org7c6c1f3"><span class="section-number-3">9.5.</span> Create MythTV Storage Area</h3>
+<div id="outline-container-org808c2b0" class="outline-3">
+<h3 id="org808c2b0"><span class="section-number-3">9.5.</span> Create MythTV Storage Area</h3>
<div class="outline-text-3" id="text-9-5">
<p>
The backend does not have a default storage area for its recordings.
</div>
</div>
</div>
-<div id="outline-container-orgbbfee39" class="outline-3">
-<h3 id="orgbbfee39"><span class="section-number-3">9.6.</span> Configure MythTV Backend</h3>
+<div id="outline-container-org74b7705" class="outline-3">
+<h3 id="org74b7705"><span class="section-number-3">9.6.</span> Configure MythTV Backend</h3>
<div class="outline-text-3" id="text-9-6">
<p>
With MythTV built and installed, the post-installation tasks
</ul>
</div>
</div>
-<div id="outline-container-org47d1cd3" class="outline-3">
-<h3 id="org47d1cd3"><span class="section-number-3">9.7.</span> Configure Tuner</h3>
+<div id="outline-container-orgfaf6990" class="outline-3">
+<h3 id="orgfaf6990"><span class="section-number-3">9.7.</span> Configure Tuner</h3>
<div class="outline-text-3" id="text-9-7">
<p>
The abbey has a Silicon Dust Homerun HDTV Duo (with two tuners). It
-is setup as described in <a href="#orgbcbd35c">Cloistering</a>, after which the tuner is
+is setup as described in <a href="#orgc20b3b8">Cloistering</a>, after which the tuner is
accessible by name (e.g. <code>new</code>) on the cloister network. Assuming
<code>ping -c1 new</code> works, the tuner should be accessible via the
<code>hdhomerun_config_gui</code> command, a graphical interface contributed to
</p>
</div>
</div>
-<div id="outline-container-org64695ca" class="outline-3">
-<h3 id="org64695ca"><span class="section-number-3">9.8.</span> Add HDHomerun and Mr.Antenna</h3>
+<div id="outline-container-orgccbdf6f" class="outline-3">
+<h3 id="orgccbdf6f"><span class="section-number-3">9.8.</span> Add HDHomerun and Mr.Antenna</h3>
<div class="outline-text-3" id="text-9-8">
<p>
In MythTV Setup:
</ul>
</div>
</div>
-<div id="outline-container-org1a5bf23" class="outline-3">
-<h3 id="org1a5bf23"><span class="section-number-3">9.9.</span> Scan for New Channels</h3>
+<div id="outline-container-orgde61b4e" class="outline-3">
+<h3 id="orgde61b4e"><span class="section-number-3">9.9.</span> Scan for New Channels</h3>
<div class="outline-text-3" id="text-9-9">
<p>
In MythTV Backend, the website on Core's port 6544, e.g.
</ul>
</div>
</div>
-<div id="outline-container-orge06879f" class="outline-3">
-<h3 id="orge06879f"><span class="section-number-3">9.10.</span> Configure XMLTV</h3>
+<div id="outline-container-org80ccc8f" class="outline-3">
+<h3 id="org80ccc8f"><span class="section-number-3">9.10.</span> Configure XMLTV</h3>
<div class="outline-text-3" id="text-9-10">
<p>
The <code>xmltv</code> package, specifically its <code>tv_grab_zz_sdjson</code> program, is
the OTA (over the air) broadcasts.
</p>
-<pre class="example" id="org1ea8f23">
+<pre class="example" id="orgc1ba380">
$ tv_grab_zz_sdjson --configure --config-file .mythtv/Mr.Antenna.xml
Cache file for lineups, schedules and programs.
Cache file: [/home/mythtv/.xmltv/tv_grab_zz_sdjson.cache]
</p>
</div>
</div>
-<div id="outline-container-org2d5e116" class="outline-3">
-<h3 id="org2d5e116"><span class="section-number-3">9.11.</span> Debug XMLTV</h3>
+<div id="outline-container-orge5a0a71" class="outline-3">
+<h3 id="orge5a0a71"><span class="section-number-3">9.11.</span> Debug XMLTV</h3>
<div class="outline-text-3" id="text-9-11">
<p>
If the <code>mythfilldatabase</code> command fails or expected listings do not
</div>
</div>
</div>
-<div id="outline-container-orge0bfe53" class="outline-3">
-<h3 id="orge0bfe53"><span class="section-number-3">9.12.</span> Change Broadcast Area</h3>
+<div id="outline-container-org80d938c" class="outline-3">
+<h3 id="org80d938c"><span class="section-number-3">9.12.</span> Change Broadcast Area</h3>
<div class="outline-text-3" id="text-9-12">
<p>
The abbey changes location almost weekly, so its HDTV broadcast area
changes frequently. At the start of a long stay the administrator
uses the MythTV Setup program to scan for the new area's channels, as
-described in <a href="#org1a5bf23">Scan for New Channels</a>.
+described in <a href="#orgde61b4e">Scan for New Channels</a>.
</p>
<p>
<p>
The program will prompt for the zip code and offer a list of "inputs"
-available in that area, as described in <a href="#orge06879f">Configure XMLTV</a>.
+available in that area, as described in <a href="#org80ccc8f">Configure XMLTV</a>.
</p>
<p>
</div>
<p>
-If the command fails, consult <a href="#org2d5e116">Debug XMLTV</a>. Else, the listings appear
+If the command fails, consult <a href="#orge5a0a71">Debug XMLTV</a>. Else, the listings appear
in MythTV Backend's "Program Guide" page.
</p>
</div>
</div>
</div>
-<div id="outline-container-org89ddc1e" class="outline-2">
-<h2 id="org89ddc1e"><span class="section-number-2">10.</span> The Ansible Configuration</h2>
+<div id="outline-container-org3257ce4" class="outline-2">
+<h2 id="org3257ce4"><span class="section-number-2">10.</span> The Ansible Configuration</h2>
<div class="outline-text-2" id="text-10">
<p>
The abbey's Ansible configuration, like that of <a href="Institute/README.html">A Small Institute</a>, is
</p>
<p>
-NOTE: if you have not read at least the <a href="Institute/README.html#org
953f84e">Overview</a> of <a href="Institute/README.html">A Small Institute</a>
+NOTE: if you have not read at least the <a href="Institute/README.html#org
09790c1">Overview</a> of <a href="Institute/README.html">A Small Institute</a>
you are lost.
</p>
<q>README.org</q>, and <a href="Institute/README.html"><q>Institute/README.org</q></a>.
</p>
</div>
-<div id="outline-container-org009c273" class="outline-3">
-<h3 id="org009c273"><span class="section-number-3">10.1.</span> <q>ansible.cfg</q></h3>
+<div id="outline-container-orgadec7f5" class="outline-3">
+<h3 id="orgadec7f5"><span class="section-number-3">10.1.</span> <q>ansible.cfg</q></h3>
<div class="outline-text-3" id="text-10-1">
<p>
This is much like the example (test) institutional configuration file,
</div>
</div>
</div>
-<div id="outline-container-org87eda60" class="outline-3">
-<h3 id="org87eda60"><span class="section-number-3">10.2.</span> <q>hosts</q></h3>
+<div id="outline-container-orgb3b8968" class="outline-3">
+<h3 id="orgb3b8968"><span class="section-number-3">10.2.</span> <q>hosts</q></h3>
<div class="outline-text-3" id="text-10-2">
<div class="org-src-container">
-<a href="hosts"><q>hosts</q></a><pre class="src src-conf" id="orga772956"><code>all:
+<a href="hosts"><q>hosts</q></a><pre class="src src-conf" id="org64e133d"><code>all:
vars:
ansible_user: sysadm
ansible_ssh_extra_args: -i Secret/ssh_admin/id_rsa
</div>
</div>
</div>
-<div id="outline-container-org8998876" class="outline-3">
-<h3 id="org8998876"><span class="section-number-3">10.3.</span> <q>playbooks/site.yml</q></h3>
+<div id="outline-container-org1b17cbc" class="outline-3">
+<h3 id="org1b17cbc"><span class="section-number-3">10.3.</span> <q>playbooks/site.yml</q></h3>
<div class="outline-text-3" id="text-10-3">
<p>
This playbook provisions the entire network by applying first the
</div>
</div>
</div>
-<div id="outline-container-org910bf1b" class="outline-2">
-<h2 id="org910bf1b"><span class="section-number-2">11.</span> The Abbey Commands</h2>
+<div id="outline-container-org4fa99bc" class="outline-2">
+<h2 id="org4fa99bc"><span class="section-number-2">11.</span> The Abbey Commands</h2>
<div class="outline-text-2" id="text-11">
<p>
The <code>./abbey</code> script encodes the abbey's canonical procedures. It
-includes <a href="Institute/README.html#org219b1f0">The Institute Commands</a> and adds a few abbey-specific
+includes <a href="Institute/README.html#org072ccf4">The Institute Commands</a> and adds a few abbey-specific
sub-commands.
</p>
</div>
-<div id="outline-container-orga60eee4" class="outline-3">
-<h3 id="orga60eee4"><span class="section-number-3">11.1.</span> Abbey Command Overview</h3>
+<div id="outline-container-org8bb4807" class="outline-3">
+<h3 id="org8bb4807"><span class="section-number-3">11.1.</span> Abbey Command Overview</h3>
<div class="outline-text-3" id="text-11-1">
<p>
Institutional sub-commands:
</dl>
</div>
</div>
-<div id="outline-container-org67dbcd9" class="outline-3">
-<h3 id="org67dbcd9"><span class="section-number-3">11.2.</span> Abbey Command Script</h3>
+<div id="outline-container-orgcca0043" class="outline-3">
+<h3 id="orgcca0043"><span class="section-number-3">11.2.</span> Abbey Command Script</h3>
<div class="outline-text-3" id="text-11-2">
<p>
The script begins with the following prefix and trampolines.
The small institute's <code>./inst</code> command expects to be running in
<q>Institute/</q>, not <q>./</q>, but it only references <q>public/</q>, <q>private/</q>,
<q>Secret/</q> and <q>playbooks/check-inst-vars.yml</q>, and will find the abbey
-specific versions of these. The <code>roles_path</code> setting in <a href="#org009c273"><q>ansible.cfg</q></a>
+specific versions of these. The <code>roles_path</code> setting in <a href="#orgadec7f5"><q>ansible.cfg</q></a>
effectively merges the institutional roles into the distinctly named
abbey specific roles. The roles likewise reference files with
relative names, and will find the abbey specific <q>private/</q>
</div>
</div>
</div>
-<div id="outline-container-org741731b" class="outline-3">
-<h3 id="org741731b"><span class="section-number-3">11.3.</span> The Upgrade Command</h3>
+<div id="outline-container-orgc7b7e0c" class="outline-3">
+<h3 id="orgc7b7e0c"><span class="section-number-3">11.3.</span> The Upgrade Command</h3>
<div class="outline-text-3" id="text-11-3">
<p>
The script implements an <code>upgrade</code> sub-command that runs <code>apt update</code>
</div>
</div>
</div>
-<div id="outline-container-org753535b" class="outline-3">
-<h3 id="org753535b"><span class="section-number-3">11.4.</span> The Reboots Command</h3>
+<div id="outline-container-org6ba85ee" class="outline-3">
+<h3 id="org6ba85ee"><span class="section-number-3">11.4.</span> The Reboots Command</h3>
<div class="outline-text-3" id="text-11-4">
<p>
The script implements a <code>reboots</code> sub-command that looks for
</div>
</div>
</div>
-<div id="outline-container-org98619eb" class="outline-3">
-<h3 id="org98619eb"><span class="section-number-3">11.5.</span> The Versions Command</h3>
+<div id="outline-container-org1bcbca5" class="outline-3">
+<h3 id="org1bcbca5"><span class="section-number-3">11.5.</span> The Versions Command</h3>
<div class="outline-text-3" id="text-11-5">
<p>
The script implements a <code>versions</code> sub-command that reports the
</div>
</div>
</div>
-<div id="outline-container-orgf9b1ac0" class="outline-3">
-<h3 id="orgf9b1ac0"><span class="section-number-3">11.6.</span> The Facts Command</h3>
+<div id="outline-container-orgd9f8357" class="outline-3">
+<h3 id="orgd9f8357"><span class="section-number-3">11.6.</span> The Facts Command</h3>
<div class="outline-text-3" id="text-11-6">
<p>
The script implements a <code>facts</code> sub-command to collect the Ansible
</div>
</div>
</div>
-<div id="outline-container-org50015c8" class="outline-3">
-<h3 id="org50015c8"><span class="section-number-3">11.7.</span> The TZ Command</h3>
+<div id="outline-container-orgc768180" class="outline-3">
+<h3 id="orgc768180"><span class="section-number-3">11.7.</span> The TZ Command</h3>
<div class="outline-text-3" id="text-11-7">
<p>
The abbey changes location almost weekly, so its timezone changes
</div>
</div>
</div>
-<div id="outline-container-org261237d" class="outline-3">
-<h3 id="org261237d"><span class="section-number-3">11.8.</span> Abbey Command Help</h3>
+<div id="outline-container-orgb0ff5ac" class="outline-3">
+<h3 id="orgb0ff5ac"><span class="section-number-3">11.8.</span> Abbey Command Help</h3>
<div class="outline-text-3" id="text-11-8">
<div class="org-src-container">
<a href="abbey"><q>abbey</q></a><pre class="src src-perl"><code><span class="org-keyword">my</span> $<span class="org-variable-name">ops</span> = (<span class="org-string">"config,new,old,pass,client,"</span>
</div>
</div>
</div>
-<div id="outline-container-orgbcbd35c" class="outline-2">
-<h2 id="orgbcbd35c"><span class="section-number-2">12.</span> Cloistering</h2>
+<div id="outline-container-orgc20b3b8" class="outline-2">
+<h2 id="orgc20b3b8"><span class="section-number-2">12.</span> Cloistering</h2>
<div class="outline-text-2" id="text-12">
<p>
This is how a new machine is brought into the cloister. The process
Ansible.
</p>
</div>
-<div id="outline-container-orgecbedba" class="outline-3">
-<h3 id="orgecbedba"><span class="section-number-3">12.1.</span> IoT Devices</h3>
+<div id="outline-container-org025bfc6" class="outline-3">
+<h3 id="org025bfc6"><span class="section-number-3">12.1.</span> IoT Devices</h3>
<div class="outline-text-3" id="text-12-1">
<p>
A wireless IoT device (smart TV, Blu-ray deck, etc.) cannot install
</p>
<ul class="org-ul">
-<li><a href="#orgadef5df">Add to Core DHCP</a></li>
-<li><a href="#org3f8edac">Create Wired Domain Name</a></li>
+<li><a href="#org12f0a21">Add to Core DHCP</a></li>
+<li><a href="#org46888e8">Create Wired Domain Name</a></li>
</ul>
<p>
</p>
<ul class="org-ul">
-<li><a href="#org330fa20">Create Wireless Domain Name</a></li>
+<li><a href="#orgf7703af">Create Wireless Domain Name</a></li>
</ul>
</div>
</div>
-<div id="outline-container-orgb51956b" class="outline-3">
-<h3 id="orgb51956b"><span class="section-number-3">12.2.</span> Raspberry Pis</h3>
+<div id="outline-container-orge44b8a7" class="outline-3">
+<h3 id="orge44b8a7"><span class="section-number-3">12.2.</span> Raspberry Pis</h3>
<div class="outline-text-3" id="text-12-2">
<p>
The abbey's Raspberry Pi runs the Raspberry Pi OS desktop off an NVMe
<li>new username: sysadm</li>
<li>new password: <password></li>
</ul></li>
-<li><a href="#orgadef5df">Add to Core DHCP</a></li>
-<li><a href="#org3f8edac">Create Wired Domain Name</a></li>
+<li><a href="#org12f0a21">Add to Core DHCP</a></li>
+<li><a href="#org46888e8">Create Wired Domain Name</a></li>
<li>Launch the desktop.</li>
<li>If the desktop is running on a USB HD (thumb drive) or μSD card, use
the Raspberry Pi Imager app in Accessories in the main menu. Choose
<li>Right click on the desktop (background) and choose Preferences. In
the Control Centre choose Interfaces in the left side bar and toggle
SSH on.</li>
-<li><a href="#orgef77f9b">Update From Cloister Apt Cache</a></li>
-<li><a href="#org162f1d6">Authorize Remote Administration</a></li>
-<li><a href="#org9304c14">Configure with Ansible</a></li>
+<li><a href="#org0990812">Update From Cloister Apt Cache</a></li>
+<li><a href="#org1218333">Authorize Remote Administration</a></li>
+<li><a href="#orgd719afa">Configure with Ansible</a></li>
</ul>
<p>
</p>
<ul class="org-ul">
-<li><a href="#org844c5f9">Connect to Cloister Wi-Fi</a></li>
-<li><a href="#org93a29fc">Connect to Cloister VPN</a></li>
-<li><a href="#org330fa20">Create Wireless Domain Name</a></li>
+<li><a href="#org2e23c76">Connect to Cloister Wi-Fi</a></li>
+<li><a href="#org9a2e0f6">Connect to Cloister VPN</a></li>
+<li><a href="#orgf7703af">Create Wireless Domain Name</a></li>
</ul>
</div>
</div>
-<div id="outline-container-org1ebc509" class="outline-3">
-<h3 id="org1ebc509"><span class="section-number-3">12.3.</span> PCs</h3>
+<div id="outline-container-org9446d65" class="outline-3">
+<h3 id="org9446d65"><span class="section-number-3">12.3.</span> PCs</h3>
<div class="outline-text-3" id="text-12-3">
<p>
Most of the abbey's machines, like Core and Gate, are general-purpose
to a USB drive and connect it to the PC.</li>
<li>Connect an HDMI monitor, a USB keyboard/mouse, and the cloister
Ethernet, and power up. Choose to boot from the USB drive.</li>
-<li><a href="#orgadef5df">Add to Core DHCP</a></li>
-<li><a href="#org3f8edac">Create Wired Domain Name</a></li>
+<li><a href="#org12f0a21">Add to Core DHCP</a></li>
+<li><a href="#org46888e8">Create Wired Domain Name</a></li>
<li>Answer first-boot installation questions as detailed in the
preparation of <a href="Institute/README.org*A Test Machine">A Test Machine</a> for a Small Institute.</li>
<li>Log in as <code>sysadm</code> on the console.</li>
-<li><a href="#orgef77f9b">Update From Cloister Apt Cache</a></li>
+<li><a href="#org0990812">Update From Cloister Apt Cache</a></li>
<li><p>
Install <code>openssh-server</code>, unless it was included in the
distribution. Run the following if unsure.
<pre class="example">
sudo apt install openssh-server
</pre></li>
-<li><a href="#org162f1d6">Authorize Remote Administration</a></li>
-<li><a href="#org9304c14">Configure with Ansible</a></li>
+<li><a href="#org1218333">Authorize Remote Administration</a></li>
+<li><a href="#orgd719afa">Configure with Ansible</a></li>
</ul>
<p>
</p>
<ul class="org-ul">
-<li><a href="#org844c5f9">Connect to Cloister Wi-Fi</a></li>
-<li><a href="#org93a29fc">Connect to Cloister VPN</a></li>
-<li><a href="#org330fa20">Create Wireless Domain Name</a></li>
+<li><a href="#org2e23c76">Connect to Cloister Wi-Fi</a></li>
+<li><a href="#org9a2e0f6">Connect to Cloister VPN</a></li>
+<li><a href="#orgf7703af">Create Wireless Domain Name</a></li>
</ul>
</div>
</div>
-<div id="outline-container-orgadef5df" class="outline-3">
-<h3 id="orgadef5df"><span class="section-number-3">12.4.</span> Add to Core DHCP</h3>
+<div id="outline-container-org12f0a21" class="outline-3">
+<h3 id="org12f0a21"><span class="section-number-3">12.4.</span> Add to Core DHCP</h3>
<div class="outline-text-3" id="text-12-4">
<p>
When a new machine is connected to the cloister Ethernet, its MAC
</div>
</div>
</div>
-<div id="outline-container-org3f8edac" class="outline-3">
-<h3 id="org3f8edac"><span class="section-number-3">12.5.</span> Create Wired Domain Name</h3>
+<div id="outline-container-org46888e8" class="outline-3">
+<h3 id="org46888e8"><span class="section-number-3">12.5.</span> Create Wired Domain Name</h3>
<div class="outline-text-3" id="text-12-5">
<p>
A wired device is assigned an IP address when it is added to Core's
-DHCP configuration (as in <a href="#orgadef5df">Add to Core DHCP</a>). A private domain name is
+DHCP configuration (as in <a href="#org12f0a21">Add to Core DHCP</a>). A private domain name is
then associated with this address. If the device is intended to
operate wirelessly, the name for its address is modified with a <code>-w</code>
suffix. Thus <code>new-w.small.private</code> would be the name of the new
</div>
</div>
</div>
-<div id="outline-container-orgef77f9b" class="outline-3">
-<h3 id="orgef77f9b"><span class="section-number-3">12.6.</span> Update From Cloister Apt Cache</h3>
+<div id="outline-container-org0990812" class="outline-3">
+<h3 id="org0990812"><span class="section-number-3">12.6.</span> Update From Cloister Apt Cache</h3>
<div class="outline-text-3" id="text-12-6">
<ul class="org-ul">
<li>Log in as <code>sysadm</code> on the console.</li>
</ul>
</div>
</div>
-<div id="outline-container-org162f1d6" class="outline-3">
-<h3 id="org162f1d6"><span class="section-number-3">12.7.</span> Authorize Remote Administration</h3>
+<div id="outline-container-org1218333" class="outline-3">
+<h3 id="org1218333"><span class="section-number-3">12.7.</span> Authorize Remote Administration</h3>
<div class="outline-text-3" id="text-12-7">
<p>
To remotely administer <code>new-w</code>, Ansible must be authorized to login as
</div>
</div>
</div>
-<div id="outline-container-org9304c14" class="outline-3">
-<h3 id="org9304c14"><span class="section-number-3">12.8.</span> Configure with Ansible</h3>
+<div id="outline-container-orgd719afa" class="outline-3">
+<h3 id="orgd719afa"><span class="section-number-3">12.8.</span> Configure with Ansible</h3>
<div class="outline-text-3" id="text-12-8">
<p>
-With remote administration authorized and tested (as in <a href="#org162f1d6">Authorize
+With remote administration authorized and tested (as in <a href="#org1218333">Authorize
Remote Administration</a>), and the machine connected to the cloister
Ethernet, the configuration of <code>new-w</code> can be completed by Ansible.
Note that if the machine is staying on the cloister Ethernet, its
</p>
<p>
-First <code>new-w</code> is added to Ansible's inventory in <a href="#org87eda60"><q>hosts</q></a>. A <code>new-w</code>
+First <code>new-w</code> is added to Ansible's inventory in <a href="#orgb3b8968"><q>hosts</q></a>. A <code>new-w</code>
section is added to the list of all hosts, and an empty section of the
same name is added to the list of <code>campus</code> hosts. If the machine uses
the usual privileged account name, <code>sysadm</code>, the <code>ansible_user</code> key is
</div>
</div>
</div>
-<div id="outline-container-org844c5f9" class="outline-3">
-<h3 id="org844c5f9"><span class="section-number-3">12.9.</span> Connect to Cloister Wi-Fi</h3>
+<div id="outline-container-org2e23c76" class="outline-3">
+<h3 id="org2e23c76"><span class="section-number-3">12.9.</span> Connect to Cloister Wi-Fi</h3>
<div class="outline-text-3" id="text-12-9">
<p>
On an IoT device, or a Debian or Android "desktop", the cloister Wi-Fi
</div>
</div>
</div>
-<div id="outline-container-org93a29fc" class="outline-3">
-<h3 id="org93a29fc"><span class="section-number-3">12.10.</span> Connect to Cloister VPN</h3>
+<div id="outline-container-org9a2e0f6" class="outline-3">
+<h3 id="org9a2e0f6"><span class="section-number-3">12.10.</span> Connect to Cloister VPN</h3>
<div class="outline-text-3" id="text-12-10">
<p>
Wireless devices (with the cloister Wi-Fi password) can get an IP
<p>
Connections to the cloister VPN are authorized by the <code>./abbey
-client...</code> command (aka <a href="Institute/README.html#orgf253523">The Client Command</a>), which registers a new
+client...</code> command (aka <a href="Institute/README.html#org7f55798">The Client Command</a>), which registers a new
client's public key and installs new WireGuard™ configurations on the
servers. Private keys are kept on the clients (e.g. in
<q>/etc/wireguard/private-key</q>).
</p>
</div>
-<div id="outline-container-orgb137076" class="outline-4">
-<h4 id="orgb137076"><span class="section-number-4">12.10.1.</span> Campus Desktops and Servers</h4>
+<div id="outline-container-org1931e36" class="outline-4">
+<h4 id="org1931e36"><span class="section-number-4">12.10.1.</span> Campus Desktops and Servers</h4>
<div class="outline-text-4" id="text-12-10-1">
<p>
Wireless Debian desktops (with NetworkManager) as well as servers
</ul>
</div>
</div>
-<div id="outline-container-org120c7de" class="outline-4">
-<h4 id="org120c7de"><span class="section-number-4">12.10.2.</span> Private Desktops</h4>
+<div id="outline-container-orgc982918" class="outline-4">
+<h4 id="orgc982918"><span class="section-number-4">12.10.2.</span> Private Desktops</h4>
<div class="outline-text-4" id="text-12-10-2">
<p>
Member notebooks are private machines not remotely administered by the
</p>
</div>
</div>
-<div id="outline-container-org8a46237" class="outline-4">
-<h4 id="org8a46237"><span class="section-number-4">12.10.3.</span> Android</h4>
+<div id="outline-container-orgd6eaa14" class="outline-4">
+<h4 id="orgd6eaa14"><span class="section-number-4">12.10.3.</span> Android</h4>
<div class="outline-text-4" id="text-12-10-3">
<p>
Android phones and tablets are authorized to connect to the cloister
</div>
</div>
</div>
-<div id="outline-container-org330fa20" class="outline-3">
-<h3 id="org330fa20"><span class="section-number-3">12.11.</span> Create Wireless Domain Name</h3>
+<div id="outline-container-orgf7703af" class="outline-3">
+<h3 id="orgf7703af"><span class="section-number-3">12.11.</span> Create Wireless Domain Name</h3>
<div class="outline-text-3" id="text-12-11">
<p>
A wireless machine is assigned a Wi-Fi address when it connects to the
</div>
<div id="postamble" class="status">
<p class="author">Author: Matt Birkholz</p>
-<p class="date">Created: 2026-05-09 Sat 15:42</p>
+<p class="date">Created: 2026-06-15 Mon 11:36</p>
<p class="validation"><a href="https://validator.w3.org/check?uri=referer">Validate</a></p>
</div>
</body>
projects / Network / commitdiff