Recent content by mouk

  1. M

    [SOLVED] resource pools, create vm, network bridge selection

    Ah that works yes! Thanks @d.oishi! I still feel it would also be logical to simply add a network bridge (a resource, much like a storage) to a resource pool, to make it available inside a pool. Anyway: this works, thanks again!
  2. M

    [SOLVED] resource pools, create vm, network bridge selection

    ah right?! I did not know that... I will try and report back!
  3. M

    [SOLVED] resource pools, create vm, network bridge selection

    We're not using the SDN framework, but the 'old style' the bridges, but thanks for the suggestion, both!
  4. M

    [SOLVED] resource pools, create vm, network bridge selection

    Hi, Wondering about resource pools, and resource separation. In our PoC, I created some test resource pools, added users, VMs and some storages to them. Now, when creating a new VM (as a resource pool member) I see correctly the available storages, but in the last step, I do not see any of the...
  5. M

    [FIXED] pve firewall seems to be bypassed..? VM port open, despite not opened in any pve firewall

    Hi Stefan, Thanks for the quick follow-up! Looking at your requested output qm config 3346, I noticed it myself: firewall=1 was missing for the net0 device. After turning it on, the firewall started behaving as expected! Apologies and thanks!
  6. M

    [FIXED] pve firewall seems to be bypassed..? VM port open, despite not opened in any pve firewall

    Note: input policy is set to DROP, on both the DC and the VM level. I have now even created an explicit VM-level DROP-rule for port tcp/5403, and the behaviour has not changed. It seems the firewall rules don't apply for VMs in the same subnet as the pve nodes? (IN DROP -source...
  7. M

    [FIXED] pve firewall seems to be bypassed..? VM port open, despite not opened in any pve firewall

    Hi, Trying to understand something. I created a VM for Qdevice , in the same /24 as my proxmox hypervisors: pve1: 192.168.33.44 pve2: 192.168.33.45 qdevice: 192.168.33.46 I understand from the docs that firewalling on the VM level should still apply, and I have only allowed specific (ssh...
  8. M

    proxmox destroys working /etc/network/interfaces bond config

    Yeah, we reverted now to doing that as well. But vmbr names are now nice and descriptive, and bonds are just numbered. It would be nice to eliminate that restriction.
  9. M

    proxmox destroys working /etc/network/interfaces bond config

    Great! I really hope the limitation will also be lifted for bridges! Thanks for the quick help! :-)
  10. M

    proxmox destroys working /etc/network/interfaces bond config

    Thanks for checking and confirming back. Ok, that's a pity, we would have liked to use meaningful names, including a VLAN identifier. We will have to use the comment field instead. Does the same limitation apply to vmbr? I notice those DO get recognised as bridges in the pve GUI.
  11. M

    proxmox destroys working /etc/network/interfaces bond config

    Yeah I added the bonds manually, not through the GUI. then later I edited something network through the GUI, and then all bond definitions were rewritten. (and broken, so after a reboot, the complete system was unreachable)
  12. M

    proxmox destroys working /etc/network/interfaces bond config

    Hi, To our surprise we see that proxmox rewrites (parts of) the network/interfaces file from this working version: auto MNGT_bond0 iface MNGT_bond0 inet manual bond-miimon 100 bond-mode 802.3ad bond-xmit-hash-policy layer3+4 bond-slaves nic3 bond-lacp-rate fast to this...
  13. M

    tips for shared storage that 'has it all' :-)

    Thanks for all valuable input provided. Much appreciated.