Search results

  1. S

    Proxmox VE and VLAN tag stacking

    No sorry, this was probably too bad of an explanation from my side. Of course I had to install ifupdown2 on every cluster node to be able to migrate the vm in question all over the cluster. And on every single installation the corresponding node booted right after apt-get install. In fact since...
  2. S

    Proxmox VE and VLAN tag stacking

    No it is not. The guest attached to the outer vlan does of course create itself several vlans (the inner ones). And inside these vlans only those arp work that are not used in the host bridge attached to the inner vlan. Believe me that I know a thing or two about networking, and I have already...
  3. S

    Proxmox VE and VLAN tag stacking

    Now we encountered other problems: 1) ARP between the external inner vlan and the newly created bridge does not work, in fact it seems indeed no arp at all works. The guest with its own vlan config (from other bridge) cannot arp to the guest on the inner vlan host bridge and both cannot arp to...
  4. S

    Proxmox 6 Cluster Node Liste

    Ich versuche gerade eine Migration zwischen der fraglichen Node und einer anderen und das ist deutlich langsamer als zwischen anderen Nodes. Das bedeutet dass der Cluster tatsaechlich das 1 GBit/s Interface benutzt. Wie kann ich das aendern?
  5. S

    Proxmox VE and VLAN tag stacking

    PS: I tried to install your ifupdown2 package but shot down a cluster node by doing that. I do not quite understand why it takes down the whole node and restarts just because of this installation ... PS2: After rebooting the node the dual tagged interface came up, which probably means ifupdown2...
  6. S

    Proxmox VE and VLAN tag stacking

    Ok, the double vlan tagged interface definition does not work: # ifup enp5s0f0.1007.8 Error: 8021q: VLAN device already exists. ifup: ignoring unknown interface enp5s0f0.1007.8=enp5s0f0.1007.8
  7. S

    Proxmox VE and VLAN tag stacking

    There are two use-cases by the guests: 1) One type of guest uses the bridged outer vlan and tags the inner vlan itself inside the guest linux 2) Another type of guest uses inner vlan host bridges as simple interfaces to communicate to type 1 guests vlan interface (defined inside the guest) The...
  8. S

    Proxmox VE and VLAN tag stacking

    Hm, which means I would have to hand-configure all inner vlans needed by guests as bridges on every host of the cluster... I guess that's what "vlan-aware" was intended to replace :) Just checked: I have installed: ifupdown/stable,now 0.8.35 amd64 [installed]
  9. S

    Proxmox VE and VLAN tag stacking

    Ok, I can confirm that your second code part works. I tried that. Unfortunately it does not solve the problem. It is the details that are complex: - I need one vlan-aware bridge for guests that should be attached to a single "inner" vlan, basically needing an interface like eth0.1008.25. - On...
  10. S

    Proxmox 6 Cluster Node Liste

    Hallo zusammen, ich frage mich gerade warum ich in einem Cluster mit 3 Nodes fuer eine davon verschiedene IP-Adressen sehe, je nachdem wo man nachsieht. In der GUI unter "Rechenzentrum()" -> Übersicht / Knoten steht fuer eine der Nodes eine andere IP-Adresse als in der Shell erscheint per...
  11. S

    Proxmox VE and VLAN tag stacking

    Hello all, can anyone confirm that VLAN tag stacking works with Proxmox VE and bridging configured as "vlan-aware"? We are trying to make the following work: Many VLANs arrive at the host encapsulated in an outer VLAN 1008. Host bridge is vlan-aware. Guest gets an interface with tag=1008. So...