From: Trond Myklebust <trond.myklebust@primarydata.com>
To: Justus Ranvier <justusranvier@gmail.com>
Cc: linuxnfs <linux-nfs@vger.kernel.org>
Subject: Re: NFSv4 guest opens random ports
Date: Sun, 19 Jan 2014 14:16:29 -0500 [thread overview]
Message-ID: <94AFC682-E055-4BA5-8022-2674AFCA91C7@primarydata.com> (raw)
In-Reply-To: <52DC1926.10600@fuckthenavy.net>
On Jan 19, 2014, at 13:27, Justus Ranvier <justusranvier@gmail.com> wrote:
> I have systems running Gentoo Linux mounting shares hosted on a Gentoo
> Linux server. All are running 3.12.8 kernels and using NFS 4.
>
> I've followed all instructions I can find for fixing everything to a
> static port, but I still see one instance ofrandom port behavior.
>
> A kernel process (does not display a PID in netstat) on the guests is
> opening listening sockets on random high-numbered ports. The server is
> attempting to contact those guests via random low-numbered ports, which
> my firewall is blocking.
>
> Despite these packets being blocked, I haven't noticed any adverse
> effects - everything appears to work normally except for my system logs
> on the server being spammed with blocked outgoing connection attempts.
>
> What is this random port the client is trying to accept connections on,
> and how do I make it listen on a fixed port instead of a random one so
> that I can write useful firewall rules?
>
That’s probably the NFSv4 callback port. Please see your kernel Documentation/kernel-parameters.txt for how to set the nfs.callback_tcpport kernel/module option.
--
Trond Myklebust
Linux NFS client maintainer
next prev parent reply other threads:[~2014-01-19 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 18:27 NFSv4 guest opens random ports Justus Ranvier
2014-01-19 19:16 ` Trond Myklebust [this message]
2014-01-20 14:54 ` Justus Ranvier
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=94AFC682-E055-4BA5-8022-2674AFCA91C7@primarydata.com \
--to=trond.myklebust@primarydata.com \
--cc=justusranvier@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox