diff --git a/deployments/automation/FOG Project.md b/deployments/automation/FOG Project.md index 12d9da5..233c846 100644 --- a/deployments/automation/FOG Project.md +++ b/deployments/automation/FOG Project.md @@ -7,34 +7,39 @@ If you want to deploy the FOG Project software in your homelab environment to re It is also assumed that you allocate at least 4-cores and 8GB of RAM with at least 256GB of storage for the OS and FOG images. !!! warning "Potential Netplan Misconfiguration" - I observed an oddity with the networking stack of the Ubuntu Server VM, so just to be safe, run the following command to check that you have both the `nameservers` pointing to your DNS server(s) and `routes` pointing to your default gateway. + If the FOG server cannot resolve DNS names or reach external networks, verify that the Netplan configuration includes both: + + - `nameservers` pointing to valid DNS servers + - a default route pointing to the network gateway + + Check the Netplan configuration: ```sh cd /etc/netplan ls - - nano + sudo nano ``` - Ensure it looks something like this, and fix it if any fields are missing: + Ensure it looks similar to this: ```yaml network: + version: 2 ethernets: - ens18: + ens18: addresses: - - 192.168.3.9/24 + - 192.168.3.9/24 routes: - - to: default + - to: default via: 192.168.3.1 match: - macaddress: bc:24:11:5c:eb:c9 + macaddress: bc:24:11:5c:eb:c9 nameservers: - addresses: [192.168.3.25, 192.168.3.26] - search: [] + addresses: + - 192.168.3.25 + - 192.168.3.26 + search: [] set-name: ens18 - version: 2 ``` - Lastly run `sudo netplan apply` to apply the changes to fix the networking stack. - + Apply the configuration safely and temporarily with `sudo netplan try` and if connectivity still works, accept the changes permanently by running `sudo netplan apply`. Otherwise, Netplan will roll back the changes automatically. \ No newline at end of file