Leo Tominna wrote:
This patch appears to help when strict ARP handling is enabled or when non-standard routing tables are used. The ARP request is replied to through the device that will be used for subsequent communication, so the ARP entry gets associated with the correct device in the ARP cache. tcpdump shows consistent ARPs generated by similar arguments to ping and rds-ping.
Hi Loe,
Does this patch comes to solve the problem discussed over the "pick the outgoing HCA based on the IP used for bind" threads dated to February this year at the general and rds-devel mailing lists (http://lists.openfabrics.org/pipermail/general/2009-February/057008.html)? also by "strict ARP handling" do you refer to the case where there are multiple NICs on the same L2 broadcast domain (VLAN/Partition)?
Or. _______________________________________________ general mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
