VMs and CTs not accesing LAN or Internet in default configuration

[dycral]

Hi,

I'm testing Proxmox with a very basic configuration, a single proxmox node and a container inside the node, but the bridge is not working and the container is not able to communicate to the LAN or Internet. The node has only one NIC and is able to communicate to other devices in the LAN and also is able to reach Internet. The configuration of the node is the default one:



And the etc/network/interfaces file:

auto lo
iface lo inet loopback

iface ens192 inet manual

auto vmbr0
iface vmbr0 inet static
address 10.1.3.65
netmask 255.255.0.0
gateway 10.1.1.1
bridge_ports ens192
bridge_stp off
bridge_fd 0

The ip address for the node is this one:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether 00:0c:29:da:02:41 brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:0c:29:da:02:41 brd ff:ff:ff:ff:ff:ff
inet 10.1.3.65/16 brd 10.1.255.255 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::20c:29ff:feda:241/64 scope link
valid_lft forever preferred_lft forever
7: veth100i0@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether fe:d6:81:af:63:a8 brd ff:ff:ff:ff:ff:ff link-netnsid 0

The configuration of the container is:


And the etc/network/interfaces of the container is:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 10.1.3.75
netmask 255.255.0.0
gateway 10.1.1.1

And the ip address command:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
6: eth0@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 72:37:d5:ce:1e:1c brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 10.1.3.75/16 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::7037:d5ff:fece:1e1c/64 scope link
valid_lft forever preferred_lft forever

Help files are pretty straight forward about how the bridged connection works and how it's configured (including an example of the interfaces file):
https://pve.proxmox.com/wiki/Network_Configuration

I tried different proxmox versions (v6.0 and 6.1) and different configurations (VMs, CTs, single node, 3 nodes, etc) but always the same result, the containers and VMs are not able to reach anything beyond the host.

What I'm missing?

Thkx.

 

[dycral]

Solved, the issue was related to Proxmox running on ESXi (I didn't mention promox is running on ESXi). Changing the vSwitch to promiscuous mode solved the problem.

Here is also an alternative solution:

https://forum.proxmox.com/threads/t...mox-on-esxi-network-problem.37612/post-237106

I chose the promiscuous solution because this is just a test environment and the hosts in production will be running on a physical server.

Thanks.