The only valid solution found is killing the interface before bringing
up another one. I was looking for a more ortodox solution, but this
catholic one makes his job.
Your idea of using /var/run/ppp* files works fine.
thanx
Sergiu Dunca
-----------------------------------------------------------------------------
On Tue, 28 Dec 1999, Michael Talbot-Wilson wrote:
> On Tue, 28 Dec 1999, Sergiu Dunca wrote:
>
> >
> > I've tried several combinations of versions of ppp 2.3.x with the latest
> > 2.2.x kernels. The problem is that in some situations pppd process
> > terminates but his interface and route remains up. This thing is very
> > nasty. This problem appears only on 2.2.x kernels, on 2.0.x kernels
> > the termination of pppd brought his interface and route down.
> >
> >
> > Sergiu Dunca
> > CODEC Electronic Prod Ltd
>
> All of these end-game problems, link falling over and pppd failing
> to exit, pppd dying but the interface staying alive etc. are
> probably better handled by not relying on pppd, ifconfig, route
> etc. to be bug-free. Run something with cron that will check the
> link. Have ip-up put something in /var/run that associates the IP
> address you pinged with the interface i/d.
>
> $ cat /var/run/ppp_10.1.7.2
> ppp2
>
> If the link has died, kill the interface. Assume nothing.
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
