Thanks for reporting this bug.
Can you confirm that your switch is configured to enable 802.3ad mode?
Would it be possible to confirm that this does not happen with a container? The recipe to create the container would be:
======================= sudo apt-get -y install lxc cat > lxc2.conf << EOF lxc.network.type=veth lxc.network.bridge=brb2 lxc.network.flags=up EOF sudo lxc-create -t ubuntu -n q1 -f lxc2.conf =======================
Then start the container with
sudo lxc-start -n q1
log in on that console with username ubuntu password ubuntu, and run the test from there?
Thanks for reporting this bug.
Can you confirm that your switch is configured to enable 802.3ad mode?
Would it be possible to confirm that this does not happen with a container? The recipe to create the container would be:
======= ======= ======= == type=veth bridge= brb2 flags=up ======= ======= ==
sudo apt-get -y install lxc
cat > lxc2.conf << EOF
lxc.network.
lxc.network.
lxc.network.
EOF
sudo lxc-create -t ubuntu -n q1 -f lxc2.conf
=======
Then start the container with
sudo lxc-start -n q1
log in on that console with username ubuntu password ubuntu, and run the test from there?