You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2024/2024-11-12-Cobbler-v3.3.6-Beginners-Guide.md
+18-6Lines changed: 18 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,11 +78,17 @@ This guide assumes that both the **Cobbler Server** and **PXE Clinet(s)** are ru
78
78
79
79
## Fedora Server Basics
80
80
81
-
As stated above, this document outlines the procedures necessary to install and configure Cobbler v3.3.6 on a Fedora 34 host server for local network installations/provisioning through PXE. Additionally, necessary adjustments will be made for security through **selinux** and **firewalld** on the Cobbler server. As such, it is recommended to keep things simple and **limit the number of additional applications installed** to the Cobbler server to **minimize unexpected firewall and selinux complications.**
81
+
As stated above, this document outlines the procedures necessary to install and configure Cobbler v3.3.6 on a Fedora 34 host server for local network installations/provisioning through PXE. Additionally, recommended security measures for the Cobbler server will be detailed towards the end of this guide, including basic **selinux**and **firewalld** configs.
82
82
83
83
### Updating
84
84
85
-
If Cobbler is to be installed on a Fedora 34 *Server* host, and automatic partitioning was used during initial OS installation, be sure to extend the LVM Logical Volme to a more usable capacity (recommended 95%):
85
+
First, set a static IP address on the Cobbler server interface *(enp0s8)* for hosting PXE services
If Cobbler is to be installed on a Fedora 34 *Server edition* host, and automatic partitioning was used during initial OS installation, be sure to extend the LVM Logical Volme to a more usable capacity (recommended 95%):
@@ -312,9 +318,15 @@ SELinux and firewall operations can seem daunting at first, especially with an a
312
318
313
319
SELinux should come enabled by default on a fresh Fedora 34 Server installation, and we set it to `permissive`in the **Base Updates and Configs** section above, but sometimes `selinux` can be disabled on the kernel command line
314
320
315
-
If `selinux=0` is setin the `/proc/cmdline` file, then follow the instructions found in the `/etc/selinux/config` file for the `grubby`command to enable selinux at boot time. The kernel command line parameters will take precedence over the other configurations.
321
+
If `selinux=0` is setin the `/proc/cmdline` file, then follow the instructions found in the `/etc/selinux/config` file for the `grubby`command to enable selinux at boot time*(DO NOT reboot yet)*. The kernel command line parameters will take precedence over the other configurations.
322
+
323
+
With SELinux enabled at the kernel command line, run the `getenforce`command to check the current enforcing status
324
+
325
+
- if`permissive` is returned, skip to the **Enforcing SELinux** section below
326
+
327
+
- if`enforcing`, skip to the **Cobbler SELinux Config** section.
316
328
317
-
If the output of the `getenforce`command is already `permissive` skip to the **Enforcing SELinux**section below;if it is `enforcing` skip to the **Cobbler SELinux Config** section.
329
+
- if`disabled`, proceed to the next section **Enabling SELinux**
> Cobbler Triggers will run at different times depending on which directory they are placed in, and in alphabetical order within that directory. This sync-trigger specifically should typically be run after ALL sync tasks/triggers are completed
381
+
> Cobbler Triggers will run at different times depending on which directory they are placed in, and in alphabetical order within that directory. This sync-trigger specifically should typically be run after ALL other sync tasks/triggers are completed
370
382
>
371
383
>> Additionally, if there is an error with a `cobbler sync` task (trigger, or otherwise) before reaching this trigger, the sync task will terminate, and the trigger will not run, causing Cobbler files to not be relabeled appropriately... however, there are likely bigger issues at hand if the `cobbler sync` task is erroring out.
372
384
>
@@ -412,7 +424,7 @@ Reconfigure **enp0s8** to operate in the **new firewalld zone**
412
424
nmcli con mod enp0s8 connection.zone cobbler
413
425
```
414
426
415
-
> As defined above, this zone will NOT permit inbound ICMP traffic like ping
427
+
> As defined above, this firewall zone will NOT permit inbound ICMP traffic like ping
416
428
417
429
For simplicity, **enp0s3** can be left in the **default firewalld zone** (verify the current active zones with `firewall-cmd --get-active-zones`)
0 commit comments