Chapter 5.3: Configure ClearOS public IP address
Click on the button Exit to console in the ClearOS VM’s console
Do not insert the password as requested, instead hit the keys ALT + F2
You will be prompted with a standard linux login. Now enter the username root and use the [ClearOS root password]
Type the following command and hit enter
nano /etc/sysconfig/network-scripts/ifcfg-ens18
Edit and add the following lines with these settings
Edit:
BOOTPROTO=static
ONBOOT=yes
Add:
IPADDR=[OVH first additional IP address]
NETMASK=255.255.255.255
GATEWAY=[use the first 3 block of numbers of the OVH main IP address].254
If you followed this tutorial from the beginning, you can find the IP addresses that you need in your OVH server control panel:
This is how it should look:
Save your edits by pressing CONTROL + O (the letter O, not zero) and hit enter, then press CONTROL + X to exit
Type the following command and hit enter
nano /etc/sysconfig/network-scripts/route-ens18
Add the following lines with these settings:
[use the first 3 block of numbers of the OVH main IP address].254 dev ens18
default via [use the first 3 block of numbers of the OVH main IP address].254 dev ens18
This is how it should look:
Save your edits by pressing CONTROL + O (the letter O, not zero) and hit enter, then press CONTROL + X to exit
Poweroff the ClearOS virtual machine in Proxmox
Go back to the OVH IP control panel and click on Add a virtual MAC. Be sure to do so on the same line of the additional IP address you set up before (the one in the file ifcfg-ens18)
Create the new [OVH MAC address] using the name ClearOS (this name is not very important, just avoid duplicates in the future), and use OVH as the type of virtual MAC and click on Confirm
Go back to Proxmox, select the ClearOS VM in the left sidebar and click on Hardware. Then double click on the network device vmbr0
Now in the OVH control panel you should be able to see the [OVH MAC address] you just generated, copy it
Paste the [OVH MAC address] in the correct field in Proxmox (substitute the old one with the new one) and press OK
Start the ClearOS VM
Wait for the VM to boot completely, then point your browser to the address:
https://[OVH first additional IP address]:81
After confirming the certificate security exeption, you should see the ClearOS login page
Hi! I can not access https://[OVH first additional IP address]:81 after following all the steps above. Can you help me? thnks.
Hi Xavi, sure. Is your provider Soyoustart?
I suggest you to start by checking the files /etc/sysconfig/network-scripts/ifcfg-ens18 and /etc/sysconfig/network-scripts/route-ens18.
In the first file be sure that you used the netmask 255.255.255.255. You may be used to a 0 in the last block but this is not the case, it needs to be 255.
If you want you can send the two files to info@hostinstructor.com, we will try to have a look at them as soon as possible.
Another very important thing is to correctly set the generated virtual MAC address in the ClearOS proxmox container’s virtual network card.
Thanks for answering so fast.
I have verified both suggested files and NETMASK ends at 255 and the content of the guide matches the contents of the files.
I have also been able to verify that the VIRTUAL MAC of SouyouStart is the same in both the IP manager and the virtual machine card (vmbr0).
Of course the IP FAILOVER is not accessible from outside
Thank you very much for your help.
Yes, it looks like ClearOS cannot be accessed from outside via failover IP. But can ClearOS access the outside? To check it out try to ping Google from the ClearOS virtual console with this command:
ping google.com
The results should look like this:
64 bytes from 216.58.205.174: icmp_seq=0 ttl=53 time=3.256 ms
64 bytes from 216.58.205.174: icmp_seq=1 ttl=53 time=6.113 ms
64 bytes from 216.58.205.174: icmp_seq=2 ttl=53 time=4.887 ms
64 bytes from 216.58.205.174: icmp_seq=3 ttl=53 time=4.512 ms
If it doesn’t work it means that ClearOS external network via failover IP is not properly configured. I can tell you that the guide works on multiple installations, you just need to look for some mistake in your configurations.
Another thing: notice that the GATEWAY parameter in file /etc/sysconfig/network-scripts/ifcfg-ens18 is composed by the first 3 blocks of the main IP address (the one you use to connect to Proxmox), not the failover IP. For example, if you connect to Proxmox from https://123.456.789.100:8006, your gateway parameter will be 123.456.789.254
Same thing in /etc/sysconfig/network-scripts/route-ens18