* nfs4.1 and nconnect - is this supported?
@ 2021-07-15 13:16 guy keren
2021-07-15 14:43 ` Rick Macklem
0 siblings, 1 reply; 3+ messages in thread
From: guy keren @ 2021-07-15 13:16 UTC (permalink / raw)
To: linux-nfs
hi,
i wonder if the linux client's nfs nconnect feature was designed to
support NFS4.1 (or higher) versions? according to our experimentation,
the linux client seems to just alternate messages between the multiple
RPC/TCP connections, and does not seem to adhere to the NFS 4.1 protocol
requirement, that when using multiple connections, the client needs to
use BIND_CONN_TO_SESSION when trying to user a 2nd connection with the
same NFS4.1 session.
was this done on purpose? or is this configuration not supported by
linux client's 'nconnect'? or am i missing something?
thanks,
--guy
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: nfs4.1 and nconnect - is this supported?
2021-07-15 13:16 nfs4.1 and nconnect - is this supported? guy keren
@ 2021-07-15 14:43 ` Rick Macklem
2021-07-15 20:25 ` guy keren
0 siblings, 1 reply; 3+ messages in thread
From: Rick Macklem @ 2021-07-15 14:43 UTC (permalink / raw)
To: guy keren, linux-nfs
guy keren <guy@vastdata.com> wrote:
>hi,
>
>i wonder if the linux client's nfs nconnect feature was designed to
>support NFS4.1 (or higher) versions? according to our experimentation,
>the linux client seems to just alternate messages between the multiple
>RPC/TCP connections, and does not seem to adhere to the NFS 4.1 protocol
>requirement, that when using multiple connections, the client needs to
>use BIND_CONN_TO_SESSION when trying to user a 2nd connection with the
>same NFS4.1 session.
>
>was this done on purpose? or is this configuration not supported by
>linux client's 'nconnect'? or am i missing something?
Yep, you're missing something.
Snippet from RFC 5661 pg. 43:
If the client specifies no state
protection (Section 18.35) when the session is created, then when
SEQUENCE is transmitted on a different connection, the connection is
automatically associated with the fore channel of the session
specified in the SEQUENCE operation.
As such, BIND_CONN_TO_SESSION is only required to associate the
backchannel to the connection.
rick
thanks,
--guy
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: nfs4.1 and nconnect - is this supported?
2021-07-15 14:43 ` Rick Macklem
@ 2021-07-15 20:25 ` guy keren
0 siblings, 0 replies; 3+ messages in thread
From: guy keren @ 2021-07-15 20:25 UTC (permalink / raw)
To: Rick Macklem, linux-nfs
On 7/15/21 5:43 PM, Rick Macklem wrote:
> guy keren <guy@vastdata.com> wrote:
>> hi,
>>
>> i wonder if the linux client's nfs nconnect feature was designed to
>> support NFS4.1 (or higher) versions? according to our experimentation,
>> the linux client seems to just alternate messages between the multiple
>> RPC/TCP connections, and does not seem to adhere to the NFS 4.1 protocol
>> requirement, that when using multiple connections, the client needs to
>> use BIND_CONN_TO_SESSION when trying to user a 2nd connection with the
>> same NFS4.1 session.
>>
>> was this done on purpose? or is this configuration not supported by
>> linux client's 'nconnect'? or am i missing something?
> Yep, you're missing something.
>
> Snippet from RFC 5661 pg. 43:
> If the client specifies no state
> protection (Section 18.35) when the session is created, then when
> SEQUENCE is transmitted on a different connection, the connection is
> automatically associated with the fore channel of the session
> specified in the SEQUENCE operation.
>
> As such, BIND_CONN_TO_SESSION is only required to associate the
> backchannel to the connection.
>
> rick
thanks for pointing this out, rick - i forgot about this feature.
does it mean that 'nconnect' cannot work with MACHCRED or SSV client
authentication then?
will it work with kerberos (which does authenticate the client machine
normally, as far as i know)?
thanks,
--guy
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-07-15 20:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-15 13:16 nfs4.1 and nconnect - is this supported? guy keren
2021-07-15 14:43 ` Rick Macklem
2021-07-15 20:25 ` guy keren
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.