pfsense:install_pfsense:installation_of_pfsense
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
pfsense:install_pfsense:installation_of_pfsense [2020/11/30 16:12] – created peter | pfsense:install_pfsense:installation_of_pfsense [2023/04/21 22:07] (current) – [Determine Networks] peter | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== PFSense - Install pfSense - Installation of pfSense ====== | ====== PFSense - Install pfSense - Installation of pfSense ====== | ||
+ | |||
+ | ===== Download pfSense image ===== | ||
+ | |||
+ | Go to https:// | ||
+ | |||
+ | {{: | ||
+ | |||
+ | <WRAP info> | ||
+ | **NOTE: | ||
+ | |||
+ | * Architecture: | ||
+ | * Installer: | ||
+ | * Console: | ||
+ | |||
+ | Choose different options as required. | ||
+ | </ | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Burn the pfSense image on to a USB drive ===== | ||
+ | |||
+ | <code bash> | ||
+ | sudo dd if=pfSense-CE-memstick-2.4.5-RELEASE-amd64.img of=/dev/sdb | ||
+ | </ | ||
+ | |||
+ | <WRAP alert> | ||
+ | **ALERT**: | ||
+ | |||
+ | If you make a mistake here, you might overwrite your hard drive! | ||
+ | |||
+ | There are many ways to check which device is connected to the USB including: | ||
+ | |||
+ | < | ||
+ | dmesg | ||
+ | </ | ||
+ | |||
+ | returns: | ||
+ | |||
+ | <code bash> | ||
+ | ... | ||
+ | [411849.265872] usb 3-2: new high-speed USB device number 6 using xhci_hcd | ||
+ | [411849.418209] usb 3-2: New USB device found, idVendor=048d, | ||
+ | [411849.418210] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 | ||
+ | [411849.418211] usb 3-2: Product: Disk 2.0 | ||
+ | [411849.418212] usb 3-2: Manufacturer: | ||
+ | [411849.418212] usb 3-2: SerialNumber: | ||
+ | [411849.418481] usb-storage 3-2:1.0: USB Mass Storage device detected | ||
+ | [411849.418603] scsi host12: usb-storage 3-2:1.0 | ||
+ | [411850.422697] scsi 12:0:0:0: Direct-Access | ||
+ | [411850.422989] sd 12:0:0:0: Attached scsi generic sg1 type 0 | ||
+ | [411850.423703] sd 12:0:0:0: [sdb] 3891200 512-byte logical blocks: (1.99 GB/1.86 GiB) | ||
+ | [411850.423817] sd 12:0:0:0: [sdb] Write Protect is off | ||
+ | [411850.423819] sd 12:0:0:0: [sdb] Mode Sense: 03 00 00 00 | ||
+ | [411850.423936] sd 12:0:0:0: [sdb] No Caching mode page found | ||
+ | [411850.423941] sd 12:0:0:0: [sdb] Assuming drive cache: write through | ||
+ | [411850.426796] | ||
+ | sdb2: <bsd: sdb5 > | ||
+ | [411850.427528] sd 12:0:0:0: [sdb] Attached SCSI removable disk | ||
+ | </ | ||
+ | |||
+ | In this example, the device is shown as **sdb**. | ||
+ | </ | ||
+ | |||
+ | <WRAP info> | ||
+ | **NOTE: | ||
+ | |||
+ | For creating a bootable USB with a Mac, try Etcher: https:// | ||
+ | </ | ||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Verify the BIOS settings for Booting ===== | ||
+ | |||
+ | Ensure BIOS is set to boot from USB. | ||
+ | |||
+ | While powering up the device, press the **DEL** key and verify that it boots to the BIOS. | ||
+ | |||
+ | <WRAP info> | ||
+ | **NOTE: | ||
+ | </ | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Verify the BIOS settings for Power Cuts ===== | ||
+ | |||
+ | Make sure the power state is set to **ON** after a power cut. | ||
+ | |||
+ | <WRAP info> | ||
+ | **NOTE: | ||
+ | </ | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Boot from the USB ===== | ||
+ | |||
+ | Connect USB drive. | ||
+ | |||
+ | Start the router device. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | <WRAP info> | ||
+ | **NOTE: | ||
+ | </ | ||
+ | |||
+ | |||
+ | <WRAP info> | ||
+ | **NOTE:** An alternative to booting up from USB is to connect using a Console Cable. | ||
+ | |||
+ | See: [[PFSense: | ||
+ | |||
+ | </ | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Determine Networks ===== | ||
+ | |||
+ | By default, only 2 networks will be set up. WAN and LAN. | ||
+ | |||
+ | < | ||
+ | WAN (wan) -> igb0 -> DHCP | ||
+ | LAN (lan) -> igb1 -> v4: 192.168.1.1/ | ||
+ | </ | ||
+ | |||
+ | <WRAP info> | ||
+ | **NOTE: | ||
+ | |||
+ | The second NIC will be configured as your local LAN interface at 192.168.1.1. | ||
+ | |||
+ | |||
+ | </ | ||
+ | |||
+ | <WRAP tip> | ||
+ | **TIP: | ||
+ | |||
+ | There is a DHCP server running on the LAN interface so if you connect your PC to this port, you should be able to obtain an IP address which will allow you to access the pfSense web configurator to continue the configuration process. | ||
+ | |||
+ | </ | ||
+ | |||
+ | |||
+ | <WRAP info> | ||
+ | **Optional: | ||
+ | |||
+ | * Assign Interfaces | ||
+ | * No VLANs | ||
+ | * WAN, Autodetect, Plug the WAN (PPPoE modem) cable into the onboard network socket, Press enter | ||
+ | * LAN, Autodetect, Plug the LAN cable into the top socket (port 0) on the Intel low profile NIC, press enter | ||
+ | * Add no more | ||
+ | * Accept settings | ||
+ | * Set Interface(s) IP address | ||
+ | * Set LAN | ||
+ | * IPv4 = 192.168.1.1 | ||
+ | * Subnet: 24 (255.255.255.0) | ||
+ | * No LAN IPv6 (enable at a later date) | ||
+ | * Enable DHCP on LAN | ||
+ | * Client address range = 192.168.1.100 --> 192.168.1.199 | ||
+ | * Do you want to revert to HTTP as the webConfigurator protocol? | ||
+ | * Currently the web-server is using HTTPS and this is asking if you want to downgrade to HTTP | ||
+ | * Select No | ||
+ | |||
+ | </ | ||
+ | |||
+ | ---- | ||
+ | |||
+ | Return to [[PFSense: | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== References ===== | ||
+ | |||
+ | https:// | ||
pfsense/install_pfsense/installation_of_pfsense.1606752748.txt.gz · Last modified: 2020/11/30 16:12 by peter