[.]
> > 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 pp
Brian Somers wrote:
> > Brian Somers wrote:
> >
> > > Ok, I found the culprit in ppp. I'm committing a change now.
> > >
> > > Thanks for the report !
> >
> > It seems that have found other culpit, because I'm continuing to see "Error:
>ip_Input:
> > deflink: wrote 0, got Input/output error" (3
> Brian Somers wrote:
>
> > Ok, I found the culprit in ppp. I'm committing a change now.
> >
> > Thanks for the report !
>
> It seems that have found other culpit, because I'm continuing to see "Error:
>ip_Input:
> deflink: wrote 0, got Input/output error" (3.2-STABLE) even using ppp cvsup'ed
Brian Somers wrote:
> Ok, I found the culprit in ppp. I'm committing a change now.
>
> Thanks for the report !
It seems that have found other culpit, because I'm continuing to see "Error: ip_Input:
deflink: wrote 0, got Input/output error" (3.2-STABLE) even using ppp cvsup'ed and
builded
today
Ok, I found the culprit in ppp. I'm committing a change now.
Thanks for the report !
> Hi folks,
>
> It seems that in some specific conditions user level ppp (PPP Version
> 2.22 - $Date: 1999/06/23 16:48:19 $) trying to incorrectly write to the
> tun device causing a panic if revision prior to
Hi folks,
It seems that in some specific conditions user level ppp (PPP Version
2.22 - $Date: 1999/06/23 16:48:19 $) trying to incorrectly write to the
tun device causing a panic if revision prior to 1.61 (current) or
1.51.2.1 (stable) of if_tun.c is used. In this tun revisions some belts
against
