From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jan Kasprzak <kas@fi.muni.cz>
Cc: nfs@lists.sourceforge.net
Subject: Re: mountd gives "illegal port"
Date: Wed, 27 Oct 2004 12:39:10 -0400 [thread overview]
Message-ID: <20041027163910.GB4292@fieldses.org> (raw)
In-Reply-To: <20041027162321.GD4333@fi.muni.cz>
On Wed, Oct 27, 2004 at 06:23:22PM +0200, Jan Kasprzak wrote:
> J. Bruce Fields wrote:
> : On Wed, Oct 27, 2004 at 02:42:28PM +0200, Jan Kasprzak wrote:
> : > I have discovered the following problem in Linux NFS: When you mount
> : > many filesystems from the same server, mountd sometimes refuses the
> : > request with "illegal port" message in syslog. To reproduce this, I did
> : > the following:
> :
> : Just add the "insecure" export option to the server's export.
> :
> Of course, but I don't want to do this.
Why not?
> The problem is that client is querying portmap over TCP and from
> privileged port. By changing this we can use twice as much mounts in
> the TIME_WAIT period.
OK. It seems like kind of an obscure thing to care about....
> We may also force mount to query mountd over UDP, but I don't know how
> to do this. -o udp is probably for nfsd traffic, isn't it?
That's what I'd assume, but I don't know.--b.
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-10-27 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 12:42 mountd gives "illegal port" Jan Kasprzak
2004-10-27 15:45 ` J. Bruce Fields
2004-10-27 16:23 ` Jan Kasprzak
2004-10-27 16:39 ` J. Bruce Fields [this message]
2004-10-27 16:40 ` Jan Kasprzak
2004-10-27 18:28 ` Peter Astrand
2004-10-27 16:12 ` Jan Kasprzak
2004-10-27 21:04 ` Michael Richardson
2004-10-27 21:13 ` Jan Kasprzak
2004-10-27 22:19 ` Michael Richardson
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=20041027163910.GB4292@fieldses.org \
--to=bfields@fieldses.org \
--cc=kas@fi.muni.cz \
--cc=nfs@lists.sourceforge.net \
/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.