Order at least a block of 8 IPs (/29) or a block of 16 IPs (/28). Go back to your OVH/SoYouStart control panel and order some IPs for this server. $ vi /etc/newtork/interfacesīe sure to create some type of fallback in case something goes wrong (like you are used to do with firewall, if you configure it remotely). My private subnet will be 10.1.100.0/24, so I have reserved 10.1.100.1 for the KVM router and 10.1.100.254 for the vmbr2 on the server.Įdit /etc/networking/interfaces and add your private subnet virtual bridge (vmbr2). It is system administrator’s choice of router software, so one could go for the great piece of open source software pfSense, but this time I choose Mikrotik‘s RouterOS (for x86) since I am using it with Mikrotik routers for a few years now and I am very familiar with it. The goal was to configure server in the way the virtual machines running on this server will use private subnet and will be accessible via router (NAT), which runs in one of the KVM machines. So my Proxmox was configured with a gateway of Server.254 (on interface vmbr0). OVH instructs to configure networking using a gateway which is first three octets of Server.IP and the last octet is. In this article I will use Server.IP as a reference to my Proxmox server IP address. Proxmox VE enables you to use two types of virtualization at the same time: OpenVZ containers and KVM.Īfter my dedicated server setup has finished, an email was received with IP and root login information to access my Proxmox VE shell. When I rented a dedicated server at SoYouStart ( OVH‘s brand) in early 2015, I choose to install it with Proxmox VE 3.4.
0 kommentar(er)
