From owner-freebsd-current  Fri Mar 28 13:59:20 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA06532
          for current-outgoing; Fri, 28 Mar 1997 13:59:20 -0800 (PST)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA06522
          for <current@freebsd.org>; Fri, 28 Mar 1997 13:59:16 -0800 (PST)
Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id OAA21883 for <current@freebsd.org>; Fri, 28 Mar 1997 14:02:55 -0800
Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3)
	id QAA15302; Fri, 28 Mar 1997 16:58:42 -0500
Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4)
	id QAA12382; Fri, 28 Mar 1997 16:58:42 -0500
Received: (from alk@localhost) by compound.east.sun.com (8.8.5/8.7.3) id VAA00548; Fri, 28 Mar 1997 21:58:39 GMT
Date: Fri, 28 Mar 1997 21:58:39 GMT
Reply-To: Anthony.Kimball@East.Sun.COM
Message-Id: <199703282158.VAA00548@compound.east.sun.com>
From: Tony Kimball <Anthony.Kimball@East.Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: current@freebsd.org
Subject: Anyone familiar with iijppp NFS failures?
X-Face: O9M"E%K;(f-Go/XDxL+pCxI5<W_e*r7B8ojMD.5+qDgOp4/\gTQEgbOoBqf:Vtl*aW:<;9/
	UIVk'U^XhYg+v#r~*X<$Q=_ik@5:%E}pl]9|9|:]WLW8n:fLgg0~cfwWRBQxK/HSG0b1D/gljJC$qp
	b=HDF@+"H<|fXy`w#$8#6A"!F:>*gr[=FN@Y`cl1.Tn
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


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.

//alk