From owner-freebsd-current Sat Mar 29 00:35:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA16179 for current-outgoing; Sat, 29 Mar 1997 00:35:39 -0800 (PST) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA16174 for ; Sat, 29 Mar 1997 00:35:35 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by nlsystems.com (8.8.5/8.8.5) with SMTP id IAA04565; Sat, 29 Mar 1997 08:33:57 GMT Date: Sat, 29 Mar 1997 08:33:57 +0000 (GMT) From: Doug Rabson To: Tony Kimball cc: current@FreeBSD.ORG Subject: Re: Anyone familiar with iijppp NFS failures? In-Reply-To: <199703282158.VAA00548@compound.east.sun.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 28 Mar 1997, Tony Kimball wrote: > > Has anyone seen this? iijppp fails during NFS traffic: > wrote 1500, got -1 > wrote 672, got -1 > ... > Obviously in ip.c: > /* > * Pass it to tunnel device > */ > nw = write(tun_out, tunbuff, nb); > if (nw != nb) > fprintf(stderr, "wrote %d, got %d\r\n", nb, nw); > Before looking deeper, I thought I'd ask if there were any known > reasons for this sort of thing to happen. It would be helpful to know the value of errno at this point. From looking at the code, tunwrite can error if it is given a packet which is too large (EIO), if allocation of mbufs failed or if an input queue was full (ENOBUFS). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891