> >> 1. net.ipv4.conf.default.arp_ignore equals 0 (the default) > >> 2. server side bonding/teaming fail-over when the Gratitous ARP sent was > >> lost > >> 3. re-order of ibM net-devices mapping to HCA PCI devices after server > >> boot/crash > >> 4. etc more > >> > >> Basically, when the rdma-cm observes difference between the destination > GID as present in the IB path within the CM REQ to the one resolved > locally, we should at least print a warning. Perhaps, we should reject the > connection request? (in that case, I wasn't sure what would be the > appropriate reject reason), any more ideas? > > I'm not sure that this results in a single error case. > > Sorry... I'm not sure to follow, can you elaborate a bit more?
We don't know what type of device responds to the ARP query. It could come from an ethernet device. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
