From owner-freebsd-bugs  Sun Apr  6 21:50:03 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA21604
          for bugs-outgoing; Sun, 6 Apr 1997 21:50:03 -0700 (PDT)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA21595;
          Sun, 6 Apr 1997 21:50:02 -0700 (PDT)
Resent-Date: Sun, 6 Apr 1997 21:50:02 -0700 (PDT)
Resent-Message-Id: <199704070450.VAA21595@freefall.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, hsu@clinet.fi
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA21028
          for <FreeBSD-gnats-submit@freebsd.org>; Sun, 6 Apr 1997 21:41:04 -0700 (PDT)
Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1])
          by who.cdrom.com (8.8.5/8.6.11) with ESMTP id MAA25400
          for <FreeBSD-gnats-submit@freebsd.org>; Sun, 6 Apr 1997 12:32:14 -0700 (PDT)
Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.8.5/8.6.4) with ESMTP id WAA22948 for <FreeBSD-gnats-submit@freebsd.org>; Sun, 6 Apr 1997 22:32:07 +0300 (EET DST)
Received: (hsu@localhost) by katiska.clinet.fi (8.8.5/8.6.4) id WAA17384; Sun, 6 Apr 1997 22:32:06 +0300 (EET DST)
Message-Id: <199704061932.WAA17384@katiska.clinet.fi>
Date: Sun, 6 Apr 1997 22:32:06 +0300 (EET DST)
From: Heikki Suonsivu <hsu@clinet.fi>
Reply-To: hsu@clinet.fi
To: FreeBSD-gnats-submit@freebsd.org
X-Send-Pr-Version: 3.2
Subject: kern/3219: sppp or arnet gets looped after connection burb
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>Number:         3219
>Category:       kern
>Synopsis:       sppp or arnet gets looped after connection burb
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Apr  6 21:50:01 PDT 1997
>Last-Modified:
>Originator:     Heikki Suonsivu
>Organization:
Clinet, Espoo, Finland
>Release:        FreeBSD 2.2-RELEASE i386
>Environment:

FreeBSD used as a router.  Happens on all of them, common configuration is
digi/arnet 570i synchronous serial board (usually 4-port).  CPU
configurations vary from 486SX-33 to P133.

>Description:

Sometimes after a netburb a on leased circuit arnet (sppp?) goes out of sync
and does not handshake the line back up after the break:

Apr  3 00:49:15 innopoli3-gw /kernel: ar3: up
Apr  3 00:50:16 innopoli3-gw /kernel: ar3: down
Apr  3 00:50:31 innopoli3-gw /kernel: ar3: up

<line goes dead here>

<at this point I started checking out the port and said ifconfig debug for
the interface>

Apr  3 01:34:36 innopoli3-gw /kernel: ar3: lcp output <echo-req id=83h len=8h 33-1c-1c-57>
Apr  3 01:34:36 innopoli3-gw /kernel: ar3: lcp input(O): 8 bytes <echo-reply id=83h len=8h 2b-76-c-7f>
Apr  3 01:34:39 innopoli3-gw /kernel: ar3: lcp input(O): 12 bytes <echo-req id=3h len=ch 2b-76-c-7f-0-0-0-0>
Apr  3 01:34:39 innopoli3-gw /kernel: ar3: lcp output <echo-reply id=3h len=ch 33-1c-1c-57-0-0-0-0>
Apr  3 01:34:46 innopoli3-gw /kernel: ar3: lcp output <echo-req id=84h len=8h 33-1c-1c-57>
Apr  3 01:34:46 innopoli3-gw /kernel: ar3: lcp input(O): 8 bytes <echo-reply id=84h len=8h 2b-76-c-7f>
Apr  3 01:34:49 innopoli3-gw /kernel: ar3: lcp input(O): 12 bytes <echo-req id=4h len=ch 2b-76-c-7f-0-0-0-0>
Apr  3 01:34:49 innopoli3-gw /kernel: ar3: lcp output <echo-reply id=4h len=ch 33-1c-1c-57-0-0-0-0>
Apr  3 01:34:56 innopoli3-gw /kernel: ar3: lcp output <echo-req id=85h len=8h 33-1c-1c-57>
Apr  3 01:34:56 innopoli3-gw /kernel: ar3: lcp input(O): 8 bytes <echo-reply id=85h len=8h 2b-76-c-7f>
Apr  3 01:34:59 innopoli3-gw /kernel: ar3: lcp input(O): 12 bytes <echo-req id=5h len=ch 2b-76-c-7f-0-0-0-0>

