On Fri, 2009-10-09 at 16:46 -0600, Jason Gunthorpe wrote:
On Fri, Oct 09, 2009 at 02:15:01PM -0700, David J. Wilder wrote:
Yes ping6 will work but I must specify the interface to use:
ping6 fe80::202:c903:1:1925%ib0
Here is the patch to rping to allow the source address to be
On Mon, Oct 12, 2009 at 10:52:59AM -0700, David J. Wilder wrote:
It is not, IPv6 link local addresses must be scoped. rping is
parsing the address with getaddrinfo, that does correctly set the
sin6_scope_id value in the sockaddr.
ping6 is scoping the address (setting sin6_scope_id) by
David J. Wilder dwil...@us.ibm.com wrote:
I added an option to rping to specify a source address and supply it to
patch?
rdma_resolve_addr(), but now it is failing rdma_resolve_route().
$ ./rping -d -c -v -a fe80::202:c903:1:1925 -i fe80::202:c903:1:28ed
cma_event type
On Fri, 2009-10-09 at 22:53 +0200, Or Gerlitz wrote:
David J. Wilder dwil...@us.ibm.com wrote:
I added an option to rping to specify a source address and supply it to
patch?
rdma_resolve_addr(), but now it is failing rdma_resolve_route().
$ ./rping -d -c -v -a fe80::202:c903:1:1925
David J. Wilder dwil...@us.ibm.com wrote:
If I run rping without my rping change to add the source address to
rdma_resolve_address(), ip neigh show gives: fe80::202:c903:1:1925 dev eth1
FAILED
Notice that interface is incorrect, it should be ib0. tcpdump showed the
neighbor-discovery
rdma_resolve_addr (and likely the underlying kernel component) must
respect this when dealing with link local scope addresses.
rmda_resolve_addr should fail if a link local IPv6 address is provided
without scope, like the normal IP stack:
The rdma cm was never fully coded or tested for ipv6
