How to add IP address?

[nbrogi]

I'm extremely confused.

I'm using Proxmox 4.4, and being used to Proxmox 3 I'm unable to make basic things work.

I've created a container, but I'm having problems assigning it an IP address. This is my interface info:



The IP I'm trying to assign is 178.33.101.160.

These are my settings:


Why is it not working? My IP address was correctly assigned to my server (OVH). I have no idea how to fix this, I've tried putting the subnet make in the "Gateway" field, as well as the server's main IP address.

Any help appreciated.

 

[guletz]

And what is the problem? Is your X command do not working? Give a clear sample of your problem / and many details as you can.

 

[nbrogi]

Proxmox gives no error.

I'm just unable to reach the server or login as root after I start the container.

 

[guletz]

The container is created from a proxmox template?
How do you try to make a login?

 

[nbrogi]

Yes, Ubuntu Xenial.

I try to log as the root user via my PC command line. I can also tell by pinging the server that it's not connected to the internet/not responding.

 

[nbrogi]

UPDATE: I was able to connect from Proxmox's GUI. Still no luck remotely. I tried pinging yahoo.com from inside the container, and it just cut out from the outside world.

 

[guletz]

Please try in that container to see how is look:

ip address

 

[nbrogi]

I appreciate your help. Here is what it says:



This is a similar _working_ configuration in Proxmox 3.4:

root@test-01:~# ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/void
inet 127.0.0.2/32 scope host venet0
inet 178.33.101.160/32 scope global venet0:0
​

Is it possibile that it's the template (Ubuntu 16.04 standard) that is wrong? What do people use to install Ubuntu Xenial (I guess the most popular server OS?)?

Thanks!!!

 

[tom]

Did you use this howto?

https://pve.proxmox.com/wiki/OVH

 

[nbrogi]

I didn't!

I didn't know I had to do anything special because of OVH.

Thanks, I'll try following that guide and see if it works.

Will report back.

 

[guletz]

Sorry for my late reply

Another thing, from proxmox node can you ping IP-your-vm ?

And from VM/CT can you run :

traceroute 8.8.4.4

I have a feeling that is only a routing problem

 

[nbrogi]

It might be OVH-related:

Did you use this howto?

https://pve.proxmox.com/wiki/OVH​

 

[guletz]

Do not make assumptions, without facts. Make some checks, and then go forward. All of us we make mistakes. A forum is a place when you can show the facts and your opinion... If you have some luck, someone can show you the solution. In many case good sense are useful. I see many cases when guys who do not use ever the X software was able to give the wright solution

 

[guletz]

It might be OVH-related:

Did you use this howto?

https://pve.proxmox.com/wiki/OVH​

No. I think this is not so useful at least for me. For many years I use something like this, until I discover ospf(dynamic routing). So I start to use switches who can speak ospf. For me ospf can solve almost any routing problem I can create any VM / PVE, without care about... how can I route this IP? But what is ok for me, maybe could be bad for others.

 

[nbrogi]

Did you use this howto?

https://pve.proxmox.com/wiki/OVH

Thanks (to everyone, but you in particular ). The problem was indeed that the VM wasn't connected to the outside world, and the reason was that with OVH you have to create a virtual MAC address from the control panel, and then tell Proxmox what it is.

I'm now able to ping the machine.

Thanks!!!