Date: Tue, 24 Mar 1998 13:10:04 -0800 (PST) From: Duncan Barclay <dmlb@ragnet.demon.co.uk> To: freebsd-bugs Subject: Re: i386/5698: LPIP causes spurious reboots Message-ID: <199803242110.NAA01550@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR i386/5698; it has been noted by GNATS.
From: Duncan Barclay <dmlb@ragnet.demon.co.uk>
To: freebsd-gnats-submit@freebsd.org, dag-erli@ifi.uio.no
Cc: Subject: Re: i386/5698: LPIP causes spurious reboots
Date: Tue, 24 Mar 1998 20:49:38 -0000 (GMT)
Summary of my experiences using PLIP on FreeBSD 2.2.5, with
one 5x86-133 with 20MB RAM and a 486/25 with 4MB Contura laptop.
- sometimes when using a fast and slow machine (eg.P100 and 486/25)
the fast machine crashes when you do big transfers. I think it
is due to buffer overruns on the slow machine side and the fast
machine doesnt deal with this well. The work around is to get the
slow machine to be the initiator end of any xfer, i.e. slow machine
is saying "give me next block" or "here's the next block". Be warned
things like ftp and rcp have different initiator ends.
- NFS works (bearing in mind the above, use the old reduce the
block size hack, although I never tried it). However, due to
the way an RPC is implemented in FreeBSD, portmap/mountd attaches
itself to the first network interface (for things like getting
a hostname etc.) which is often lp0 (depends on kernel config). This
is a pain because the RPC code can't handle a point to point
interface (like PLPI or PPP) and you don't get a running mountd.
Workaround is to add a static route use
# to enable rpc to work with a PLIP network (rpc binds to the first
# network interface it finds an lp0 is found v. early)
static_routes="loop_lp0"
route_loop_lp0="192.168.201.32 127.0.0.1 1"
---
________________________________________________________________________
Duncan Barclay | God smiles upon the little children,
dmlb@ragnet.demon.co.uk | the alcoholics, and the permanently stoned.
________________________________________________________________________
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803242110.NAA01550>