From owner-freebsd-questions  Wed Feb 21 13:08:09 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA27975
          for questions-outgoing; Wed, 21 Feb 1996 13:08:09 -0800 (PST)
Received: from digi.digiware.nl (root@digi.digiware.nl [192.87.209.247])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA27832
          for <questions@freebsd.org>; Wed, 21 Feb 1996 13:07:37 -0800 (PST)
Received: by digi.digiware.nl (8.6.12/1.63)
    id WAA06944; Wed, 21 Feb 1996 22:07:10 +0100
From: wjw@digi.digiware.nl (Willem Jan Withagen)
Message-Id: <199602212107.WAA06944@digi.digiware.nl>
Subject: slattach problems
To: questions@freebsd.org
Date: Wed, 21 Feb 1996 22:07:08 +0100 (MET)
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-questions@freebsd.org
Precedence: bulk

Hi,

I'm running 2.1.0 on a 486/100 with all RELEASE stuff.

My Internet connection is a leased line with 2 Zyxels, and this has
funtioned flawless under 2.0.5.

But under 2.1.0 there occurs a problem once the leased line has gone down
and comes up again:
    -	slattach informes about the missing carrier
    -	and in due time the status the routing entry for the link is 
	adjusted
    -	then the lines comes up, but slattach only tells the system that the
	carrier has returned. 
	The IP routing entry is not updated.
	NOTE:	This is a fixed connection, so I have a permanent SLIP
		without login at the portmaster at the other side. It 
		just always speaks SLIP to me.
    -	If I kill the current slattach, and start a fresh one, then the 
	routing entry IS updated.

Now what can the problems be, and how do I detect them?

Thanx,
	Willem Jan Withagen