All checks were successful
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 5s
45 lines
1.6 KiB
Markdown
45 lines
1.6 KiB
Markdown
## Purpose
|
|
If you want to deploy the FOG Project software in your homelab environment to remotely image devices via PXE boot, follow the instructions below to get through the process.
|
|
|
|
!!! info "assumptions"
|
|
It is assumed that you are deploying FOG Project in Ubuntu Server 26.04 or newer. This documentation does not account for distro-specific issues in other operating systems.
|
|
|
|
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"
|
|
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
|
|
sudo nano <netplan file>
|
|
```
|
|
|
|
Ensure it looks similar to this:
|
|
|
|
```yaml
|
|
network:
|
|
version: 2
|
|
ethernets:
|
|
ens18:
|
|
addresses:
|
|
- 192.168.3.9/24
|
|
routes:
|
|
- to: default
|
|
via: 192.168.3.1
|
|
match:
|
|
macaddress: bc:24:11:5c:eb:c9
|
|
nameservers:
|
|
addresses:
|
|
- 192.168.3.25
|
|
- 192.168.3.26
|
|
search: []
|
|
set-name: ens18
|
|
```
|
|
|
|
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. |