Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!gatech!enterpoop.mit.edu!ai-lab!hal.gnu.ai.mit.edu!not-for-mail From: mycroft@hal.gnu.ai.mit.edu (Charles Hannum) Newsgroups: comp.os.386bsd.questions Subject: Re: NFS PROBLEMS AFTER PATCH 0.2.2 Date: 5 Apr 1993 18:47:58 -0400 Organization: dis Lines: 18 Message-ID: <1pqcuu$1li5@hal.gnu.ai.mit.edu> References: <733572001snz@feline.demon.co.uk> <C4ttG9.2qB@news.cso.uiuc.edu> NNTP-Posting-Host: hal.ai.mit.edu In article <C4ttG9.2qB@news.cso.uiuc.edu> rkb55989@uxa.cso.uiuc.edu (Rafal) writes: > > I am running a 0.2.1 system, and am seeing similar problems. Just for > reference, I am running over SLIP, with my MTU [on the BSD box] set > at the standard 296. The terminal server I connect to claims it is > using an MTU of 1536, but all works with the standard BSD MTU, except > NFS [well, it works somewhat]. It sounds like 386BSD is not being intelligent enough to fragment the large UDP packets that NFS uses. Try using the options `rsize=256,wsize=256' (or smaller) with a MTU of 296. -- \ / Charles Hannum, mycroft@ai.mit.edu /\ \ PGP public key available on request. MIME, AMS, NextMail accepted. Scheme White heterosexual atheist male (WHAM) pride!