Yet another automated deployment

index.html

@@ -216,5 +216,5 @@ <h2 id="whats-here">What's here?</h2>
 
 <!--
 MkDocs version : 1.6.1
-Build Date UTC : 2024-11-24 07:39:55.641666+00:00
+Build Date UTC : 2024-11-24 07:42:28.011548+00:00
 -->

tutorials/epc-setup/index.html

@@ -180,7 +180,7 @@ <h2 id="software-components">Software Components</h2>
 <p>We would also recommend running the optional WebUI (Web User Interface) service: <code>open5gs-webui.service</code>.</p>
 <p>The following steps will walk you through this installation process.</p>
 <h1 id="step-1-open5gs-install-notes">Step 1: Open5GS Install Notes</h1>
-<p>We install Open5GS following the <a href="https://open5gs.org/open5gs/docs/guide/01-quickstart/">Open5GS Quickstart documentation</a> based on your operating system and desired implementation (e.g. "bare metal" directly on the operating system vs. <a href="https://github.com/wildeyedskies/docker-open5gs-basic-config">Docker</a>).
+<p>Install Open5GS following the <a href="https://open5gs.org/open5gs/docs/guide/01-quickstart/">Open5GS Quickstart documentation</a> based on your operating system and desired implementation (e.g. "bare metal" directly on the operating system vs. <a href="https://github.com/wildeyedskies/docker-open5gs-basic-config">Docker</a>).
 There are even <a href="https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/">VoLTE</a> and <a href="https://open5gs.org/open5gs/docs/tutorial/03-VoLTE-dockerized/">Dockerized VoLTE</a> implementations of Open5GS.
 A similar step-by-step tutorial to this one can be found <a href="https://medium.com/networkers-fiit-stu/setting-up-open5gs-a-step-by-step-guide-or-how-we-set-up-our-lab-environment-5da1c8db0439">here</a>.</p>
 <p>In SCN we have run Open5GS successfully using Ubuntu 20.04 and 22.04, on bare metal or in Virtual Machines, installed via the <code>apt</code> package manager.
@@ -234,7 +234,7 @@ <h3 id="a-recommended">A. Recommended</h3>
 <p>The "downstream" ethernet interface (enp4s0) connected to the eNB is assigned two IP addresses and
 subnets, which are configured statically (<em>not</em> by DHCP, hence the <code>dhcp4: no</code>).
 In our case, we need this interface to talk to the Baicells Nova 233 eNB we use.
-Our eNB has the default local (LAN) IP address of <code>192.168.150.1</code>. We also need to set its WAN address (for whatever reason this is required to be different) to <code>192.168.151.1</code>, as in <a href="https://docs.seattlecommunitynetwork.org/infrastructure/sas-setup.html">this eNB setup tutorial</a>. That's why we have the <code>addresses:</code> section that sets the static IP addresses of the EPC to <code>192.168.150.2/24</code> and <code>192.168.151.2/24</code>. Since these IP addresses are in the same subnet as the eNB IP addresses, they will be able to talk to each other automatically <em>without a router in between</em> helping to route communications packets between the two addresses.</p>
+Our eNB has the default local (LAN) IP address of <code>192.168.150.1</code>. We also need to set its WAN address (for whatever reason this is required to be different) to <code>192.168.151.1</code>, as in <a href="https://docs.seattlecommunitynetwork.org/infrastructure/sas-setup">this eNB setup tutorial</a>. That's why we have the <code>addresses:</code> section that sets the static IP addresses of the EPC to <code>192.168.150.2/24</code> and <code>192.168.151.2/24</code>. Since these IP addresses are in the same subnet as the eNB IP addresses, they will be able to talk to each other automatically <em>without a router in between</em> helping to route communications packets between the two addresses.</p>
 <p>Below we also provide an alternate configuration in case you do not yet have a
 machine with 2 ethernet ports or a USB to ethernet adapter dongle. However, only
 the first configuration is recommended for deployments for security reasons.