Search results

This is fixed in: ii pve-kernel-4.4.13-1-pve 4.4.13-56 amd64 The Proxmox PVE Kernel Image

In the network interface properties of the VM. I attached an image from the VM creation window.

It's the same thing Only vlan 10 (native vlan) will be sent untagged, all the other vlans will be sent tagged. In the proxmox interface you just need to set the VMs interface to use the specified tag.

Hi Geezer, You can leave the proxmox config as-is and configure native vlan on the switch side. (switchport trunk native vlan 10) This will instruct the switch to send the packets for vlan 10 without tag (and also packets received without tag will be put into vlan 10). The packets for the rest...

No, this is a semi-production machine and I did not want to risk with a vanilla kernel. Instead I did an "git clone git://git.proxmox.com/git/pve-kernel.git", added the patch to the Makefile, rebuilt the pve-kernel deb package, install it as usual and just rebooted the machine. Now the...

This patch (integrated into 4.4.11 longterm kernel) should fix my issue: https://lists.linuxfoundation.org/pipermail/bridge/2016-May/009976.html I already have a querier in the network so it made no sense to also enable it on the linux bridge. If I enable the multicast querier the information...

Oh, ok, thank you for clearing that up (I should have thought to test that myself) :) I will dig deeper to find out what patches landed in the linux multicast area during 3.x and 4.x. I would call it a bug, a regression even, the sysfs knob does not do what it supposed to while during 2.6.x it...

Heya Richard, Thank you very much for testing. Maybe I did not explain correctly. Indeed, also in my case the mdb looks ok but the multicast packets get duplicated to all the interfaces in the bridge, even to the interfaces that did not specifically asked for them (joined the multicast group)...

Hello, I just updated my proxmox install from 3.4 (kernel 2.6.32-pve) and 4.2 (kernel 4.4.8-pve) and it looks like igmp snooping on bridges stopped working. It's enabled in the config but it looks like it's not doing what it's supposed to do. I have two VMs connecting to the multicast source...