On Wed, Apr 23, 2003 at 12:09:56PM +0200, Martin Weber wrote:
> On Wed, Apr 23, 2003 at 12:51:01PM +0300, Juha K Kallio wrote:
> > I really have no idea why the in-kernel pppoe isn't disconnecting when the peer doesn't answer LCP. tcpdump clearly showed
> > the LCP echoes and replies. Today I checked another NetBSD machine which is timeouting correctly, and the config was just like 
> > mine:
> > 
> > create
> > ! pppoectl -e rtk0 pppoe0
> > ! pppoectl pppoe0 myauthproto=chap myauthname=user myauthsecret=pass max-auth-failure=0 # I've tried with PAP too
> > inet 213.139.166.169 212.50.132.94 # I really can't believe switching to 0.0.0.0 0.0.0.1 would affect this
> > ! route -q add 213.139.166.169 127.0.0.1 # that's for correct connections to my own IP, otherwise they go around the peer ;-)
> > up
> 
> That one is running ifwatchd ?

No. But what does ifwatchd have to do with this? It just watches when the ppp connection goes down, but the problem here is, 
it is not going down. Besides, I don't think I'll need ifwatchd for anything with a static IP.