Container network connectivity

ICENINE

New Member
May 10, 2017
3
0
1
26
So I have a proxmox server running 4.4 (let's say at 172.16.16.16), and on it are several containers. I can get these containers networked if I set them up using NAT via iptables MASQUERADE, however if i try to bridge them to the host to use the same subnet they cannot ping out and I cannot ping them from other devices on the network, yet from the proxmox server can ping the address of the container (say 172.16.16.18) and get a response. I have below my /etc/network/interfaces of the host and the /etc/network/interfaces of the container.

Host interfaces:
Code:
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 172.16.16.16
        netmask 255.255.255.0
        gateway 172.16.16.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

Guest interfaces:
Code:
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address 172.16.16.18
        netmask 255.255.255.0
        gateway 172.16.16.1
 
Last edited:
the container gateway on bridged network should be same as hosts "gateway 172.16.16.1"
It normally is, I had it set to the host to see if that would have any effect. Upon setting it to the host there is no change in connectivity.
 
I have found that if host nic is not in promiscuous mode the VMs have no connectivity.

try running "ifconfig eth0 promisc" on Host. !! this is for the NIC card it self, not for bridge.

BTW is your host setup on real hardware? this is not one of the nested configs?
 
I have found that if host nic is not in promiscuous mode the VMs have no connectivity.

try running "ifconfig eth0 promisc" on Host. !! this is for the NIC card it self, not for bridge.

BTW is your host setup on real hardware? this is not one of the nested configs?

The proxmox server itself is a VM in a datacenter. Enabling promiscuous mode had no effect, however I'm asking the hosting provider if the vsphere is set up to allow for what I'm trying to do
 
that will not work, when I said it must be NIC it must be NIC on the datacenter configured not nic in VM.

since is is VMware host, it needs to configure the nic of your Proxmox VM to be in promiscuous mode and to allow MAC spoofing.
I am assuming the hardware is setup to allow this, since it is a datacenter.
 

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!