mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Roland Kuhn <rkuhn@e18.physik.tu-muenchen.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [newbie] NFS client: port-unreachable
Date: Sun, 3 Jun 2001 00:15:16 +0200	[thread overview]
Message-ID: <15129.25972.433708.994343@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.31.0106022258210.17342-100000@pc40.e18.physik.tu-muenchen.de>
In-Reply-To: <shsd78o2h84.fsf@charged.uio.no> <Pine.LNX.4.31.0106022258210.17342-100000@pc40.e18.physik.tu-muenchen.de>

>>>>> " " == Roland Kuhn <rkuhn@e18.physik.tu-muenchen.de> writes:

     > No, I have no port specific rules in the firewall (iptables),
     > but this machine does SNAT for 32 other linux boxes which also
     > get some directories from the same server (including YP). I had
     > some trouble with the YPSERV-calls until I bound two more IPs
     > to the network card and masqueraded the 32 boxes via these
     > additional addresses. What might happen is that the specific
     > port gets allocated by some port remapping in iptables during
     > the request, but I don't see why this should happen only for
     > specific directories (e.g. /home works and /compass doesn't
     > while both are from the same server).

Are /home and /compass on the same mount point on the client though? 
If not, then they won't share the same port.

IOW: they will only share the same port if you have '/' as the NFS
mountpoint.

Cheers,
  Trond

  parent reply	other threads:[~2001-06-02 22:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-01 17:04 Roland Kuhn
2001-06-01 18:22 ` Trond Myklebust
2001-06-02 21:04   ` Roland Kuhn
2001-06-02 22:15   ` Trond Myklebust [this message]
2001-06-03 15:56     ` iptables port remapping problem (was: [newbie] NFS client: port-unreachable) Roland Kuhn

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=15129.25972.433708.994343@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkuhn@e18.physik.tu-muenchen.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

all inboxes | Powered by JetHome®