Debian 8.0 - Configuration of the network problem, is it broken?

Potar

New Member
May 6, 2015
3
0
1
Hey, I am not sure if the Debian 8.0 is supported by the Proxmox, I am new with proxmox as well on that point I would like to say hello everyone, I was using only the VMware and templates so this is something new for me to learn about the network etc.

Problem is that I have installed new VM, I run a debian 8.0 netinst on it, installed everything (minimal version), and the problem is after setting the network which is /etc/network/interface, there is no network to the internet from the VM, ping shows that there is no network or cannot reach the host.

I am adding the logs and screens from the console, if you would help me with that that would be great.

Server Proxmox ip -a:

Code:
[B]Serwer PROXMOX:[/B][B]root@ns395961:~# ip a[/B]
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 [URL="http://127.0.0.1/8"]127.0.0.1/8[/URL] scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:22:4d:7a:39:e1 brd ff:ff:ff:ff:ff:ff
3: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether 12:42:1b:87:fb:c3 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::1042:1bff:fe87:fbc3/64 scope link
       valid_lft forever preferred_lft forever
4: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether 12:42:1b:87:fb:c3 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::1042:1bff:fe87:fbc3/64 scope link
       valid_lft forever preferred_lft forever
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether 00:22:4d:7a:39:e1 brd ff:ff:ff:ff:ff:ff
    inet [URL="http://176.31.121.138/24"]176.31.121.138/24[/URL] brd 176.31.121.255 scope global vmbr0
    inet6 2001:41d0:8:408a::1/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::222:4dff:fe7a:39e1/64 scope link
       valid_lft forever preferred_lft forever
6: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/void
    inet6 fe80::1/128 scope link
       valid_lft forever preferred_lft forever
11: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 500
    link/ether b2:21:c0:5f:b2:89 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::b021:c0ff:fe5f:b289/64 scope link

       valid_lft forever preferred_lft forever

Pings from server proxmox to the VM:

Code:
root@ns395961:~# ping 192.168.56.255
PING 192.168.56.255 (192.168.56.255) 56(84) bytes of data.
From 91.121.131.189 icmp_seq=1 Time to live exceeded
From 91.121.131.189 icmp_seq=2 Time to live exceeded
^C
--- 192.168.56.255 ping statistics ---
2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1000ms
 
root@ns395961:~# ping 192.168.56.254
PING 192.168.56.254 (192.168.56.254) 56(84) bytes of data.
From 37.187.36.211 icmp_seq=1 Time to live exceeded
From 37.187.36.211 icmp_seq=2 Time to live exceeded
^C
--- 192.168.56.254 ping statistics ---
2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1001ms
 
root@ns395961:~# ping 192.168.56.101
PING 192.168.56.101 (192.168.56.101) 56(84) bytes of data.
From 91.121.215.145 icmp_seq=1 Time to live exceeded
From 91.121.215.145 icmp_seq=2 Time to live exceeded
^C
--- 192.168.56.101 ping statistics ---
2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1000ms

VM route -n and interface, arp:

SmnvxWL.png




Settings in proxmox via website GUI:


Ut24gdk.png

HxoYCd1.png


The VM is pinging itself fine, so the IP adress and MAC address is set well.

There is also output of ifconfig of the VM:

AFCmzZj.png


Does anyone know how can I fix it?
That the VM will be able to connect the internet?

Regards,

Potar
 
So how should I handle this?

If the
176.31.121.X is a Kimsufi's IP (and that part have been set by the kimsufi as well, this is a dedicated server). and I have no any additionals IP's.

How can I resolve the problem?
 
Thats no sense, there has to be a different way to get internet access on the VM, instead of making VLAN.
Should not be done this by the proxmox by default?

For example virtualbox, while creating new machine, it assign the correct settings that the network is reachable.
 
So how should I handle this?

If the
176.31.121.X is a Kimsufi's IP (and that part have been set by the kimsufi as well, this is a dedicated server). and I have no any additionals IP's.

How can I resolve the problem?
Hi,
with only one IP you can't use the bridged mode for the VM! Use the NAT-Mode instead.

See here http://pve.proxmox.com/wiki/Network_Model

Udo
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!