1
Tutorials and FAQs / Re: Install OpnSense on OVH Public VPS
« on: January 18, 2024, 08:47:20 pm »
With the image size of OPNsense getting larger and the urge to use VPS with a small amount of RAM I have modified the process:
1- Boot the VPS in Rescue mode, it does not matter what OS is installed, it will be wiped in this process
2- Find your VPS hard drive
3- Install and launch netcat
4- On your local laptop or another server, not the VPS. Download the nano image:
8- Set the only interface as the WAN vtnet0 was mine
9- Set the WAN IP to static: xx.xx.xx.xx/24 <-- not /32
10- Log into the shell and set a default route
12- Create a firewall rule that allows you to access the GUI; this will reload the firewall.
This did work on 1GB RAM, I am not sure if it will work on 512MB
1- Boot the VPS in Rescue mode, it does not matter what OS is installed, it will be wiped in this process
2- Find your VPS hard drive
Code: [Select]
fdisk -l ### Should return a line that is near the same size as the VPS disk drive. /dev/sda is typically the rescue disk
/dev/sdb1 227328 41943006 41715679 19.9G Linux filesystem
3- Install and launch netcat
Code: [Select]
apt update && apt install netcat
nc -l -p 19000 | bzip2 -d | dd bs=16M of=/dev/sdb
4- On your local laptop or another server, not the VPS. Download the nano image:
Code: [Select]
cd ~/Downloads
wget https://mirror.ams1.nl.leaseweb.net/opnsense/releases/23.7/OPNsense-23.7-vga-amd64.img.bz2
5- ExtractCode: [Select]
bzip2 -dk OPNsense-23.7-nano-amd64.img.bz2
6- Send the disk image to the serverCode: [Select]
dd bs=16M if=OPNsense-23.7-nano-amd64.img | bzip2 -c | nc xx.xx.xx.xx 19000 ## The public IP of your server
7- Reboot in the OVH control panel and log in via KVM by clicking the three dots in the name square. Log in with: root/opnsense8- Set the only interface as the WAN vtnet0 was mine
9- Set the WAN IP to static: xx.xx.xx.xx/24 <-- not /32
10- Log into the shell and set a default route
Code: [Select]
route add default x.x.x.1
11. Disable the firewall to access the web guiCode: [Select]
pfctl -d
12- Create a firewall rule that allows you to access the GUI; this will reload the firewall.
This did work on 1GB RAM, I am not sure if it will work on 512MB