Re: kern/48935: ppp: ipcp gets stuck in stopped state

[Tilman Sauerbeck <tilman%code-monkey.de@localhost>]

The following reply was made to PR kern/48935; it has been noted by GNATS.

From: Tilman Sauerbeck <tilman%code-monkey.de@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
        netbsd-bugs%netbsd.org@localhost, martin%duskware.de@localhost
Subject: Re: kern/48935: ppp: ipcp gets stuck in stopped state
Date: Wed, 16 Jul 2014 20:01:51 +0200

 Martin Husemann [2014-07-15 19:00]:
 > The following reply was made to PR kern/48935; it has been noted by GNATS.
 > 
 > From: Martin Husemann <martin%duskware.de@localhost>
 > To: Tilman Sauerbeck <tilman%code-monkey.de@localhost>
 > Cc: gnats-bugs%NetBSD.org@localhost
 > Subject: Re: kern/48935: ppp: ipcp gets stuck in stopped state
 > Date: Tue, 15 Jul 2014 20:56:54 +0200
 > 
 >  On Tue, Jul 15, 2014 at 05:26:12PM +0200, Tilman Sauerbeck wrote:
 >  > >  I wonder if we should instead do more initialization in 
 > sppp_lcp_init().
 >  > 
 >  > Can you elaborate? I don't yet see what you have in mind.
 >  > Or are you suggesting to introduce another field next to lcp.protos
 >  > that would store the "active" protocols?
 >  
 >  No, I mean when sppp_lcp_init() runs, there can not be any active protocols,
 >  so it should probably just clear lcp.protos (and maybe a few other 
 > variables).
 
 I don't get how that would help in the scenario where I'm seeing the
 bug: what happens in my setup is that I'm creating the pppoe device
 once, when the system is coming up. At that time, sppp_lcp_init()
 is also called.
 However, it is not called again when the connection is brought up or down. 
 
 So making sppp_lcp_init() do more work would have no effect at all
 because it simply isn't run again.
 
 Thanks,
 Tilman