Hi,
since quiet a long time there have been problems with the ixgbe driver, VLANs and bondings. Back in time there was a thread about this problem, but I'm unable to find it
The problem seems to be that although a VLAN tagging is configured, packets leave the network interface card untagged, resulting in a total loss of connectivity when a VLAN tag is required to have network connectivity.
First version introducing the problem: pve-kernel-2.6.32-12-pve
The only version known to work: pve-kernel-2.6.32-11-pve
Recently I've tried to upgrade to pve-kernel-2.6.32-17-pve on the affected hosts and noticed that problem still exists.
So I'm wondering, if anybody made any proceedings with the problem? Did anyone report a bug to intel about this?
I know that earlier when that problem popped up, some people decided to manually install the old ixgbe module e.g. via module-assistant.
Is that still the only solution to not get stuck with the old kernel, when affected by this problem?
Best Regards,
Patrick
since quiet a long time there have been problems with the ixgbe driver, VLANs and bondings. Back in time there was a thread about this problem, but I'm unable to find it
The problem seems to be that although a VLAN tagging is configured, packets leave the network interface card untagged, resulting in a total loss of connectivity when a VLAN tag is required to have network connectivity.
First version introducing the problem: pve-kernel-2.6.32-12-pve
The only version known to work: pve-kernel-2.6.32-11-pve
Recently I've tried to upgrade to pve-kernel-2.6.32-17-pve on the affected hosts and noticed that problem still exists.
So I'm wondering, if anybody made any proceedings with the problem? Did anyone report a bug to intel about this?
I know that earlier when that problem popped up, some people decided to manually install the old ixgbe module e.g. via module-assistant.
Is that still the only solution to not get stuck with the old kernel, when affected by this problem?
Best Regards,
Patrick