From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Stephen Bates <sbates-pv7U853sEMVWk0Htik3J/w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Logan Gunthorpe <logang-OTvnGxWRz7hWk0Htik3J/w@public.gmane.org>,
Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>,
Max Gurtovoy <maxg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [linux-rdma and rdma-core]: Unable to perform rdma_connect in loopbacked configuration
Date: Mon, 18 Sep 2017 14:59:59 -0600 [thread overview]
Message-ID: <20170918205959.GC7059@obsidianresearch.com> (raw)
In-Reply-To: <59792242-F2C8-431A-BEDA-996844EDE4C5-pv7U853sEMVWk0Htik3J/w@public.gmane.org>
On Mon, Sep 18, 2017 at 06:18:25PM +0000, Stephen Bates wrote:
> Using a NAT approach discussed in [1] I can setup IPv4 addresses on
> both HCAs such that I avoid a local loopback (the addresses I use
> are a little different to the ones in that reference but the
> approach is identical). This allows ping, iperf and other IP based
> applications to work just fine. For example:
The RDMA stuff ignores everything in iptables.
IIRC, you need to make 'ip route get blah' not return lo. This is done
with some combination of policy routing and sysfs tweaking.
IMHO, it is also a bug if loopback roce doesn't just work out of the
box, fully internally to the NIC. :\
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-09-18 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 18:18 [linux-rdma and rdma-core]: Unable to perform rdma_connect in loopbacked configuration Stephen Bates
[not found] ` <59792242-F2C8-431A-BEDA-996844EDE4C5-pv7U853sEMVWk0Htik3J/w@public.gmane.org>
2017-09-18 19:09 ` Parav Pandit
[not found] ` <VI1PR0502MB3008FAC205874147558EA241D1630-o1MPJYiShExKsLr+rGaxW8DSnupUy6xnnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-09-18 19:41 ` Stephen Bates
2017-09-19 3:51 ` Leon Romanovsky
[not found] ` <20170919035134.GH5788-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-09-19 6:13 ` Parav Pandit
2017-09-18 20:59 ` Jason Gunthorpe [this message]
[not found] ` <20170918205959.GC7059-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-09-19 1:11 ` Stephen Bates
[not found] ` <AB27E7A4-FD5A-438E-A0CF-E593882F5EAE-pv7U853sEMVWk0Htik3J/w@public.gmane.org>
2017-09-20 16:28 ` Jason Gunthorpe
[not found] ` <20170920162828.GC536-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-09-26 20:52 ` Stephen Bates
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170918205959.GC7059@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=logang-OTvnGxWRz7hWk0Htik3J/w@public.gmane.org \
--cc=maxg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org \
--cc=sbates-pv7U853sEMVWk0Htik3J/w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox