VM´s and Containers cant access internet, Gateway or Host

[xxlfrosch]

Hello all,

I have a few VM's and containers set up. However, no container or VM can reach the internet.
The PVE host can reach the internet without problems.
For test purposes I had installed a PCI network card, with this the VM's / containers could connect to the internet without problems.
My interfaces are configured as follows.

auto lo
iface lo inet loopback

auto enp9s0
iface enp9s0 inet manual

iface enp4s0f0 inet manual

iface enp4s0f1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.178.102/24
        gateway 192.168.178.1
        bridge-ports enp9s0
        bridge-stp off
        bridge-fd 0

Pinging a Windows VM to the gateway outputs the following:
The 121 is the IP of the VM.

Ping is executed for 192.168.178.1 with 32 bytes of data:
Response from 192.168.178.121: Destination host not reachable.
Request timeout.
Response from 192.168.178.121: Destination host not reachable.
Request timed out.

Ping statistics for 192.168.178.1:
    Packets: Sent = 4, Received = 2, Lost = 2.
    (50% loss),

On an Ubuntu container, the same command looks like this:

ping 192.168.178.1
ping: connect: Network is unreachable

All VM's / containers are configured with DHCP and also get an IP.
The NIC installed on the mainboard is the Intel i 225-V.
Unfortunately, I do not get on with this problem any more, why I turn to you, I hope here someone has a solution.

 

[ph0x]

I would say that if the VMs get an IP address from the DHCP server then there is a connection.
Please shot the output of ip a and ip r of the Ubuntu VM.

 

[xxlfrosch]

Thanks for the fast reply.

the output is as follows:

root@nodeRED:~# ip route show
root@nodeRED:~# ip addr show
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: eth0@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 6e:8b:f3:79:55:98 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::6c8b:f3ff:fe79:5598/64 scope link
       valid_lft forever preferred_lft forever
root@nodeRED:~#

Looks like the Ubuntu VM does not get an IP.
Only the Windows VM.

 

[ph0x]

I can't imagine why a Win VM should get an address and a Linux VM should not. Anyway, I would try the following: assign an IP address manually, set the route manually and try to ping the Proxmox host and then the DHCP server.