Comment 3 for bug 1554950
Revision history for this message
| Divakar Dharanalakota (ddivakar) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
We are hitting the bug:#1550632 while processing arp request in the Destination compute node. 1550632 is fixed so we should not have any more issues further. In the builds where 1550632 is not fixed, GRO has to be disabled for correct ARP functionality to appear. GRO can be disabled like this
echo 0 > /proc/sys/
Root cause:
In the destination compute node, after the bridging, when the ARP request is being handled in L2EncapNh of destination VM, packet is handed over for GRO processing. Post GRO completion, due to a bug in GRO handling, the ingress interface is no more treated at Fabric interface but dest VM's Tap interface. Because of this the ARP response packet is sent to destination VM rather sent as tunneled packet to source VM. Disabling the GRO sends the ARP response packet to source VM. Fix for 1550632 ensures that the ingress interface is retained and hence ARP response travels to right source VM.
-Divakar