-policy in <q>/etc/default/ufw</q>, and install the above rules in
-<q>/etc/ufw/before.rules</q>. When Gate is configured by <code>./abbey config
-gate</code> as in the example bootstrap, enabling the firewall should not be
-a problem. But when configuring a new gate with <code>./abbey config
-new-gate</code>, enabling the firewall could break Ansible's current and
-future ssh sessions. For this reason, Ansible <i>does not</i> enable the
-firewall. The administrator must login and execute the following
-command after Gate is configured or new gate is "in position"
-(connected to old Gate's <code>wild</code> and <code>isp</code> networks).
+policy in <q>/etc/default/ufw</q>, install the NAT rules in
+<q>/etc/ufw/before.rules</q>, and the Forward rules in
+<q>/etc/ufw/user.rules</q> (where the <code>ufw-user-forward</code> chain
+is… mentioned?).
+</p>
+
+<p>
+When Gate is configured by <code>./abbey config gate</code> as in the example
+bootstrap, enabling the firewall should not be a problem. But when
+configuring a new gate with <code>./abbey config new-gate</code>, enabling the
+firewall could break Ansible's current and future ssh sessions. For
+this reason, Ansible <i>does not</i> enable the firewall.
+</p>
+
+<p>
+The administrator must login and execute the following command after
+Gate is configured or new gate is "in position" (connected to old
+Gate's <code>wild</code> and <code>isp</code> networks).