From: Joschi Brauchle <joschi.brauchle@tum.de>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Cc: "Fehenberger, Tobias" <tobias.fehenberger@tum.de>,
"Stinner, Markus" <markus.stinner@tum.de>
Subject: Need help debugging NFSv3+KRB5+PAT (Port Address Translation) problem
Date: Fri, 26 Sep 2014 17:31:55 +0200 [thread overview]
Message-ID: <542586EB.2040101@tum.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
Hello everyone,
I need some help debugging a NFSv3 + KRB5 + PAT (Port Address
Translation) problem.
We have two hosts behind a firewall and an NFSv3 server outside
requiring KRB5 authentication.
1) Client_NAT is using NAT (network address translation),
2) Client_PAT is using PAT (port address translation)
to reach the NFSv3 server through the firewall.
Both clients are configured identically in terms of Kerberos and so on.
Mounting an NFSv3 share now fails on Client_PAT with the message:
RPC: server SERVERNAME requires stronger authentication.
On Client_NAT, mounting succeeds.
We strongly suspect the port address translation to be the reason for
the failure, but would need help confirming this and advice on how to
fix it.
Please find here the RPC debug logs from
Client_NAT: http://pastebin.com/9RANqVgY
Client_PAT: http://pastebin.com/TiscNVqW
Here is a DIFF between the two: http://pastebin.com/wCg7WyYd
I'm grateful for any help on this problem!
Best regards,
Joschi Brauchle
--
Dipl.-Ing. Joschi Brauchle, M.S.
Institute for Communications Engineering (LNT)
Technische Universitaet Muenchen (TUM)
80290 Munich, Germany
Tel (work): +49 89 289-23474
Fax (work): +49 89 289-23490
E-mail: joschi.brauchle@tum.de
Web: http://www.lnt.ei.tum.de/
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4917 bytes --]
next reply other threads:[~2014-09-26 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 15:31 Joschi Brauchle [this message]
2014-09-26 15:56 ` Need help debugging NFSv3+KRB5+PAT (Port Address Translation) problem Jeff Layton
2014-09-26 16:24 ` Joschi Brauchle
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=542586EB.2040101@tum.de \
--to=joschi.brauchle@tum.de \
--cc=linux-nfs@vger.kernel.org \
--cc=markus.stinner@tum.de \
--cc=tobias.fehenberger@tum.de \
/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