<Around this point (I think) I told the interface ifconfig down and
ifconfig up.>

Apr  3 01:34:59 innopoli3-gw /kernel: ar3: lcp output <echo-reply id=5h len=ch 33-1c-1c-57-0-0-0-0>
Apr  3 01:35:08 innopoli3-gw /kernel: ar3: lcp output <conf-req id=86h len=ah 5-6-33-1c-1c-57>
Apr  3 01:35:08 innopoli3-gw /kernel: ar3: lcp input(C): 10 bytes <conf-req id=50h len=ah 5-6-2b-9e-e8-65>
Apr  3 01:35:08 innopoli3-gw /kernel: ar3: lcp output <conf-ack id=50h len=ah 5-6-2b-9e-e8-65>
Apr  3 01:35:08 innopoli3-gw /kernel: ar3: lcp input(S): 10 bytes <conf-ack id=86h len=ah 5-6-33-1c-1c-57>
Apr  3 01:35:08 innopoli3-gw /kernel: ar3: ipcp output <conf-req id=87h len=4h>
Apr  3 01:35:08 innopoli3-gw /kernel: ar3: ipcp input: 10 bytes <conf-req id=dh len=ah 3-6-c2-64-2d-fa>
Apr  3 01:35:08 innopoli3-gw /kernel: ar3: ipcp output <conf-rej id=dh len=ah 3-6-c2-64-2d-fa>
Apr  3 01:35:09 innopoli3-gw /kernel: ar3: lcp output <proto-rej id=88h len=ah 82-7-1-f7-0-4>
Apr  3 01:35:09 innopoli3-gw /kernel: ar3: invalid input protocol <0xff 0x3 0x8207>
Apr  3 01:35:09 innopoli3-gw /kernel: ar3: ipcp input: 4 bytes <conf-ack id=87h len=4h>
Apr  3 01:35:09 innopoli3-gw /kernel: ar3: ipcp input: 4 bytes <conf-req id=eh len=4h>
Apr  3 01:35:09 innopoli3-gw /kernel: ar3: ipcp output <conf-ack id=eh len=4h>
Apr  3 01:35:09 innopoli3-gw /kernel: ar3: lcp input(O): 12 bytes <echo-req id=1h len=ch 2b-9e-e8-65-0-0-0-0>
Apr  3 01:35:09 innopoli3-gw /kernel: ar3: lcp output <echo-reply id=1h len=ch 33-1c-1c-57-0-0-0-0>
Apr  3 01:35:16 innopoli3-gw /kernel: ar3: lcp output <echo-req id=89h len=8h 33-1c-1c-57>
Apr  3 01:35:16 innopoli3-gw /kernel: ar3: lcp input(O): 8 bytes <echo-reply id=89h len=8h 2b-9e-e8-65>
Apr  3 01:35:19 innopoli3-gw /kernel: ar3: lcp input(O): 12 bytes <echo-req id=2h len=ch 2b-9e-e8-65-0-0-0-0>
Apr  3 01:35:19 innopoli3-gw /kernel: ar3: lcp output <echo-reply id=2h len=ch 33-1c-1c-57-0-0-0-0>

<line works again.>

This happens both with arnet-arnet and arnet-cisco connections.

>How-To-Repeat:

Cause randon breaks on a leased line.  I do not know exactly how long they
have to be to wake up the problem, it seems that maybe one of ten breaks
has problems getting it right.

>Fix:
	
Workaround is to ifconfig down and ifconfig up the interface.

I think people with SDL cards have reported similar problem.

>Audit-Trail:
>Unformatted: