From: Leon Romanovsky <leon@kernel.org>
To: wangqi <3100102071@zju.edu.cn>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [Discussion] can ROCE protocol work with NAT (Network Address Translation)?
Date: Fri, 10 Jan 2020 21:00:44 +0200 [thread overview]
Message-ID: <20200110190044.GC6871@unreal> (raw)
In-Reply-To: <c663da6a-486e-415e-0687-300239f0f56a@zju.edu.cn>
On Fri, Jan 10, 2020 at 06:51:39PM +0800, wangqi wrote:
> Dear experts,
>
> Because of a project, we need to use ROCE to send data from
>
> region A to region B. A and B are not in a same LAN, and it will
>
> go through NAT (Network Address Translation). However, we found
>
> that we can't send data successfully. We do some investigations
>
> and find that in an INTEL ppt, it says because "ICRC doesn't allow
>
> IP header modifications", ROCE protocol can't work with NAT
>
> while iWARP can work with NAT. We want to ask a few questions.
>
> 1. Can ROCE protocol work with NAT? Is the INTEL ppt right?
I have no idea to which "INTEL ppt" you are referring, but RoCEv2
is an extension of RoCEv1 to support routing over different subnets.
Instead of IB GRH field in RoCEv1 packets, RoCEv2 uses IP and UDP
headers.
>
> 2. Is there any method that we can use to make ROCE work with
>
> NAT? For example, can we modify or remove the ICRC part in the
>
> ROCE protocol? Is it a good idea?a
Use proper hardware that supports RoCEv2.
>
> Best wishes,
>
> Qi
>
>
prev parent reply other threads:[~2020-01-10 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 10:51 [Discussion] can ROCE protocol work with NAT (Network Address Translation)? wangqi
2020-01-10 19:00 ` Leon Romanovsky [this message]
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=20200110190044.GC6871@unreal \
--to=leon@kernel.org \
--cc=3100102071@zju.edu.cn \
--cc=linux-rdma@vger.kernel.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