From owner-freebsd-bugs Tue Nov 23 2:40:23 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 6BA7A152A7 for ; Tue, 23 Nov 1999 02:40:15 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id CAA15175; Tue, 23 Nov 1999 02:40:00 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from inga.augusta.de (inga.augusta.de [193.175.23.65]) by hub.freebsd.org (Postfix) with ESMTP id C2CE214A00 for ; Tue, 23 Nov 1999 02:33:30 -0800 (PST) (envelope-from estartu@starbox.augusta.de) Received: (from uucp@localhost) by inga.augusta.de (8.9.3/8.9.3) with UUCP id LAA07252 for FreeBSD-gnats-submit@freebsd.org; Tue, 23 Nov 1999 11:33:17 +0100 (MET) Received: (from root@localhost) by sbgate.starbox.augusta.de (8.9.3/8.9.3) id LAA88517; Tue, 23 Nov 1999 11:27:31 +0100 (CET) (envelope-from estartu) Message-Id: <199911231027.LAA88517@sbgate.starbox.augusta.de> Date: Tue, 23 Nov 1999 11:27:31 +0100 (CET) From: Gerhard Schmidt Reply-To: root@sbgate.starbox.augusta.de To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: i386/15062: i4 problem with ascend terminalserver Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 15062 >Category: i386 >Synopsis: i4b stops working after some time >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Nov 23 02:40:00 PST 1999 >Closed-Date: >Last-Modified: >Originator: Gerhard Schmidt >Release: FreeBSD 3.2-STABLE i386 >Organization: Augsburger Computer Forum e.V. >Environment: FreeBSD sbgate.starbox.augusta.de 3.2-STABLE FreeBSD 3.2-STABLE #0: Sat Jul 31 15:46:08 CEST 1999 root@sbgate.starbox.augusta.de:/usr/src/sys/compile/SBGATE i386 >Description: I use i4b for nearly a year with my local ISP. Last week they switched from a US Robotics Terminal Server to two Ascent Terminalserver. I change my config to the new Destination address. Everything worked for some hours. My system is configured as Dial on Demand. 4 hour later I tried to connect, i4b connected an disconnected after few seconds. an repeated to connect over 40 times with the same result. I activated the debug option and got the following output Nov 23 10:37:40 sbgate /kernel: isp0: lcp open(initial) Nov 23 10:37:40 sbgate /kernel: isp0: phase establish Nov 23 10:37:40 sbgate /kernel: isp0: Up event Nov 23 10:37:40 sbgate /kernel: isp0: lcp up(starting) Nov 23 10:37:40 sbgate /kernel: isp0: lcp output Nov 23 10:37:41 sbgate /kernel: isp0: lcp input(req-sent): Nov 23 10:37:41 sbgate /kernel: isp0: lcp parse opts: mru auth-proto 0x13 [rej] send conf-rej Nov 23 10:37:41 sbgate /kernel: isp0: lcp output Nov 23 10:37:41 sbgate /kernel: isp0: lcp input(req-sent): Nov 23 10:37:41 sbgate /kernel: isp0: lcp input(ack-rcvd): Nov 23 10:37:41 sbgate /kernel: isp0: lcp parse opts: mru auth-proto Nov 23 10:37:41 sbgate /kernel: isp0: lcp parse opt values: mru 1524 auth-proto send conf-ack Nov 23 10:37:42 sbgate /kernel: isp0: lcp output Nov 23 10:37:42 sbgate /kernel: isp0: lcp tlu Nov 23 10:37:42 sbgate /kernel: isp0: phase authenticate Nov 23 10:37:42 sbgate /kernel: isp0: pap output Nov 23 10:37:42 sbgate /kernel: isp0: pap success Nov 23 10:37:42 sbgate /kernel: isp0: phase network Nov 23 10:37:43 sbgate /kernel: isp0: ipcp open(stopped) Nov 23 10:37:43 sbgate /kernel: isp0: lcp close(opened) Nov 23 10:37:43 sbgate /kernel: isp0: phase terminate Nov 23 10:37:43 sbgate /kernel: isp0: lcp output Nov 23 10:37:43 sbgate /kernel: isp0: invalid input protocol Nov 23 10:37:43 sbgate /kernel: isp0: lcp input(closing): Nov 23 10:37:43 sbgate /kernel: isp0: phase dead Nov 23 10:37:43 sbgate /kernel: isp0: lcp down(closed) Nov 23 10:37:43 sbgate /kernel: isp0: Down event (carrier loss) Nov 23 10:37:43 sbgate /kernel: isp0: lcp close(initial) The Problem Remains til I reboot. After the reboot everything work fine for some hours and then the Problem returns. >How-To-Repeat: >Fix: reboot the system, but thats not realy a option. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message