From ece040f34aa2e540c1bfb2a456c1e0fe334db401 Mon Sep 17 00:00:00 2001 From: pkubaj Date: Wed, 30 Aug 2017 17:14:05 +0200 Subject: [PATCH 1/7] Create PfSense.md --- docs/PfSense.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 docs/PfSense.md diff --git a/docs/PfSense.md b/docs/PfSense.md new file mode 100644 index 0000000..c26e0b9 --- /dev/null +++ b/docs/PfSense.md @@ -0,0 +1,20 @@ +In order to boot PfSense via PXE and use unattended install, +you need the following: + +1. Extracted PfSense installation ISO exported via NFS. + +2. Relevant entry in DHCP server config: + `option root-path "/srv/tftp/images/pfsense";` + /srv/tftp/images/pfsense is the path to the extracted ISO. + +3. Relevant entries in PXELINUX config: +``` +label PfSense + menu label PfSense + pxe images/pfsense/boot/pxeboot +``` + +The path `images/pfsense/boot/pxeboot` is relative to TFTP root directory. +It's a path to the PXE loader in the extracted PfSense installation image. + +Unfortunately, there's no mechanism for unattended installation of PfSense. From 0b19e82fc8c5def988ca05866a4f92ce73ba3438 Mon Sep 17 00:00:00 2001 From: pkubaj Date: Wed, 30 Aug 2017 23:18:45 +0200 Subject: [PATCH 2/7] Update PfSense.md --- docs/PfSense.md | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/docs/PfSense.md b/docs/PfSense.md index c26e0b9..f3f9c56 100644 --- a/docs/PfSense.md +++ b/docs/PfSense.md @@ -1,11 +1,22 @@ In order to boot PfSense via PXE and use unattended install, -you need the following: +you need to do the following: -1. Extracted PfSense installation ISO exported via NFS. +1. Download ISO from https://nyifiles.pfsense.org/mirror/downloads/pfSense-CE-2.3.4-RELEASE-amd64.iso.gz + +2. Extract the ISO contents to a directory called + `images/pfsense` in TFTP root: + `gzip -d pfSense-CE-2.3.4-RELEASE-amd64.iso.gz` + + In order to extract the contents, you need to mount + the ISO with following commands (example from FreeBSD): + `mount /dev/$(mdconfig -a -t vnode -f pfSense-CE-2.3.4-RELEASE-amd64.iso) /mnt` + Then: + `rsync -avvP /mnt/ /srv/tftp/images/pfsense/` + You need to have `rsync` installed. 2. Relevant entry in DHCP server config: - `option root-path "/srv/tftp/images/pfsense";` - /srv/tftp/images/pfsense is the path to the extracted ISO. + `option root-path /srv/tftp/images/pfsense;` + `/srv/tftp/images/pfsense` is the path to the extracted ISO. 3. Relevant entries in PXELINUX config: ``` From 2911cca09298a33324221f0090d697963453d789 Mon Sep 17 00:00:00 2001 From: pkubaj Date: Thu, 31 Aug 2017 19:14:35 +0200 Subject: [PATCH 3/7] Remove wrong info --- docs/PfSense.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/PfSense.md b/docs/PfSense.md index f3f9c56..cfda2ab 100644 --- a/docs/PfSense.md +++ b/docs/PfSense.md @@ -1,4 +1,4 @@ -In order to boot PfSense via PXE and use unattended install, +In order to boot PfSense via PXE, you need to do the following: 1. Download ISO from https://nyifiles.pfsense.org/mirror/downloads/pfSense-CE-2.3.4-RELEASE-amd64.iso.gz From a445a046f408d49c2f0adaa8f4f5cd2bb40fa018 Mon Sep 17 00:00:00 2001 From: pkubaj Date: Thu, 31 Aug 2017 19:19:35 +0200 Subject: [PATCH 4/7] PfSense ISO is cd9660 --- docs/PfSense.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/PfSense.md b/docs/PfSense.md index cfda2ab..2b6d775 100644 --- a/docs/PfSense.md +++ b/docs/PfSense.md @@ -9,7 +9,7 @@ you need to do the following: In order to extract the contents, you need to mount the ISO with following commands (example from FreeBSD): - `mount /dev/$(mdconfig -a -t vnode -f pfSense-CE-2.3.4-RELEASE-amd64.iso) /mnt` + `mount_cd9660 /dev/$(mdconfig -a -t vnode -f pfSense-CE-2.3.4-RELEASE-amd64.iso) /mnt` Then: `rsync -avvP /mnt/ /srv/tftp/images/pfsense/` You need to have `rsync` installed. From 1883d966589501cf3538c0d1d4b61bd8d9325fe9 Mon Sep 17 00:00:00 2001 From: pkubaj Date: Thu, 31 Aug 2017 19:42:59 +0200 Subject: [PATCH 5/7] Add info about SHA256 --- docs/PfSense.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/PfSense.md b/docs/PfSense.md index 2b6d775..ffe4f45 100644 --- a/docs/PfSense.md +++ b/docs/PfSense.md @@ -2,6 +2,10 @@ In order to boot PfSense via PXE, you need to do the following: 1. Download ISO from https://nyifiles.pfsense.org/mirror/downloads/pfSense-CE-2.3.4-RELEASE-amd64.iso.gz + + You should also check the SHA256 hash: + `sha256 -c 610b2a8c696e1d1854845d553ce8540debaab9d78ed6c15ce83872eaeac9d05f pfSense-CE-2.3.4-RELEASE-amd64.iso.gz` + and compare it to the one in https://nyifiles.pfsense.org/mirror/downloads/pfSense-CE-2.3.4-RELEASE-amd64.iso.gz.sha256 2. Extract the ISO contents to a directory called `images/pfsense` in TFTP root: From 820d38b1d035508f8b381000ecba87fa883c89f4 Mon Sep 17 00:00:00 2001 From: pkubaj Date: Fri, 1 Sep 2017 19:52:38 +0200 Subject: [PATCH 6/7] Update PfSense.md --- docs/PfSense.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/PfSense.md b/docs/PfSense.md index ffe4f45..6dc4c09 100644 --- a/docs/PfSense.md +++ b/docs/PfSense.md @@ -1,12 +1,11 @@ -In order to boot PfSense via PXE, +In order to boot PfSense via iPXE, you need to do the following: 1. Download ISO from https://nyifiles.pfsense.org/mirror/downloads/pfSense-CE-2.3.4-RELEASE-amd64.iso.gz You should also check the SHA256 hash: `sha256 -c 610b2a8c696e1d1854845d553ce8540debaab9d78ed6c15ce83872eaeac9d05f pfSense-CE-2.3.4-RELEASE-amd64.iso.gz` - and compare it to the one in https://nyifiles.pfsense.org/mirror/downloads/pfSense-CE-2.3.4-RELEASE-amd64.iso.gz.sha256 - + 2. Extract the ISO contents to a directory called `images/pfsense` in TFTP root: `gzip -d pfSense-CE-2.3.4-RELEASE-amd64.iso.gz` @@ -14,6 +13,10 @@ you need to do the following: In order to extract the contents, you need to mount the ISO with following commands (example from FreeBSD): `mount_cd9660 /dev/$(mdconfig -a -t vnode -f pfSense-CE-2.3.4-RELEASE-amd64.iso) /mnt` + + To mount the ISO from GNU / Linux use: + `mount -o loop pfSense-CE-2.3.4-RELEASE-amd64.iso /mnt` + Then: `rsync -avvP /mnt/ /srv/tftp/images/pfsense/` You need to have `rsync` installed. From 3ae1410baaa2916f9c067c59efabd9dcb1726b6c Mon Sep 17 00:00:00 2001 From: pkubaj Date: Fri, 1 Sep 2017 19:58:12 +0200 Subject: [PATCH 7/7] Update PfSense.md --- docs/PfSense.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/PfSense.md b/docs/PfSense.md index 6dc4c09..fe49cbe 100644 --- a/docs/PfSense.md +++ b/docs/PfSense.md @@ -36,3 +36,5 @@ The path `images/pfsense/boot/pxeboot` is relative to TFTP root directory. It's a path to the PXE loader in the extracted PfSense installation image. Unfortunately, there's no mechanism for unattended installation of PfSense. +PfSense documentation doesn't mention this: +https://doc.pfsense.org/index.php/Installing_pfSense