From: "Malte Schröder" <maltesch@gmx.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: NFS4 sec=krb5 broken in 3.9-rc8
Date: Wed, 24 Apr 2013 07:58:44 +0200 [thread overview]
Message-ID: <51777494.8010306@gmx.de> (raw)
In-Reply-To: <20130423215807.GL3676@fieldses.org>
[-- Attachment #1.1: Type: text/plain, Size: 883 bytes --]
On 23.04.2013 23:58, J. Bruce Fields wrote:
> On Tue, Apr 23, 2013 at 09:55:01PM +0200, Malte Schröder wrote:
>> Hi,
>> when I update my server from kernel 3.8.5 to 3.9-rc8 I cannot mount its
>> NFS exports from clients using nfs4 and sec=krb5. Using sec=sys works,
>> using 3.8.5 also works good with both modes.
>
> Could you get a network trace showing the failure
>
> Run
>
> tcpdump -s0 -wtmp.pcap
>
> then send us tmp.pcap.
>
> (You can also take a look at tmp.pcap yourself in wireshark--it may be
> obvious where the failure occurs.)
>
> --b.
>
The trace is attached. It contains two tries, the first using sec=sys,
the second sec=krb5. I used "mount -tnfs -overs=4,sec=krb5 gateway:/
/mnt". NFS-Utils have version 1.2.6.
--
Gruß
Malte Schröder
---------------------------------------------------------------------
MalteSch@gmx.de
[-- Attachment #1.2: nfs4.pcap --]
[-- Type: application/vnd.tcpdump.pcap, Size: 239168 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-04-24 5:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 19:55 NFS4 sec=krb5 broken in 3.9-rc8 Malte Schröder
2013-04-23 21:58 ` J. Bruce Fields
2013-04-24 5:58 ` Malte Schröder [this message]
2013-04-24 14:01 ` J. Bruce Fields
2013-04-24 17:07 ` Malte Schröder
2013-04-24 19:23 ` J. Bruce Fields
2013-04-26 9:20 ` Malte Schröder
2013-04-26 15:23 ` J. Bruce Fields
2013-04-26 16:56 ` Malte Schröder
2013-04-26 17:16 ` J. Bruce Fields
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=51777494.8010306@gmx.de \
--to=maltesch@gmx.de \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).