New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Doesn't Virtualizor handle IP allocations
Try through ip mac. This method works on vmware, proxmox, vmmanager. I think it will work on the virtualizator.
I’ll try to set up a free server and write an article tomorrow.
I have the IP Pool added but I believe my issue is I have them bound incorrectly. I added the first IP in the range to eth0:0 via the ip alias method. So now the server listens to that IP but when I try and ssh into that IP with a virtual machine on that IP I get an authentication failed message. Neither the node root pass works nor the vps root pass.
Well, I have never used Virtualizor, but I don't think there are any circumstances where you configure the IP on the host? Maybe I am misunderstanding you.
I found this https://docs.ovh.com/gb/en/dedicated/network-bridging/#centos-7 but does it replace the original IP? and do I have to do that step for each IP?
If you want add ovh ip to virtualizor: https://www.virtualizor.com/blog/docs/admin/setup-ovh/
For example there is FO IP: 91.121.8.88
Create a MAC for it and register it on the virtual machine when it is created. For example, in vmware like this: http://vova1234.com/blog/notes/435.html
On the VM itself, make a network:
91.121.8.88
255.255.255.0
91.121.8.254
I haven’t mastered Virtualizator yet, but I know about this panel.
I got it! Not the easiest thing in the world.
For future reference I would follow this guide first https://docs.ovh.com/gb/en/dedicated/network-bridging/#centos-7. Instead of replacing your default ip in the eth0 file I would create a file eth0:0 and proceeding with this guide. Just remember the device name is eth0:0
Then follow this guide thanks to @PremiumFast_Net https://www.virtualizor.com/blog/docs/admin/setup-ovh/
That is wrong.
It may very well work for the short time but configuring your fail overs to the server itself first is wrong.
All you need to do is create a mac for each IP via OVH dashboard.
Then go and create the pool.
The gateway will be your main host IP and change the last digits to 254 e.g 145.xx.xxx.254
Netmask will be 255.255.255.0
Use google nameservers and select routed network.
Once that is done, just add your IP's and the macs to the pool you just created.
That is it.
Do not over complicate it by adding the IPs to the host directly.
EDIT2: Also, if you want a permanent bridge to persist after a reboot, you need to create viifbr0.
For some reason the link took me to adding additional IPs to a OVH server.
https://www.virtualizor.com/docs/admin/kvm-bridge/
The reason I went that route is because when I got the email stating my IP Block after I purchased it stated I needed to add the IP's to the node that way and also create the virtual mac addresses. I just figured it was a weird OVH thing like so many more things out there OVH complicates it. Every host I've even been with before you just assign the IP in Vitualizor, but that wasn't working here.