All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas <kuch3n@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: NFS giving Access via DNS-Exports
Date: Thu, 30 Jul 2015 13:05:34 +0200	[thread overview]
Message-ID: <55BA04FE.6060908@gmail.com> (raw)

Hi,

my Network gots following topology:

Gateway I [10.1.0.1] lab01.labornetz.3315.
|---Row I [10.1.0.255].
\---Gateway II [10.1.0.2] lab11.labornetz.3315.
      |---Row II [10.2.0.255].
      \---Gateway III [10.2.0.1] lab21.labornetz.3315.
           \---Row III [10.3.0.255].

All of that Machines except for lab21 can Access the NFS-Shares with:

/srv/nfs4 
*.labornetz.3315(rw,fsid=0,no_subtree_check,nohide,anonuid=99,anongid=100)
/srv/nfs4/public *.labornetz.3315(rw,no_subtree_check,nohide)
/srv/nfs4/backups 
*.labornetz.3315(rw,no_subtree_check,nohide,root_squash,anonuid=99,anongid=100)

The nslookup for lab21 and reverse: http://nopaste.linux-dev.org/?664551
for lab11: http://nopaste.linux-dev.org/?664552

The /etc/exports file: http://nopaste.linux-dev.org/?664553

Output of 'tcpdump -i lan0 host 10.2.0.2 and port 2049 -n': 
http://nopaste.linux-dev.org/?664558

Uncommenting 17 and 18 will give access to Machine lab21, imho this is 
more a Workaround than a fix.

Any Suggestion on this?

Regards


                 reply	other threads:[~2015-07-30 11:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=55BA04FE.6060908@gmail.com \
    --to=kuch3n@gmail.com \
    --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 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.