I added Rodolfo to this bug, hopefully he can add more information from the IRC discussion.
Sean's comment in the related bug:
its not that ageing prevents the vm receiving the packet.
it worked without ageing because the unicast packets were bing flooded
so that is why it "works" with ageing disabled. based on our irc conversation i think
the flooding was masking a different proablem in the linux bridge agent where it was/is
incorrectly setting entries in the bridge fdb against the vlan interface instead of the tap
From that it looks like a bug in the agent code, I just can't confirm it.
I added Rodolfo to this bug, hopefully he can add more information from the IRC discussion.
Sean's comment in the related bug:
its not that ageing prevents the vm receiving the packet.
it worked without ageing because the unicast packets were bing flooded
so that is why it "works" with ageing disabled. based on our irc conversation i think
the flooding was masking a different proablem in the linux bridge agent where it was/is
incorrectly setting entries in the bridge fdb against the vlan interface instead of the tap
From that it looks like a bug in the agent code, I just can't confirm it.