From owner-freebsd-isdn Mon Feb 24 14:51:42 2003 Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98D2B37B401 for ; Mon, 24 Feb 2003 14:51:40 -0800 (PST) Received: from mta03bw.bigpond.com (mta03bw.bigpond.com [139.134.6.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0607843F75 for ; Mon, 24 Feb 2003 14:51:39 -0800 (PST) (envelope-from mhoroschun@canprint.com.au) Received: from canprint.com.au ([144.135.24.72]) by mta03bw.bigpond.com (Netscape Messaging Server 4.15 mta03bw Jul 16 2002 22:47:55) with SMTP id HAU4U000.HR5 for ; Tue, 25 Feb 2003 08:51:36 +1000 Received: from CPE-203-51-35-130.nsw.bigpond.net.au ([203.51.35.130]) by bwmam02.mailsvc.email.bigpond.com(MailRouter V3.0n 17/1415000); 25 Feb 2003 08:51:36 Date: Tue, 25 Feb 2003 09:51:36 +1100 Mime-Version: 1.0 (Apple Message framework v551) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Disconnection problem and configuration advice From: Matthew Horoschun To: freebsd-isdn@FreeBSD.ORG Content-Transfer-Encoding: 7bit Message-Id: <8713CD4E-484A-11D7-A987-000393B3A702@canprint.com.au> X-Mailer: Apple Mail (2.551) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi All, I've been using isdn4bsd for some time now and as a general rule it works well. I do however have occasional problems where after a long period of continuous connection the link dies. Curiously enough, IP-layer diagnostics (ping, traceroute) show that the link is down, but isdn-monitor still reports the channels up and running (even with a small amount of traffic flowing). The machine contains two Traverse NetJet-S cards and I'm using userland ppp (obviously with rbch devices). We use three channels in total. Two on the first card out to our ISP and one on the second card to another office. All channels are intended to stay up permanently. Just before the link dies, I get the following messages: Feb 25 06:46:53 zark /kernel: i4b-L1 itjc_dma_rx_intr: RDO (unit=0) dma=508 src=428 Feb 25 06:46:53 zark /kernel: i4b-L1 itjc_dma_rx_intr: RDO (unit=0) dma=520 src=428 Feb 25 06:47:48 zark /kernel: i4b-L2 i4b_rxd_ack: ((N(R)-1)=4) != (UA=5) !!! Feb 25 06:48:58 zark /kernel: i4b-L4 i4b_l4_setup_timeout_fix_unit: 1046116138: ERROR: idletime[60]+earlyhup[5] > unitlength[60]! Feb 25 06:49:07 zark /kernel: i4b-L4 i4b_l4_setup_timeout_fix_unit: 1046116147: ERROR: idletime[60]+earlyhup[5] > unitlength[60]! Any help with pointing me to what is going on would be appreciated! As an aside, I've never really understood the rates configuration properly or how they apply to userland ppp initiated connections. For an always-up connection, what should: ratetype unitlength unitlengthsrc idletime-incoming idletime-outgoing earlyhangup be set to? and what, if anything, should I put in isdnd.rates? Many thanks for any assistance. Matthew. -- Matthew Horoschun Network Administrator CanPrint Communications Pty. Ltd. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Feb 24 19:27:20 2003 Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2CF837B401 for ; Mon, 24 Feb 2003 19:27:18 -0800 (PST) Received: from nexus.tmp.com.br (nexus.tmp.com.br [200.255.204.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2365743FA3 for ; Mon, 24 Feb 2003 19:27:17 -0800 (PST) (envelope-from prallon@nexus.tmp.com.br) Received: (from prallon@localhost) by nexus.tmp.com.br (8.8.8/8.8.8) id AAA11378 for freebsd-isdn@freebsd.org; Tue, 25 Feb 2003 00:27:13 -0300 Date: Tue, 25 Feb 2003 00:26:16 -0300 From: Sergio de Souza Prallon To: Matthew Horoschun Subject: Re: Disconnection problem and configuration advice Message-ID: <20030225002616.A10465@tmp.com.br> References: <8713CD4E-484A-11D7-A987-000393B3A702@canprint.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <8713CD4E-484A-11D7-A987-000393B3A702@canprint.com.au>; from mhoroschun@canprint.com.au on Tue, Feb 25, 2003 at 09:51:36AM +1100 X-URL: http://www.tmp.com.br Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Feb 25, 2003 at 09:51:36AM +1100, Matthew Horoschun wrote: [...] > > Just before the link dies, I get the following messages: > > Feb 25 06:46:53 zark /kernel: i4b-L1 itjc_dma_rx_intr: RDO (unit=0) > dma=508 src=428 > Feb 25 06:46:53 zark /kernel: i4b-L1 itjc_dma_rx_intr: RDO (unit=0) > dma=520 src=428 Sometimes I see these too when the link is dropped. I believe that your B-channels stopped receiving valid HDLC data at this exact moment. > Feb 25 06:47:48 zark /kernel: i4b-L2 i4b_rxd_ack: ((N(R)-1)=4) != > (UA=5) !!! And then, a minute later I4B notes that something is possibly wrong with the D-channel also. The above message states that the SEQ# of the incoming D-channel packet is wrong. The carrier is one number ahead of what your machine expects. > Feb 25 06:48:58 zark /kernel: i4b-L4 i4b_l4_setup_timeout_fix_unit: > 1046116138: ERROR: idletime[60]+earlyhup[5] > unitlength[60]! > Feb 25 06:49:07 zark /kernel: i4b-L4 i4b_l4_setup_timeout_fix_unit: > 1046116147: ERROR: idletime[60]+earlyhup[5] > unitlength[60]! This is a config error discovered and reported when, I believe, your system attempted a redial. Set unitlength to the period of time your telco charges an active connection. Earlyhangup is probably OK, but you should make idletime-{in,out}going a least a second smaller than unitlength-earlyhangup. However, I don't believe this is the reason of your problems. I think the telco hung your call and failed to notify your machine of the fact and the reason for doing so. The cause can be a bug or a timeout limit in the telco system or on your ISP's NAS. It can even be an I4B bug: an ill-formed D-channel packet could have driven the switch into a state where a reset condition on the link was called for. Try to enable debug on the D-channel and on I.430 events. Next time, may be we can have something more concrete to look at. []'s -- Prallon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 27 19:18:29 2003 Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8841A37B401 for ; Thu, 27 Feb 2003 19:18:27 -0800 (PST) Received: from neuromancer.canprint.com.au (mail.canprint.com.au [198.142.3.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id A919043F93 for ; Thu, 27 Feb 2003 19:18:25 -0800 (PST) (envelope-from mhoroschun@canprint.com.au) Received: (from root@localhost) by neuromancer.canprint.com.au (8.12.6/8.11.1) id h1S3IOjs094614 for freebsd-isdn@freebsd.org; Fri, 28 Feb 2003 14:18:24 +1100 (EST) (envelope-from mhoroschun@canprint.com.au) Received: from canprint.com.au (cp252.canprint.intranet [192.168.1.252]) by neuromancer.canprint.com.au (8.12.6/8.11.1) with ESMTP id h1S3IKUu094606; Fri, 28 Feb 2003 14:18:21 +1100 (EST) (envelope-from mhoroschun@canprint.com.au) Date: Fri, 28 Feb 2003 14:15:05 +1100 Subject: Re: Disconnection problem and configuration advice Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) Cc: freebsd-isdn@freebsd.org To: Sergio de Souza Prallon From: Matthew Horoschun In-Reply-To: <20030225002616.A10465@tmp.com.br> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.551) X-Virus-Scanned: by Sophos SWEEP at CanPrint Communications Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Sergio, On Tuesday, February 25, 2003, at 02:26 PM, Sergio de Souza Prallon wrote: > > Try to enable debug on the D-channel and on I.430 events. Next time, > may > be we can have something more concrete to look at. Thanks for your advice. I'll enable the debugging as suggested and fix my configuration. This problem only occurs every 60 days or so... I'll just sit it out until then. Cheers Matthew. -- Matthew Horoschun Network Administrator CanPrint Communications Pty. Ltd. Telephone: (02) 6295 4422 Facsimile: (02) 6295 4473 -- Matthew Horoschun Network Administrator CanPrint Communications Pty. Ltd. Mobile: 0417 282 378 Direct: (02) 6295 4544 Telephone: (02) 6295 4422 Facsimile: (02) 6295 4473 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message