Re: rping is not resolving ipv6 addresses

2009-10-11 Thread Or Gerlitz
Sean Hefty wrote: > The rdma cm was never fully coded or tested for ipv6 support. Sean, even if not fully coded/tested, some work has been done, e.g commits 38617c64 "RDMA/addr: Add support for translating IPv6 addresses" and 1f5175ad "RDMA/cma: Add IPv6 support". I suggest we'll try to see what

Re: rping is not resolving ipv6 addresses

2009-10-11 Thread Jason Gunthorpe
On Sun, Oct 11, 2009 at 09:29:08AM +0200, Or Gerlitz wrote: > Sean Hefty wrote: > > The rdma cm was never fully coded or tested for ipv6 support. > Sean, even if not fully coded/tested, some work has been done, e.g > commits 38617c64 "RDMA/addr: Add support for translating IPv6 > addresses" and 1

Re: [ewg] rping is not resolving ipv6 addresses

2009-10-09 Thread Or Gerlitz
David J. Wilder 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 RDMA_CM_EVENT_ADDR_RESOLVED cma_id 0

Re: [ewg] rping is not resolving ipv6 addresses

2009-10-09 Thread David J. Wilder
On Fri, 2009-10-09 at 22:53 +0200, Or Gerlitz wrote: > David J. Wilder 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::2

Re: [ewg] rping is not resolving ipv6 addresses

2009-10-09 Thread Or Gerlitz
David J. Wilder 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 sent out the eth0

Re: [ewg] rping is not resolving ipv6 addresses

2009-10-09 Thread Jason Gunthorpe
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 specified. > I am not sure this is the correct approach to fix this.

RE: [ewg] rping is not resolving ipv6 addresses

2009-10-09 Thread Sean Hefty
>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

Re: [ewg] rping is not resolving ipv6 addresses

2009-10-12 Thread David J. Wilder
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

Re: [ewg] rping is not resolving ipv6 addresses

2009-10-12 Thread Jason Gunthorpe
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