All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Need help with proxmox networking on a nocix server
Hello, I'm in read need of desperate help, because it seems like I have tried out everything possible. I'm trying to create a VM using proxmox and attach one of the IPs that nocix has provided so I could connect to the VM via ssh.
I have tried a multitude of different solutions, so I'll provide one of them so you perhaps could point out what am I doing wrong.
I have debian jessie and have installed proxmox using this guide: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie
Let's say my proxmox host IP is
xxx.yyy.zzz.130
And the IP I'm trying to map to one of my VMs is
xxx.yyy.zzz.131
My configs look like this:
HOST config:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth1
iface eth1 inet static
address xxx.yyy.zzz.130
netmask 255.255.255.248
network xxx.yyy.zzz.128
broadcast xxx.yyy.zzz.135
gateway xxx.yyy.zzz.129
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 127.0.0.1
dns-search nocix.net
auto vmbr0
iface vmbr0 inet static
address xxx.yyy.zzz.130
netmask 255.255.255.248
gateway xxx.yyy.zzz.129
bridge_ports eth1
bridge_stp off
bridge_fd 0
Then I install debian jessie on the VM. I use NAT for the whole installation so I can atleast get to the UI of the OS, and then I change the network device from NAT to the vmbr0 bridge that is created. I config the VM as well, but it just doesn't work then, the connection keeps saying "connecting" and that's it.
VM config:
auto lo
iface lo inet loopback
auto eno0
iface eno0 inet static
address xxx.yyy.zzz.131
netmask 255.255.255.248
gateway xxx.yyy.zzz.129
I have tried both 129 and 130 as the gateway on the VM.
I feel like I'm out of options and I just can't get it rolling.
Any help is appreciated, thanks!
Comments
Your config is wrong. Really wrong.
On the host you need device set it to something like:
Restart server.
Do I have to delete all the eth1 setting up stuff or you just left it out?
I do not have any eth1 settings in my config at all.
https://pve.proxmox.com/wiki/Network_Configuration
Still no signs of life. Do you use nocix as well? Or some other provider? And also, do you change the interfaces file on the VM (if so, is it similar to what I've shown), or do you keep it as it is and switch the settings elsewhere?
Thank you very much!
I currently have a colo with Nocix. I am also running Proxmox on that server.
I am using the exact config I posted above on that server.
My VM config is very similar to yours.
From the Proxmox server can you ping the VM?
ping x.x.x.131
Oh... In your example the netmask was .240 and mine is .248, all I had to do is change it and fiddle some more on the VM OS (had to select the correct ethernet device to use), and now the IP appears to be the one that I want! It also responds for pings from outside, so now I'll just try setting up ssh. Thank you a lot!!!
Also, what do you do if you want to create a 2nd VPS with a different IP? Same bridge but the VM config has the different IP and that's it?
Bridge is basically your proxmox acting as a hardware switch. eth1 is shared and thus no IP address should be set, and proxmox box uses vmbr0 as its port.
All your VMs will have a NIC connecting to vmbr0 as if you plug the cable into a switch. Now the only thing you need to do, is to set a different IP on the guest, with the same netmask and gateway as the host.
What happens now is:
My first VM with .131 IP works and pinging it works as well.
I set up a second VM, added the same bridge with .132 (it is a part of the network).
Now the second VM doesn't load any websites, but the IP itself pings back from my own PC (not the proxmox host), so I guess it kind of is connected to the internet, but not fully.
So it's probably a configuration error on the VM and not the host?
Possibly firewall, or issue on the VM.