[.....]
> > I've fixed it in -current, not yet in -stable. You could try the
> > latest ppp archive from my web site if you want to confirm whether
> > or not the fix works.
>
> No, you misunderstood me. I'm usually using on my 3.2 box the ppp compiled from the
>current
> sources of 4.0 (BTW ppp from 3.2 doesn't have this bug). When I've wrote that
>sources was
> cvsup'ed today I mean 4.0 sources not 3.2.
Can you try applying the attached patch and enabling debug logging ?
What do the diagnostics say for that packet before you see the IO
error ?
Cheers.
> -Maxim
> --
> "We believe in the Power and the Might!"
> (Manowar, 1996)
> ----------------------------------------
> Maxim V. Sobolev, Financial Analyst,
> Vega International Capital
> Phone: +380-(44)-246-6396
> Fax: +380-(44)-220-8715
> E-mail: [EMAIL PROTECTED]
> ICQ: #42290709
> ----------------------------------------
--
Brian <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
<http://www.Awfulhak.org> <[EMAIL PROTECTED]>
Don't _EVER_ lose your sense of humour ! <[EMAIL PROTECTED]>
Index: link.c
===================================================================
RCS file: /home/ncvs/src/usr.sbin/ppp/link.c,v
retrieving revision 1.12
diff -u -r1.12 link.c
--- link.c 1999/06/02 15:59:03 1.12
+++ link.c 1999/07/28 08:51:44
@@ -263,6 +263,8 @@
if (l->layer[layer]->pull != NULL)
bp = (*l->layer[layer]->pull)(b, l, bp, &proto);
+ log_Printf(LogDEBUG, "link_PullPacket: Proto 0x%04x length %d\n", proto, mbuf_Length(bp));
+
if (layer == l->nlayers - 1) {
/* We've just done the top layer, despatch the packet(s) */
while (bp) {
