bunny-lab/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update deployments/automation/FOG Project.md
All checks were successful
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 5s
Details

Browse Source
This commit is contained in:
Nicole Rappe
2026-05-04 16:46:09 -06:00
parent 1669691b66
commit 05c452b129
1 changed files with 18 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
deployments/automation/FOG Project.md
View File

@@ -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. 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" !!! 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 ```sh
cd /etc/netplan cd /etc/netplan
ls ls
<look for the netplan file> sudo nano <netplan file>
nano <netplan file>
``` ```
Ensure it looks something like this, and fix it if any fields are missing: Ensure it looks similar to this:
```yaml ```yaml
network: network:
version: 2
ethernets: ethernets:
ens18: ens18:
addresses: addresses:
- 192.168.3.9/24 - 192.168.3.9/24
routes: routes:
- to: default - to: default
via: 192.168.3.1 via: 192.168.3.1
match: match:
macaddress: bc:24:11:5c:eb:c9 macaddress: bc:24:11:5c:eb:c9
nameservers: nameservers:
addresses: [192.168.3.25, 192.168.3.26] addresses:
search: [] - 192.168.3.25
- 192.168.3.26
search: []
set-name: ens18 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.