Auto-update blog content from Obsidian: 2025-09-23 08:48:08
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 6s
Blog Deployment / Build (push) Has been skipped
Blog Deployment / Deploy-Staging (push) Successful in 10s
Blog Deployment / Test-Staging (push) Successful in 2s
Blog Deployment / Merge (push) Successful in 7s
Blog Deployment / Deploy-Production (push) Successful in 11s
Blog Deployment / Test-Production (push) Successful in 3s
Blog Deployment / Clean (push) Has been skipped
Blog Deployment / Notify (push) Successful in 3s

This commit is contained in:
Gitea Actions
2025-09-23 08:48:08 +00:00
parent 6c2856e935
commit e0d7ec4bde
5 changed files with 17 additions and 6 deletions

View File

@@ -49,7 +49,7 @@ Before rushing into a migration, I want to experiment the high availability setu
1. Add some VLANs in my Homelab 1. Add some VLANs in my Homelab
2. Create Fake ISP box 2. Create Fake ISP box
3. Build two OPNsense VMs 3. Build two OPNsense VMs
4. Configure the high availabilty 4. Configure high availability
5. Create another client VM 5. Create another client VM
6. Shutdown the active OPNsense node 6. Shutdown the active OPNsense node
7. See what happen! 7. See what happen!
@@ -135,15 +135,15 @@ I create the first VM from that node which I name `poc-opnsense-1`:
- 2 vCPU with 2048 MB of RAM - 2 vCPU with 2048 MB of RAM
- I select the VLAN 101 (POC WAN) for the NIC* - I select the VLAN 101 (POC WAN) for the NIC*
- Once the VM creation wizard is finished, I add a second NIC in the VLAN 102 (POC LAN) - Once the VM creation wizard is finished, I add a second NIC in the VLAN 102 (POC LAN)
- ![[proxmox-create-poc-vm-opnsense.png]] ![proxmox-create-poc-vm-opnsense.png](img/proxmox-create-poc-vm-opnsense.png)
Before starting it, I clone this one to prepare the next one: `poc-opnsense-2` Before starting it, I clone this one to prepare the next one: `poc-opnsense-2`
Booting fails, I disabled secure boot: Now I can start the VM, but the boot fails with an access denied. I enter the BIOS, navigate to Device Manager > Secure Boot Configuration, there I uncheck the `Attempt Secure Boot` option and restart the VM:
![Pasted_image_20250922145822.png](img/Pasted_image_20250922145822.png) ![proxmox-disable-secure-boot-option.png](img/proxmox-disable-secure-boot-option.png)
The VM finally boots on the ISO, I don't touch anything until I get into that screen: Now the VM boots on the ISO, I touch nothing until I get into that screen:
![opnsense-vm-installation-welcome.png](img/opnsense-vm-installation-welcome.png) ![opnsense-vm-installation-welcome.png](img/opnsense-vm-installation-welcome.png)
I enter the installation mode using the user `installer` and password `opnsense`. I select the French keyboard and select the `Install (UFS)` mode. I have a warning about RAM space but I proceed anyway. I enter the installation mode using the user `installer` and password `opnsense`. I select the French keyboard and select the `Install (UFS)` mode. I have a warning about RAM space but I proceed anyway.
@@ -160,4 +160,15 @@ I select the option 1 to assign interfaces, as the installer inverted them for m
![opnsense-vm-installation-assign-interfaces.png](img/opnsense-vm-installation-assign-interfaces.png) ![opnsense-vm-installation-assign-interfaces.png](img/opnsense-vm-installation-assign-interfaces.png)
Now my WAN interface is getting the IP address 10.101.0.150/24 from my `fake-freebox` VM. Then I configure the LAN interface with `10.102.0.2/24` and configure a DHCP pool from `10.102.0.10` to `10.102.0.99`: Now my WAN interface is getting the IP address 10.101.0.150/24 from my `fake-freebox` VM. Then I configure the LAN interface with `10.102.0.2/24` and configure a DHCP pool from `10.102.0.10` to `10.102.0.99`:
![opnsense-vm-installation-interfaces-configured.png](img/opnsense-vm-installation-interfaces-configured.png) ![opnsense-vm-installation-interfaces-configured.png](img/opnsense-vm-installation-interfaces-configured.png)
✅ The first VM is ready, I start over for the second OPNsense VM, `poc-opnsense-2` which will have the IP `10.102.0.3`
### Configure High Availability
![Pasted_image_20250922202056.png](img/Pasted_image_20250922202056.png)
![Pasted_image_20250922202211.png](img/Pasted_image_20250922202211.png)

Binary file not shown.

After

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 56 KiB

View File

Before

Width:  |  Height:  |  Size: 40 KiB

After

Width:  |  Height:  |  Size: 40 KiB