Recent content by untergeek

  1. U

    Guest container reachability over bridge

    Nope. That just clears the cruft. It does still do it.
  2. U

    Guest container reachability over bridge

    Tentative solution, which does not explain how it got there: Shut down all nodes in the cluster and do a clean reboot. Do an apt update/upgrade to make sure all nodes have the same patch level Reboot again. So far, it seems to be okay.
  3. U

    Guest container reachability over bridge

    This is the output of pveversion -v of all 3 boxes (it's the same): proxmox-ve: 4.4-78 (running kernel: 4.4.35-2-pve) pve-manager: 4.4-5 (running version: 4.4-5/c43015a5) pve-kernel-4.4.6-1-pve: 4.4.6-48 pve-kernel-4.4.35-2-pve: 4.4.35-78 lvm2: 2.02.116-pve3 corosync-pve: 2.4.0-1 libqb0: 1.0-1...
  4. U

    Guest container reachability over bridge

    The storage backend is SSD. The machine is an i7-4790K CPU @ 4.00GHz with 32G of RAM. Other machines in the cluster demonstrate the same behavior. Host: 172.19.73.9 vmbr0 Link encap:Ethernet HWaddr 74:d4:35:e7:6d:4f inet addr:172.19.73.9 Bcast:172.19.73.255 Mask:255.255.255.0...

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!