From: Shem Page <shem_page@alliedtelesyn.com>
To: nfs@lists.sourceforge.net
Subject: NFS UDP firewall reassemble failure
Date: Thu, 21 Mar 2002 13:16:49 -0800 [thread overview]
Message-ID: <00300496.C21145@alliedtelesyn.com> (raw)
I have discovered that my firewall will not re-assemble packets to a length
of more than about 1800 bytes (what fits in a single buffer).
I have been trying to mount a linux machine through the firewall and discover
that even if the mount is successful, once I start opening files, the mount
fails because the firewall cannot reassemble the packets to do it's stateful
inspection, hence it drops the packets so the client never sees the reply
from the server.
>From the packet traces it is evident that the NFS is sending fragments that
add up to well over 2k - too much for the software on the router to
reassemble.
I have been told by the maker of the router that this is not something they
intend to change in the near future, and perhaps I should look for a solution
within the configuration of the NFS.
So after quickly scanning some Man Pages, and also searching this archive, I
couldn't find any hint at how to restrict Mount, or NFSD to a limited packet
size.
Can people indicate to me whether this is possible to do, and perhaps where
I should begin.
Thanks in advance
Shem
--
==========================================================
Shem Page Tel 408 523-5305
Systems Engineer Fax 408 736-0100
Allied Telesyn Web: http://www.alliedtelesyn.com
960 Stewart Dr. Suite B email: Shem_Page@alliedtelesyn.com
Sunnyvale, California 94085
Simply connecting the IP world
==========================================================
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2002-03-21 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 21:16 Shem Page [this message]
2002-03-22 0:54 ` NFS UDP firewall reassemble failure Trond Myklebust
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=00300496.C21145@alliedtelesyn.com \
--to=shem_page@alliedtelesyn.com \
--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.