Bug 15062

Summary: i4b stops working after some time
Product: Base System Reporter: Gerhard Schmidt <estartu>
Component: i386Assignee: hm
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 3.2-STABLE   
Hardware: Any   
OS: Any   

Description Gerhard Schmidt 1999-11-23 10:40:00 UTC
	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 <conf-req id=0xc6 len=10 05-06-43-75-49-b3>
Nov 23 10:37:41 sbgate /kernel: isp0: lcp input(req-sent): <conf-req id=0x1 len=21 01-04-05-f4-03-04-c0-23-13-09-03-00-c0-7b-8f-49-2a>
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 <conf-rej id=0x1 len=13 13-09-03-00-c0-7b-8f-49-2a>
Nov 23 10:37:41 sbgate /kernel: isp0: lcp input(req-sent): <conf-ack id=0xc6 len=10 05-06-43-75-49-b3>
Nov 23 10:37:41 sbgate /kernel: isp0: lcp input(ack-rcvd): <conf-req id=0x2 len=12 01-04-05-f4-03-04-c0-23>
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 <conf-ack id=0x2 len=12 01-04-05-f4-03-04-c0-23>
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 <req id=0xc7 len=22 **-**-**-**-**-**-**-**-**-**-**-**-**-**-**-**-**-**>
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 <term-req id=0xc8 len=4>
Nov 23 10:37:43 sbgate /kernel: isp0: invalid input protocol <addr=0xff ctrl=0x3 proto=0x80fd>
Nov 23 10:37:43 sbgate /kernel: isp0: lcp input(closing): <term-ack id=0xc8 len=4>
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.

Fix: 

reboot the system, but thats not realy a option.
Comment 1 hm freebsd_committer freebsd_triage 2000-04-16 19:58:44 UTC
State Changed
From-To: open->analyzed

This seems to be related to a bug report and a patch submitted 
on the freebsd-isdn mailinglist. The patch has been integrated  
into isdn4bsd and will be comitted to freebsd-current. 


Comment 2 hm freebsd_committer freebsd_triage 2000-04-16 19:58:44 UTC
Responsible Changed
From-To: freebsd-bugs->hm

Comment 3 hm freebsd_committer freebsd_triage 2000-07-19 09:41:25 UTC
State Changed
From-To: analyzed->closed


This bug has been reportedly fixed for FreeBSD >= 4.0. No i4b 
development is taking place for FreeBSD 3.x anymore not only 
due to the lack on machines running this OS.