From owner-freebsd-infiniband@freebsd.org  Thu Aug 18 08:29:46 2016
Return-Path: <owner-freebsd-infiniband@freebsd.org>
Delivered-To: freebsd-infiniband@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E63F4BB620B
 for <freebsd-infiniband@mailman.ysv.freebsd.org>;
 Thu, 18 Aug 2016 08:29:46 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (mail.turbocat.net
 [IPv6:2a01:4f8:d16:4514::2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B293B19F1
 for <freebsd-infiniband@freebsd.org>; Thu, 18 Aug 2016 08:29:46 +0000 (UTC)
 (envelope-from hps@selasky.org)
Received: from laptop015.home.selasky.org (unknown [62.141.129.119])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id EDC131FE022;
 Thu, 18 Aug 2016 10:29:44 +0200 (CEST)
Subject: Re: rdma_bind_addr not allowing wildcarded address?
To: Alex Bowden <alex.bowden@outlook.com>,
 "freebsd-infiniband@freebsd.org" <freebsd-infiniband@freebsd.org>
References: <DM2PR05MB7518450C957991D7F5F5E74F7140@DM2PR05MB751.namprd05.prod.outlook.com>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <363fe77e-a166-27f5-f08c-481b22b3dc58@selasky.org>
Date: Thu, 18 Aug 2016 10:34:14 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <DM2PR05MB7518450C957991D7F5F5E74F7140@DM2PR05MB751.namprd05.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-infiniband@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Infiniband on FreeBSD <freebsd-infiniband.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-infiniband>, 
 <mailto:freebsd-infiniband-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-infiniband/>
List-Post: <mailto:freebsd-infiniband@freebsd.org>
List-Help: <mailto:freebsd-infiniband-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-infiniband>, 
 <mailto:freebsd-infiniband-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2016 08:29:47 -0000

On 08/17/16 19:58, Alex Bowden wrote:
> Hey Hans,
>
> Here's another one. I believe with rdma_bind_addr you do not need to specify an ip?:
>
> ./rping -s -v -d -C 10 -a 192.168.188.6 -p 4420 -P
> count 10
> port 4420
> libibverbs: Warning: couldn't open config directory '/etc/ibverbs/'.
> created cm_id 0x801c37000
> rdma_bind_addr successful
> rdma_listen
>
> ./rping -s -v -d -C 10 -p 4420 -P
> count 10
> port 4420
> libibverbs: Warning: couldn't open config directory '/etc/ibverbs/'.
> created cm_id 0x801c37000
> rdma_bind_addr: Protocol not supported
> destroy cm_id 0x801c37000
>
> I have another app that also tries the same thing and gets back "Protocol not supported." I am using RoCE V1 at the moment on MLX4.
>

Hi,

Do you have a sysctl called "unify_tcp_port_space" ?

sysctl -a | grep unify_tcp_port_space

Try to toggle its value from 1 to 0. Does it make any difference?

--HPS