From: "Bernard Metzler" <BMT@zurich.ibm.com>
To: "Benjamin Coddington" <bcodding@redhat.com>
Cc: "Chuck Lever" <chuck.lever@oracle.com>,
"linux-rdma" <linux-rdma@vger.kernel.org>
Subject: RE: directing soft iWARP traffic through a secure tunnel
Date: Fri, 12 Feb 2021 15:26:29 +0000 [thread overview]
Message-ID: <OF6479A795.E0C17A4D-ON0025867A.0054D29B-0025867A.0054D2A4@notes.na.collabserv.com> (raw)
In-Reply-To: <42736765-35DA-454E-AF9B-0484D98C821A@redhat.com>
-----"Benjamin Coddington" <bcodding@redhat.com> wrote: -----
>To: "Bernard Metzler" <BMT@zurich.ibm.com>
>From: "Benjamin Coddington" <bcodding@redhat.com>
>Date: 02/12/2021 02:27PM
>Cc: "Chuck Lever" <chuck.lever@oracle.com>, "linux-rdma"
><linux-rdma@vger.kernel.org>
>Subject: [EXTERNAL] Re: directing soft iWARP traffic through a secure
>tunnel
>
>On 12 Feb 2021, at 8:19, Bernard Metzler wrote:
>
>> How does this tunnel device look like? What does
>> ifconfig or ip show? Probably NOARP and no
>> HW address?
>
>right:
>
># ip link show tun0
>3: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc
>fq_codel state UNKNOWN mode DEFAULT group default qlen 500
>
># ifconfig tun0
>tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
> inet6 fe80::6bbf:1def:b134:2eef prefixlen 64 scopeid
>0x20<link>
> inet6 fd51:5f56:d79b:a64e:64cc:5641:2916:7c4 prefixlen 64
>scopeid 0x0<global>
> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>txqueuelen 500 (UNSPEC)
> RX packets 751 bytes 118096 (115.3 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 781 bytes 124142 (121.2 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
>> Or should I better setup a VPN client to your network
>> to see what is needed?
>
>I can provide you with an openvpn config file that you can use to
>connect to
>our network under separate cover if you'd like.
>
great.
let's take this off the list and come back with a
proposed 3 lines patch. But, actually, I hope we
do not see problems with the iwcm regarding address resolution.
Best,
Bernard.
next prev parent reply other threads:[~2021-02-12 15:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 19:35 directing soft iWARP traffic through a secure tunnel Chuck Lever
2021-02-12 12:37 ` Bernard Metzler
2021-02-12 13:02 ` Benjamin Coddington
2021-02-12 13:02 ` Chuck Lever
2021-02-12 13:19 ` Bernard Metzler
2021-02-12 13:23 ` Benjamin Coddington
2021-02-12 15:26 ` Bernard Metzler [this message]
2021-02-16 12:27 ` Bernard Metzler
2021-02-16 18:09 ` Jason Gunthorpe
2021-02-19 13:06 ` Bernard Metzler
2021-02-19 13:57 ` Jason Gunthorpe
2021-02-19 14:12 ` Tom Talpey
2021-02-19 14:34 ` Bernard Metzler
2021-02-19 14:54 ` Chuck Lever
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=OF6479A795.E0C17A4D-ON0025867A.0054D29B-0025867A.0054D2A4@notes.na.collabserv.com \
--to=bmt@zurich.ibm.com \
--cc=bcodding@redhat.com \
--cc=chuck.lever@oracle.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.