Search results

I did that and saw icmp packets but not leaving. turns out an iptables forward chain was set to deny. Not sure why that happened.

weird. I spun up a quick container, from the host I can ping the container root@pve1:~# ping 192.168.200.41 PING 192.168.200.41 (192.168.200.41) 56(84) bytes of data. 64 bytes from 192.168.200.41: icmp_seq=1 ttl=64 time=0.032 ms 64 bytes from 192.168.200.41: icmp_seq=2 ttl=64 time=0.032 ms 64...

it appears the bridge is forwarding root@pve1:~# brctl showstp vmbr1 vmbr1 bridge id 8000.00259049ecc9 designated root 8000.00259049ecc9 root port 0 path cost 0 max age 20.00 bridge max...

It was working fine. The gateway is only set on one. So get rid of one of the bridges?

default via 192.168.200.252 dev vmbr1 onlink 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev docker_gwbridge proto kernel scope link src 172.18.0.1 192.168.200.0/24 dev vmbr0 proto kernel scope link src 192.168.200.90 192.168.200.0/24 dev vmbr1...

The network to the node is up and I can ssh into the node, but cannot get to a vm and a vm cannot get out.

Everything was working and now it doesn't. I have the following bridges: auto lo iface lo inet loopback iface enp5s0f0 inet manual iface enp5s0f1 inet manual auto vmbr0 iface vmbr0 inet static address 192.168.xx.x0 netmask 255.255.255.0 gateway 192.168.xx.x253 bridge-ports...

Hello all, I'm pretty new to Proxmox and KVM/OpenVZ in general. When I log into teh web interface I get alerts that the node is offline sometimes. I can still access the consoles from the web gui on both KVM guests and OpenVZ containers but I can't create new images or guests. A rebbot of the...