From owner-freebsd-isdn Sun Feb 20 1:20:28 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 8DBDB37BEDF; Sun, 20 Feb 2000 01:20:20 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 12MSXG-000N19-0A; Sun, 20 Feb 2000 09:20:15 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA11486; Sun, 20 Feb 2000 09:21:00 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 20 Feb 2000 09:18:57 +0000 (GMT) From: Doug Rabson To: Jose Gabriel Marcelino Cc: Soren Schmidt , current@freebsd.org, freebsd-isdn@freebsd.org, hm@hcs.de Subject: Re: Big ATA problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 19 Feb 2000, Jose Gabriel Marcelino wrote: > atapci0: port 0xe000-0xe00f at device 7.1 on > pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > ... > isic0: Error allocating io at 0x160 for Teles S0/16.3! > > While I was able to use the Teles again by changing it's default IO port I > think there will be some people who will find it cumbersome to have to > change the IO on a card that was working fine before. > > I feel this is a newbus issue with the ATA driver and/or maybe the i4b > driver doesn't really need that many IO ports so I'm sending this email to > both parties. This is a bug in the isic driver. I'm sure it doesn't use every port in that range so it needs to split the range in to two or more pieces and only allocate ports which it actually needs. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 20 1:42:40 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (Postfix) with ESMTP id B7F8437BE51; Sun, 20 Feb 2000 01:42:35 -0800 (PST) (envelope-from hm@kts.org) Received: from mailstore.ppp.net (pop3.ppp.net [212.18.80.90]) by mail.ppp.net (8.8.8/8.8.8) with ESMTP id KAA13880; Sun, 20 Feb 2000 10:42:21 +0100 Received: (from uucp@localhost) by mailstore.ppp.net (8.9.3/8.9.3/Debian/GNU) with UUCP id KAA11716; Sun, 20 Feb 2000 10:35:42 +0100 Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 21BF252AA3; Sun, 20 Feb 2000 10:10:54 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id 599161F17; Sun, 20 Feb 2000 10:10:45 +0100 (CET) Subject: Re: Big ATA problems In-Reply-To: from Jose Gabriel Marcelino at "Feb 19, 2000 11:48:52 pm" To: gabriel@maquina.com (Jose Gabriel Marcelino) Date: Sun, 20 Feb 2000 10:10:45 +0100 (CET) Cc: sos@freebsd.dk, current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000220091045.599161F17@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jose Gabriel Marcelino wrote: > This obviously conflicts with the secondary IDE controller which lies at > 0x170, however this has not been a problem till this day and no driver > complained about this. Now, with the newer kernel I get this: > > atapci0: port 0xe000-0xe00f at device 7.1 on > pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > ... > isic0: Error allocating io at 0x160 for Teles S0/16.3! > > While I was able to use the Teles again by changing it's default IO port I > think there will be some people who will find it cumbersome to have to > change the IO on a card that was working fine before. > > I feel this is a newbus issue with the ATA driver and/or maybe the i4b > driver doesn't really need that many IO ports so I'm sending this email to > both parties. This type of error with the 2nd IDE controller was reported also by other people, mostly the reports were "working sometimes". First of all, Teles refuses to give out any docs about their hardware, so it might be that not all addresses are used but this is 100% speculation. What you are recognizing is the real nice thing about newbus: you can't allocate a resource twice. I admit, this might be a bit cumbersome in the single case but it saves us from the "working sometimes" and "working sometimes not" and "sometimes, very seldom and unreproducible" error reports in the general case. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 20 3: 2:32 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (Postfix) with ESMTP id 36E4437BBB1; Sun, 20 Feb 2000 03:02:23 -0800 (PST) (envelope-from hm@kts.org) Received: from mailstore.ppp.net (pop3.ppp.net [212.18.80.90]) by mail.ppp.net (8.8.8/8.8.8) with ESMTP id MAA14616; Sun, 20 Feb 2000 12:02:21 +0100 Received: (from uucp@localhost) by mailstore.ppp.net (8.9.3/8.9.3/Debian/GNU) with UUCP id LAA12305; Sun, 20 Feb 2000 11:59:02 +0100 Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 0D21B52AA3; Sun, 20 Feb 2000 11:37:54 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id EB14A1F17; Sun, 20 Feb 2000 11:37:45 +0100 (CET) Subject: Re: Big ATA problems In-Reply-To: from Doug Rabson at "Feb 20, 2000 9:18:57 am" To: dfr@nlsystems.com (Doug Rabson) Date: Sun, 20 Feb 2000 11:37:45 +0100 (CET) Cc: current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000220103745.EB14A1F17@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson wrote: > > atapci0: port 0xe000-0xe00f at device 7.1 on > > pci0 > > ata0: at 0x1f0 irq 14 on atapci0 > > ata1: at 0x170 irq 15 on atapci0 > > ... > > isic0: Error allocating io at 0x160 for Teles S0/16.3! > > > > While I was able to use the Teles again by changing it's default IO port I > > think there will be some people who will find it cumbersome to have to > > change the IO on a card that was working fine before. > > > > I feel this is a newbus issue with the ATA driver and/or maybe the i4b > > driver doesn't really need that many IO ports so I'm sending this email to > > both parties. > > This is a bug in the isic driver. I'm sure it doesn't use every port in > that range so it needs to split the range in to two or more pieces and > only allocate ports which it actually needs. How do you come to that conclusion ? A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. The card in question allocates 3 portranges for this uses with each 0x40 bytes in length. In case there is is already an IDE controller allocated at 0x170 and a Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. So where is the bug ? This all looks perfectly reasonable to me with the exception that we could start argueing about whether it would be reasonable to split the allocation ranges for the ISAC and to save (if at all possible, there are some more registers at the end of the HSCX on the card) some bytes in the HSCX case. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 20 3:38:45 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 4EAA437BA81; Sun, 20 Feb 2000 03:38:39 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 12MUhA-000MIb-0K; Sun, 20 Feb 2000 11:38:36 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA23236; Sun, 20 Feb 2000 11:40:55 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 20 Feb 2000 11:38:51 +0000 (GMT) From: Doug Rabson To: Hellmuth Michaelis Cc: current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Subject: Re: Big ATA problems In-Reply-To: <20000220103745.EB14A1F17@bert.kts.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 20 Feb 2000, Hellmuth Michaelis wrote: > Doug Rabson wrote: > > > > atapci0: port 0xe000-0xe00f at device 7.1 on > > > pci0 > > > ata0: at 0x1f0 irq 14 on atapci0 > > > ata1: at 0x170 irq 15 on atapci0 > > > ... > > > isic0: Error allocating io at 0x160 for Teles S0/16.3! > > > > > > While I was able to use the Teles again by changing it's default IO port I > > > think there will be some people who will find it cumbersome to have to > > > change the IO on a card that was working fine before. > > > > > > I feel this is a newbus issue with the ATA driver and/or maybe the i4b > > > driver doesn't really need that many IO ports so I'm sending this email to > > > both parties. > > > > This is a bug in the isic driver. I'm sure it doesn't use every port in > > that range so it needs to split the range in to two or more pieces and > > only allocate ports which it actually needs. > > How do you come to that conclusion ? > > A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC > chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, > the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. > > The card in question allocates 3 portranges for this uses with each 0x40 > bytes in length. > > In case there is is already an IDE controller allocated at 0x170 and a > Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. > > So where is the bug ? > > This all looks perfectly reasonable to me with the exception that we could > start argueing about whether it would be reasonable to split the allocation > ranges for the ISAC and to save (if at all possible, there are some more > registers at the end of the HSCX on the card) some bytes in the HSCX case. So you are saying that what we really have here is a simple i/o conflict and possibly the ISDN card can be reconfigured to use a non-conflicting address? If so, then everything is working correctly and the resource manager has pointed a possible hardware problem :-). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 20 4:18:51 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from awfulhak.org (dynamic-107.max3-du-ws.dialnetwork.pavilion.co.uk [212.74.9.107]) by hub.freebsd.org (Postfix) with ESMTP id DF2A737BB9A; Sun, 20 Feb 2000 04:18:43 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id MAA41882; Sun, 20 Feb 2000 12:10:15 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id MAA78505; Sun, 20 Feb 2000 12:10:06 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002201210.MAA78505@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Doug Rabson Cc: Hellmuth Michaelis , current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: Big ATA problems In-Reply-To: Message from Doug Rabson of "Sun, 20 Feb 2000 11:38:51 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Feb 2000 12:10:05 +0000 From: Brian Somers Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Sun, 20 Feb 2000, Hellmuth Michaelis wrote: > > > Doug Rabson wrote: > > > > > > atapci0: port 0xe000-0xe00f at device 7.1 on > > > > pci0 > > > > ata0: at 0x1f0 irq 14 on atapci0 > > > > ata1: at 0x170 irq 15 on atapci0 > > > > ... > > > > isic0: Error allocating io at 0x160 for Teles S0/16.3! > > > > > > > > While I was able to use the Teles again by changing it's default IO port I > > > > think there will be some people who will find it cumbersome to have to > > > > change the IO on a card that was working fine before. > > > > > > > > I feel this is a newbus issue with the ATA driver and/or maybe the i4b > > > > driver doesn't really need that many IO ports so I'm sending this email to > > > > both parties. > > > > > > This is a bug in the isic driver. I'm sure it doesn't use every port in > > > that range so it needs to split the range in to two or more pieces and > > > only allocate ports which it actually needs. > > > > How do you come to that conclusion ? > > > > A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC > > chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, > > the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. > > > > The card in question allocates 3 portranges for this uses with each 0x40 > > bytes in length. > > > > In case there is is already an IDE controller allocated at 0x170 and a > > Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. > > > > So where is the bug ? > > > > This all looks perfectly reasonable to me with the exception that we could > > start argueing about whether it would be reasonable to split the allocation > > ranges for the ISAC and to save (if at all possible, there are some more > > registers at the end of the HSCX on the card) some bytes in the HSCX case. > > So you are saying that what we really have here is a simple i/o conflict > and possibly the ISDN card can be reconfigured to use a non-conflicting > address? If so, then everything is working correctly and the resource > manager has pointed a possible hardware problem :-). So it would seem, *but*, before moving from wd to ata I had both working 100% reliably. I had to move the Teles card to get it to work (allocate resources successfully) once I changed to ata. I would be pretty sure that the Teles S0/16.3 doesn't actually go near the I/O range @ 0x170. > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 20 5:12:30 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from devils.maquina.com (devils.maquina.com [62.229.71.43]) by hub.freebsd.org (Postfix) with ESMTP id 510DC37BB5E; Sun, 20 Feb 2000 05:12:07 -0800 (PST) (envelope-from gabriel@maquina.com) Received: from localhost (gabriel@localhost) by devils.maquina.com (8.9.3/8.9.3) with ESMTP id NAA54664; Sun, 20 Feb 2000 13:12:01 GMT (envelope-from gabriel@maquina.com) X-Authentication-Warning: devils.maquina.com: gabriel owned process doing -bs Date: Sun, 20 Feb 2000 13:12:01 +0000 (WET) From: Jose Gabriel Marcelino To: current@freebsd.org, freebsd-isdn@freebsd.org Cc: Hellmuth Michaelis , Doug Rabson Subject: Greedy Teles card was Re: Big ATA problems In-Reply-To: <200002201210.MAA78505@hak.lan.Awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > So you are saying that what we really have here is a simple i/o conflict > > and possibly the ISDN card can be reconfigured to use a non-conflicting > > address? If so, then everything is working correctly and the resource > > manager has pointed a possible hardware problem :-). > > So it would seem, *but*, before moving from wd to ata I had both > working 100% reliably. I had to move the Teles card to get it to > work (allocate resources successfully) once I changed to ata. > > I would be pretty sure that the Teles S0/16.3 doesn't actually go > near the I/O range @ 0x170. Yes, it also worked like that for quite some time in my FreeBSD box for more than 2 years on the my company's old Linux internet gateway/small server, with IDE disks and a network mounted CDrom running on the secondary channel.. No problems whatsoever.. I understand this resource allocation assures perfect compliance with the hardware specs and if so it should really be done this way, however I think this will brake many Teles cards out there once people start changing to FreeBSD 4.x so it should be at least documented, preferably with the switch settings since the card is old and people tend to lose the docs (I didn't have mine's so it took some trial and error to match IO and switches.. some people will surely have problem with that) Regards Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 20 5:12:52 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (Postfix) with ESMTP id 5DB9D37BCAF; Sun, 20 Feb 2000 05:12:28 -0800 (PST) (envelope-from hm@kts.org) Received: from mailstore.ppp.net (pop3.ppp.net [212.18.80.90]) by mail.ppp.net (8.8.8/8.8.8) with ESMTP id OAA15746; Sun, 20 Feb 2000 14:12:22 +0100 Received: (from uucp@localhost) by mailstore.ppp.net (8.9.3/8.9.3/Debian/GNU) with UUCP id OAA13195; Sun, 20 Feb 2000 14:07:05 +0100 Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 93CF152AA3; Sun, 20 Feb 2000 14:04:36 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id E22391F17; Sun, 20 Feb 2000 14:04:35 +0100 (CET) Subject: Re: Big ATA problems In-Reply-To: from Doug Rabson at "Feb 20, 2000 11:38:51 am" To: dfr@nlsystems.com (Doug Rabson) Date: Sun, 20 Feb 2000 14:04:35 +0100 (CET) Cc: hm@kts.org, current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000220130435.E22391F17@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > atapci0: port 0xe000-0xe00f at device 7.1 on > > > > pci0 > > > > ata0: at 0x1f0 irq 14 on atapci0 > > > > ata1: at 0x170 irq 15 on atapci0 > > > > ... > > > > isic0: Error allocating io at 0x160 for Teles S0/16.3! > > > > > > > > While I was able to use the Teles again by changing it's default IO port I > > > > think there will be some people who will find it cumbersome to have to > > > > change the IO on a card that was working fine before. > > > > > > > > I feel this is a newbus issue with the ATA driver and/or maybe the i4b > > > > driver doesn't really need that many IO ports so I'm sending this email to > > > > both parties. > > > > > > This is a bug in the isic driver. I'm sure it doesn't use every port in > > > that range so it needs to split the range in to two or more pieces and > > > only allocate ports which it actually needs. > > > > How do you come to that conclusion ? > > > > A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC > > chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, > > the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. > > > > The card in question allocates 3 portranges for this uses with each 0x40 > > bytes in length. > > > > In case there is is already an IDE controller allocated at 0x170 and a > > Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. > > > > So where is the bug ? > > > > This all looks perfectly reasonable to me with the exception that we could > > start argueing about whether it would be reasonable to split the allocation > > ranges for the ISAC and to save (if at all possible, there are some more > > registers at the end of the HSCX on the card) some bytes in the HSCX case. > > So you are saying that what we really have here is a simple i/o conflict > and possibly the ISDN card can be reconfigured to use a non-conflicting > address? Yes. > If so, then everything is working correctly and the resource > manager has pointed a possible hardware problem :-). Exactly! :-) hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 20 5:22:43 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (Postfix) with ESMTP id DB00737BD69; Sun, 20 Feb 2000 05:22:35 -0800 (PST) (envelope-from hm@kts.org) Received: from mailstore.ppp.net (pop3.ppp.net [212.18.80.90]) by mail.ppp.net (8.8.8/8.8.8) with ESMTP id OAA15855; Sun, 20 Feb 2000 14:22:22 +0100 Received: (from uucp@localhost) by mailstore.ppp.net (8.9.3/8.9.3/Debian/GNU) with UUCP id OAA13294; Sun, 20 Feb 2000 14:19:56 +0100 Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id AAB6352AA3; Sun, 20 Feb 2000 14:15:00 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id 479301F17; Sun, 20 Feb 2000 14:14:55 +0100 (CET) Subject: Re: Big ATA problems In-Reply-To: <200002201210.MAA78505@hak.lan.Awfulhak.org> from Brian Somers at "Feb 20, 2000 12:10: 5 pm" To: brian@Awfulhak.org (Brian Somers) Date: Sun, 20 Feb 2000 14:14:55 +0100 (CET) Cc: dfr@nlsystems.com, hm@kts.org, current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000220131455.479301F17@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brian Somers wrote: > > So you are saying that what we really have here is a simple i/o conflict > > and possibly the ISDN card can be reconfigured to use a non-conflicting > > address? If so, then everything is working correctly and the resource > > manager has pointed a possible hardware problem :-). > > So it would seem, *but*, before moving from wd to ata I had both > working 100% reliably. I had to move the Teles card to get it to > work (allocate resources successfully) once I changed to ata. > > I would be pretty sure that the Teles S0/16.3 doesn't actually go > near the I/O range @ 0x170. It depends. Assuming that the 16.3 allocates 0x40 bytes from 0x160 on, it has 32 bytes r/w fifo from 0x160. This fifo may be accessed directly at each location or indirectly in autoincrement mode. The isic driver (IIRC) accesses it in autoincrement mode, this results in using only the first byte for read/write of the fifo. This may be the reason why it succeeds until now. Anyhow - the fifo in non-autoincrement mode is _still_ there (it might also be, that Teles does not decode the last 30 bytes of this range, but i have no idea since the chance to get docs is nearly equal to zero) how this behaves cannot be predicted for shure, so IMHO there is a resource clash and the isic driver behaves correctly unless i overlooked something. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 20 8:48:13 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from widukind.bi.teuto.net (widukind.bi.teuto.net [212.8.197.28]) by hub.freebsd.org (Postfix) with ESMTP id 247D937BC20; Sun, 20 Feb 2000 08:48:08 -0800 (PST) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (IDENT:root@rumolt.teuto.de [212.8.203.81]) by widukind.bi.teuto.net (8.9.3/8.9.3) with ESMTP id RAA03748; Sun, 20 Feb 2000 17:48:04 +0100 Received: (from martin@localhost) by rumolt.teuto.de (8.9.3/8.8.8) id RAA01128; Sun, 20 Feb 2000 17:44:04 +0100 (MET) From: Martin Husemann Message-Id: <200002201644.RAA01128@rumolt.teuto.de> Subject: Re: Big ATA problems In-Reply-To: <20000220103745.EB14A1F17@bert.kts.org> from Hellmuth Michaelis at "Feb 20, 2000 11:37:45 am" To: hm@kts.org Date: Sun, 20 Feb 2000 17:44:04 +0100 (MET) Cc: dfr@nlsystems.com (Doug Rabson), current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Organization: Crusaders Catering Services Inc. ;-) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In case there is is already an IDE controller allocated at 0x170 and a > Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. This is a PnP card, right? So what does the PnP info say about needed memory ranges? > So where is the bug ? Depends. If the drivers allocation is coherent with the vendors description in the PnP configuration data, it's a newbus error (it shouldn't try to allocate the card there in the first place). If the PnP info differs from the drivers view of the card, it's either the vendors fault for providing wrong infos (this wouldn't be the only card suffering) [fix: provide a quirk entry], or the drivers fault: it should obey what the vendor tells PnP about the card. Which case applies? Simple: if it's possible to change the driver to obey the cards infos, that should be done. If the driver couldn't be made to work support for that card should be removed :-) If I'm wrong and this isn't a PnP card: it's pilot error. The card can't work at the specified address, so everything works as expected. Paraphrased in a sentence often heard as a reply from technical support persons for a big commercial OS vendor: "Status: This behaviour is by design." Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 20 9:28:54 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 76C5437BED4; Sun, 20 Feb 2000 09:28:49 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1514 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Sun, 20 Feb 2000 18:28:45 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 53B513890; Sun, 20 Feb 2000 18:28:36 +0100 (MET) Subject: Re: Big ATA problems In-Reply-To: <200002201644.RAA01128@rumolt.teuto.de> from Martin Husemann at "Feb 20, 0 05:44:04 pm" To: martin@rumolt.teuto.de (Martin Husemann) Date: Sun, 20 Feb 2000 18:28:35 +0100 (MET) Cc: hm@kts.org, dfr@nlsystems.com, current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 551 Message-Id: <20000220172836.53B513890@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Martin Husemann: > > In case there is is already an IDE controller allocated at 0x170 and a > > Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. > > This is a PnP card, right? No. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 20 10:17:54 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (Postfix) with ESMTP id E23A337B784; Sun, 20 Feb 2000 10:17:29 -0800 (PST) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.8) with ESMTP id SAA20221; Sun, 20 Feb 2000 18:17:30 GMT (envelope-from arg@arg1.demon.co.uk) Date: Sun, 20 Feb 2000 18:17:29 +0000 (GMT) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Hellmuth Michaelis Cc: Doug Rabson , current@freebsd.org, freebsd-isdn@freebsd.org Subject: Re: Big ATA problems In-Reply-To: <20000220103745.EB14A1F17@bert.kts.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 20 Feb 2000, Hellmuth Michaelis wrote: > > A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC > chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, > the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. But in the case of the teles16.3, it does _not_ use offsets 0x00-0x3b in the HSCX or ISAC: the ASIC on the card has 'folded' the address space so that the fifo appears at an address 3 bytes after the last register (0x3e with the current scheme - see tels0163_read_fifo()). The existing driver only uses offsets 0x20-0x3e relative to its assumed base address (and offsets 0x40 upwards are mapped separately). Note that the base address of 0x160 is a figment of the driver's imagination: the card is labelled as occupying 0xd80, and hence occupies 0x180/0x580/0x980 due to ISA address decoding rules. The 0x160 is only a convenience to make the driver's address calculations the same as the other cards - which is no longer necessary now that the driver has been restructured to have sc->readreg/writereg and can do things differently for each type of card. > The card in question allocates 3 portranges for this uses with each 0x40 > bytes in length. > > In case there is is already an IDE controller allocated at 0x170 and a > Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so. > > So where is the bug ? There is definitely a bug that it doesn't seem to allocate a (larger) portrange at 0xd80 - the output shown in an earlier message in this thread suggested that only a single byte at 0xd80 was allocated. The probe code accesses 0xd80, 0xd81, 0xd82, and testing indicates that it goes up to at least 0xd87, probably in fact all the way to 0xd1f. I am 99% certain that it is also incorrect to protect 0x160-0x17f (etc.). The driver certainly doesn't access registers in these ranges, and simple testing suggests that the card doesn't drive the bus for these regions. Unfortunately, my only 16.3 card is in a machine that is in use, so I can only do non-destructive testing on it. I will be able to test it properly in a couple of weeks when this machine has been retired. > This all looks perfectly reasonable to me with the exception that we > could start argueing about whether it would be reasonable to split the > allocation ranges for the ISAC and to save (if at all possible, there > are some more registers at the end of the HSCX on the card) some bytes > in the HSCX case. This would be wrong - the driver needs to protect all the address space occupied by the card, since it will be driving the bus for all these addresses and so another (PnP) device must not be assigned addresses in the "hole". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 20 11: 5:44 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from widukind.bi.teuto.net (widukind.bi.teuto.net [212.8.197.28]) by hub.freebsd.org (Postfix) with ESMTP id 282DB37BF4F; Sun, 20 Feb 2000 11:05:38 -0800 (PST) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (IDENT:root@rumolt.teuto.de [212.8.203.81]) by widukind.bi.teuto.net (8.9.3/8.9.3) with ESMTP id UAA11429; Sun, 20 Feb 2000 20:05:35 +0100 Received: (from martin@localhost) by rumolt.teuto.de (8.9.3/8.8.8) id UAA02117; Sun, 20 Feb 2000 20:07:11 +0100 (MET) From: Martin Husemann Message-Id: <200002201907.UAA02117@rumolt.teuto.de> Subject: Re: Big ATA problems In-Reply-To: from Andrew Gordon at "Feb 20, 2000 06:17:29 pm" To: arg@arg1.demon.co.uk (Andrew Gordon) Date: Sun, 20 Feb 2000 20:07:11 +0100 (MET) Cc: hm@kts.org (Hellmuth Michaelis), dfr@nlsystems.com (Doug Rabson), current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG Organization: Crusaders Catering Services Inc. ;-) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > But in the case of the teles16.3, it does _not_ use offsets 0x00-0x3b in > the HSCX or ISAC: the ASIC on the card has 'folded' the address space so > that the fifo appears at an address 3 bytes after the last register (0x3e > with the current scheme - see tels0163_read_fifo()). Ah, then the driver should map the region the correct way and access it without offsets. This kind of stuff is why the NetBSD port uses an extra "offset" field in its private map/region array, so it can map something offset from the expected range and map the generic register offsets to the mapped-region-offsets efficiently. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 20 11:23: 6 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (Postfix) with ESMTP id 05FF337BF03; Sun, 20 Feb 2000 11:22:43 -0800 (PST) (envelope-from hm@kts.org) Received: from mailstore.ppp.net (pop3.ppp.net [212.18.80.90]) by mail.ppp.net (8.8.8/8.8.8) with ESMTP id UAA19226; Sun, 20 Feb 2000 20:22:24 +0100 Received: (from uucp@localhost) by mailstore.ppp.net (8.9.3/8.9.3/Debian/GNU) with UUCP id UAA15458; Sun, 20 Feb 2000 20:19:59 +0100 Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 5227252AA3; Sun, 20 Feb 2000 20:19:52 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id A58381F17; Sun, 20 Feb 2000 20:19:47 +0100 (CET) Subject: Re: Big ATA problems In-Reply-To: from Andrew Gordon at "Feb 20, 2000 6:17:29 pm" To: arg@arg1.demon.co.uk (Andrew Gordon) Date: Sun, 20 Feb 2000 20:19:47 +0100 (CET) Cc: dfr@nlsystems.com, current@freebsd.org, freebsd-isdn@freebsd.org Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000220191947.A58381F17@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gordon wrote: > On Sun, 20 Feb 2000, Hellmuth Michaelis wrote: > > > > A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC > > chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, > > the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. > > But in the case of the teles16.3, it does _not_ use offsets 0x00-0x3b in > the HSCX or ISAC: the ASIC on the card has 'folded' the address space so > that the fifo appears at an address 3 bytes after the last register (0x3e > with the current scheme - see tels0163_read_fifo()). Oh yes, you are right! I was (and am still a bit) confused. So it uses 0x20-0x3e for the ISAC and 0x20-0x3e and 0x60-0x7e for the HSCX and at least three bytes at its base address, right ? This makes sense. Now the real question left is are this the only locations where the card is driving the bus ? hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 20 15:32:34 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (Postfix) with ESMTP id 15EA637C02A for ; Sun, 20 Feb 2000 15:32:27 -0800 (PST) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.8) with ESMTP id XAA20982; Sun, 20 Feb 2000 23:32:22 GMT (envelope-from arg@arg1.demon.co.uk) Date: Sun, 20 Feb 2000 23:32:21 +0000 (GMT) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Hellmuth Michaelis Cc: dfr@nlsystems.com, freebsd-isdn@freebsd.org Subject: Re: Big ATA problems In-Reply-To: <20000220191947.A58381F17@bert.kts.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 20 Feb 2000, Hellmuth Michaelis wrote: > Andrew Gordon wrote: > > On Sun, 20 Feb 2000, Hellmuth Michaelis wrote: > > > > > > A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC > > > chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, > > > the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. > > > > But in the case of the teles16.3, it does _not_ use offsets 0x00-0x3b in > > the HSCX or ISAC: the ASIC on the card has 'folded' the address space so > > that the fifo appears at an address 3 bytes after the last register (0x3e > > with the current scheme - see tels0163_read_fifo()). > > Oh yes, you are right! I was (and am still a bit) confused. > > So it uses 0x20-0x3e for the ISAC and 0x20-0x3e and 0x60-0x7e for the HSCX > and at least three bytes at its base address, right ? Well, this depends where you measure the offsets from! With the current bus space allocations, ISAC/HSCX-A/HSCX-B all use offsets 0x20-0x3e relative to the base addresses 0x160 etc. When the bus allocations have been cut down to the right size, each will use offsets 0x00-0x1e within a size 0x20 allocation at 0x180 etc. I notice that in i4b/layer1/isa_isic.c (ie. OpenBSD/NetBSD) the bus_space_map calls use the "correct" starting addresses (0x180, 0x580, 0x980, 0xd80) but still have the wrong sizes. I haven't analysed how this works. Attached is a patch that _might_ do the right thing on FreeBSD. I have fiddled the offsets in tels0163_write_reg/tels0163_read_reg so that the register numbers remain unchanged. I am particularly unsure if I have done the right thing with the allocation at 0xd80 - I copied the code from elsewhere, but I don't understand NewBus well enough to know if this is right. > > This makes sense. Now the real question left is are this the only locations > where the card is driving the bus ? I will test this as soon as I can dismantle the machine with my 16.3 card in it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 20 15:35: 6 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (Postfix) with ESMTP id 6E40137C011 for ; Sun, 20 Feb 2000 15:34:52 -0800 (PST) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.8) with ESMTP id XAA21031; Sun, 20 Feb 2000 23:34:55 GMT (envelope-from arg@arg1.demon.co.uk) Date: Sun, 20 Feb 2000 23:34:55 +0000 (GMT) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Hellmuth Michaelis Cc: dfr@nlsystems.com, freebsd-isdn@freebsd.org Subject: Re: Big ATA problems [patch file missing from previous msg] In-Reply-To: <20000220191947.A58381F17@bert.kts.org> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1889213078-951089695=:20564" Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1889213078-951089695=:20564 Content-Type: TEXT/PLAIN; charset=US-ASCII Attached patch as described in previous msg. Untested! --0-1889213078-951089695=:20564 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=patch Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=patch SW5kZXg6IGk0Yl90ZWxfczAxNjMuYw0KPT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PQ0KUkNTIGZpbGU6IC9yZXBvc2l0b3J5L3NyYy9zeXMvaTRiL2xheWVyMS9p NGJfdGVsX3MwMTYzLmMsdg0KcmV0cmlldmluZyByZXZpc2lvbiAxLjYNCmRp ZmYgLWMgLXIxLjYgaTRiX3RlbF9zMDE2My5jDQoqKiogaTRiX3RlbF9zMDE2 My5jCTE5OTkvMTIvMTQgMjA6NDg6MjQJMS42DQotLS0gaTRiX3RlbF9zMDE2 My5jCTIwMDAvMDIvMjAgMjM6MTg6NTgNCioqKioqKioqKioqKioqKg0KKioq IDc0LDgyICoqKioNCiAgDQogIHN0YXRpYyB1X2NoYXIgaW50cl9ub1tdID0g eyAxLCAxLCAwLCAyLCA0LCA2LCAxLCAxLCAxLCAwLCA4LCAxMCwgMTIsIDEs IDEsIDE0IH07DQogIA0KISAjZGVmaW5lIElTQUNfT0ZGUwkweDQyMA0KISAj ZGVmaW5lCUhTQ1hBX09GRlMJMHhjMjANCiEgI2RlZmluZSBIU0NYQl9PRkZT CTB4ODIwDQogIA0KICAvKi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LSoNCiAgICogICAgICBUZWxlcyBTMC8xNi4zIHJlYWQgZmlmbyByb3V0aW5l DQotLS0gNzQsODIgLS0tLQ0KICANCiAgc3RhdGljIHVfY2hhciBpbnRyX25v W10gPSB7IDEsIDEsIDAsIDIsIDQsIDYsIDEsIDEsIDEsIDAsIDgsIDEwLCAx MiwgMSwgMSwgMTQgfTsNCiAgDQohICNkZWZpbmUgSVNBQ19PRkZTCTB4NDAw DQohICNkZWZpbmUJSFNDWEFfT0ZGUwkweGMwMA0KISAjZGVmaW5lIEhTQ1hC X09GRlMJMHg4MDANCiAgDQogIC8qLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tKg0KICAgKiAgICAgIFRlbGVzIFMwLzE2LjMgcmVhZCBmaWZvIHJv dXRpbmUNCioqKioqKioqKioqKioqKg0KKioqIDg2LDkyICoqKioNCiAgew0K ICAJYnVzX3NwYWNlX3RhZ190ICAgIHQgPSBybWFuX2dldF9idXN0YWcoc2Mt PnNjX3Jlc291cmNlcy5pb19iYXNlW3doYXQrMV0pOw0KICAJYnVzX3NwYWNl X2hhbmRsZV90IGggPSBybWFuX2dldF9idXNoYW5kbGUoc2MtPnNjX3Jlc291 cmNlcy5pb19iYXNlW3doYXQrMV0pOw0KISAJYnVzX3NwYWNlX3JlYWRfbXVs dGlfMSh0LGgsMHgzZSxidWYsc2l6ZSk7DQogIH0NCiAgDQogIC8qLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKg0KLS0tIDg2LDkyIC0tLS0NCiAg ew0KICAJYnVzX3NwYWNlX3RhZ190ICAgIHQgPSBybWFuX2dldF9idXN0YWco c2MtPnNjX3Jlc291cmNlcy5pb19iYXNlW3doYXQrMV0pOw0KICAJYnVzX3Nw YWNlX2hhbmRsZV90IGggPSBybWFuX2dldF9idXNoYW5kbGUoc2MtPnNjX3Jl c291cmNlcy5pb19iYXNlW3doYXQrMV0pOw0KISAJYnVzX3NwYWNlX3JlYWRf bXVsdGlfMSh0LGgsMHgxZSxidWYsc2l6ZSk7DQogIH0NCiAgDQogIC8qLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKg0KKioqKioqKioqKioqKioq DQoqKiogOTcsMTAzICoqKioNCiAgew0KICAJYnVzX3NwYWNlX3RhZ190ICAg IHQgPSBybWFuX2dldF9idXN0YWcoc2MtPnNjX3Jlc291cmNlcy5pb19iYXNl W3doYXQrMV0pOw0KICAJYnVzX3NwYWNlX2hhbmRsZV90IGggPSBybWFuX2dl dF9idXNoYW5kbGUoc2MtPnNjX3Jlc291cmNlcy5pb19iYXNlW3doYXQrMV0p Ow0KISAJYnVzX3NwYWNlX3dyaXRlX211bHRpXzEodCxoLDB4M2UsYnVmLHNp emUpOw0KICB9DQogIA0KICAvKi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLSoNCi0tLSA5NywxMDMgLS0tLQ0KICB7DQogIAlidXNfc3BhY2VfdGFn X3QgICAgdCA9IHJtYW5fZ2V0X2J1c3RhZyhzYy0+c2NfcmVzb3VyY2VzLmlv X2Jhc2Vbd2hhdCsxXSk7DQogIAlidXNfc3BhY2VfaGFuZGxlX3QgaCA9IHJt YW5fZ2V0X2J1c2hhbmRsZShzYy0+c2NfcmVzb3VyY2VzLmlvX2Jhc2Vbd2hh dCsxXSk7DQohIAlidXNfc3BhY2Vfd3JpdGVfbXVsdGlfMSh0LGgsMHgxZSxi dWYsc2l6ZSk7DQogIH0NCiAgDQogIC8qLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tKg0KKioqKioqKioqKioqKioqDQoqKiogMTA4LDExNCAqKioq DQogIHsNCiAgCWJ1c19zcGFjZV90YWdfdCAgICB0ID0gcm1hbl9nZXRfYnVz dGFnKHNjLT5zY19yZXNvdXJjZXMuaW9fYmFzZVt3aGF0KzFdKTsNCiAgCWJ1 c19zcGFjZV9oYW5kbGVfdCBoID0gcm1hbl9nZXRfYnVzaGFuZGxlKHNjLT5z Y19yZXNvdXJjZXMuaW9fYmFzZVt3aGF0KzFdKTsNCiEgCWJ1c19zcGFjZV93 cml0ZV8xKHQsaCxvZmZzLGRhdGEpOw0KICB9DQogIA0KICAvKi0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLSoNCi0tLSAxMDgsMTE0IC0tLS0NCiAg ew0KICAJYnVzX3NwYWNlX3RhZ190ICAgIHQgPSBybWFuX2dldF9idXN0YWco c2MtPnNjX3Jlc291cmNlcy5pb19iYXNlW3doYXQrMV0pOw0KICAJYnVzX3Nw YWNlX2hhbmRsZV90IGggPSBybWFuX2dldF9idXNoYW5kbGUoc2MtPnNjX3Jl c291cmNlcy5pb19iYXNlW3doYXQrMV0pOw0KISAJYnVzX3NwYWNlX3dyaXRl XzEodCxoLG9mZnMgLSAweDIwLGRhdGEpOw0KICB9DQogIA0KICAvKi0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSoNCioqKioqKioqKioqKioqKg0K KioqIDExOSwxMjUgKioqKg0KICB7DQogIAlidXNfc3BhY2VfdGFnX3QgICAg dCA9IHJtYW5fZ2V0X2J1c3RhZyhzYy0+c2NfcmVzb3VyY2VzLmlvX2Jhc2Vb d2hhdCsxXSk7DQogIAlidXNfc3BhY2VfaGFuZGxlX3QgaCA9IHJtYW5fZ2V0 X2J1c2hhbmRsZShzYy0+c2NfcmVzb3VyY2VzLmlvX2Jhc2Vbd2hhdCsxXSk7 DQohIAlyZXR1cm4gYnVzX3NwYWNlX3JlYWRfMSh0LGgsb2Zmcyk7DQogIH0N CiAgDQogIC8qLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKg0KLS0t IDExOSwxMjUgLS0tLQ0KICB7DQogIAlidXNfc3BhY2VfdGFnX3QgICAgdCA9 IHJtYW5fZ2V0X2J1c3RhZyhzYy0+c2NfcmVzb3VyY2VzLmlvX2Jhc2Vbd2hh dCsxXSk7DQogIAlidXNfc3BhY2VfaGFuZGxlX3QgaCA9IHJtYW5fZ2V0X2J1 c2hhbmRsZShzYy0+c2NfcmVzb3VyY2VzLmlvX2Jhc2Vbd2hhdCsxXSk7DQoh IAlyZXR1cm4gYnVzX3NwYWNlX3JlYWRfMSh0LGgsb2ZmcyAtIDB4MjApOw0K ICB9DQogIA0KICAvKi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSoN CioqKioqKioqKioqKioqKg0KKioqIDE2MywxNjggKioqKg0KLS0tIDE2Mywx NzEgLS0tLQ0KICAJLyogc2V0IGlvIGJhc2UgKi8NCiAgDQogIAlzYy0+c2Nf cG9ydCA9IHJtYW5fZ2V0X3N0YXJ0KHNjLT5zY19yZXNvdXJjZXMuaW9fYmFz ZVswXSk7DQorIAkvKiBSZWxlYXNlIHRoZSByZXNvdXJjZSAtICByZS1hbGxv Y2F0ZSBsYXRlciB3aXRoIGNvcnJlY3Qgc2l6ZQkqLw0KKyAgICAgICAgIGJ1 c19yZWxlYXNlX3Jlc291cmNlKGRldiwgU1lTX1JFU19JT1BPUlQsIHNjLT5z Y19yZXNvdXJjZXMuaW9fcmlkWzBdLA0KKyAJCQlzYy0+c2NfcmVzb3VyY2Vz LmlvX2Jhc2VbMF0pOw0KICAJDQogIAlzd2l0Y2goc2MtPnNjX3BvcnQpDQog IAl7DQoqKioqKioqKioqKioqKioNCioqKiAxOTIsMjAwICoqKioNCiAgCQ0K ICAJLyogc2V0IGlvIHBvcnQgcmVzb3VyY2VzICovDQogIA0KICAJc2MtPnNj X3Jlc291cmNlcy5pb19yaWRbMV0gPSAxOwkNCiAgCWJ1c19zZXRfcmVzb3Vy Y2UoZGV2LCBTWVNfUkVTX0lPUE9SVCwgMSwNCiEgCQlzYy0+c2NfcG9ydC1J U0FDX09GRlMsIDB4NDApOw0KICAJc2MtPnNjX3Jlc291cmNlcy5pb19iYXNl WzFdID0NCiAgCQlidXNfYWxsb2NfcmVzb3VyY2UoZGV2LCBTWVNfUkVTX0lP UE9SVCwNCiAgCQkJCSAgICZzYy0+c2NfcmVzb3VyY2VzLmlvX3JpZFsxXSwN Ci0tLSAxOTUsMjE2IC0tLS0NCiAgCQ0KICAJLyogc2V0IGlvIHBvcnQgcmVz b3VyY2VzICovDQogIA0KKyAJc2MtPnNjX3Jlc291cmNlcy5pb19yaWRbMF0g PSAwOwkNCisgCWJ1c19zZXRfcmVzb3VyY2UoZGV2LCBTWVNfUkVTX0lPUE9S VCwgMCwgc2MtPnNjX3BvcnQsIDB4MjApOw0KKyAJc2MtPnNjX3Jlc291cmNl cy5pb19iYXNlWzBdID0NCisgCQlidXNfYWxsb2NfcmVzb3VyY2UoZGV2LCBT WVNfUkVTX0lPUE9SVCwNCisgCQkJCSAgICZzYy0+c2NfcmVzb3VyY2VzLmlv X3JpZFswXSwNCisgCQkJCSAgIDB1bCwgfjB1bCwgMSwgUkZfQUNUSVZFKTsN CisgCWlmKCFzYy0+c2NfcmVzb3VyY2VzLmlvX2Jhc2VbMF0pDQorIAl7DQor IAkJcHJpbnRmKCJpc2ljJWQ6IEVycm9yIGFsbG9jYXRpbmcgaW8gYXQgMHgl eCBmb3IgVGVsZXMgUzAvMTYuMyFcbiIsDQorIAkJCXVuaXQsIHNjLT5zY19w b3J0KTsNCisgCQlpc2ljX2RldGFjaF9jb21tb24oZGV2KTsNCisgCQlyZXR1 cm4gRU5YSU87DQorIAl9DQogIAlzYy0+c2NfcmVzb3VyY2VzLmlvX3JpZFsx XSA9IDE7CQ0KICAJYnVzX3NldF9yZXNvdXJjZShkZXYsIFNZU19SRVNfSU9Q T1JULCAxLA0KISAJCXNjLT5zY19wb3J0LUlTQUNfT0ZGUywgMHgyMCk7DQog IAlzYy0+c2NfcmVzb3VyY2VzLmlvX2Jhc2VbMV0gPQ0KICAJCWJ1c19hbGxv Y19yZXNvdXJjZShkZXYsIFNZU19SRVNfSU9QT1JULA0KICAJCQkJICAgJnNj LT5zY19yZXNvdXJjZXMuaW9fcmlkWzFdLA0KKioqKioqKioqKioqKioqDQoq KiogMjA5LDIxNSAqKioqDQogIAkNCiAgCXNjLT5zY19yZXNvdXJjZXMuaW9f cmlkWzJdID0gMjsNCiAgCWJ1c19zZXRfcmVzb3VyY2UoZGV2LCBTWVNfUkVT X0lPUE9SVCwgMiwNCiEgCQlzYy0+c2NfcG9ydC1IU0NYQV9PRkZTLCAweDQw KTsNCiAgCXNjLT5zY19yZXNvdXJjZXMuaW9fYmFzZVsyXSA9DQogIAkJYnVz X2FsbG9jX3Jlc291cmNlKGRldiwgU1lTX1JFU19JT1BPUlQsDQogIAkJCQkg ICAmc2MtPnNjX3Jlc291cmNlcy5pb19yaWRbMl0sDQotLS0gMjI1LDIzMSAt LS0tDQogIAkNCiAgCXNjLT5zY19yZXNvdXJjZXMuaW9fcmlkWzJdID0gMjsN CiAgCWJ1c19zZXRfcmVzb3VyY2UoZGV2LCBTWVNfUkVTX0lPUE9SVCwgMiwN CiEgCQlzYy0+c2NfcG9ydC1IU0NYQV9PRkZTLCAweDIwKTsNCiAgCXNjLT5z Y19yZXNvdXJjZXMuaW9fYmFzZVsyXSA9DQogIAkJYnVzX2FsbG9jX3Jlc291 cmNlKGRldiwgU1lTX1JFU19JT1BPUlQsDQogIAkJCQkgICAmc2MtPnNjX3Jl c291cmNlcy5pb19yaWRbMl0sDQoqKioqKioqKioqKioqKioNCioqKiAyMjQs MjMwICoqKioNCiAgDQogIAlzYy0+c2NfcmVzb3VyY2VzLmlvX3JpZFszXSA9 IDM7DQogIAlidXNfc2V0X3Jlc291cmNlKGRldiwgU1lTX1JFU19JT1BPUlQs IDMsDQohIAkJc2MtPnNjX3BvcnQtSFNDWEJfT0ZGUywgMHg0MCk7DQogIAlz Yy0+c2NfcmVzb3VyY2VzLmlvX2Jhc2VbM10gPQ0KICAJCWJ1c19hbGxvY19y ZXNvdXJjZShkZXYsIFNZU19SRVNfSU9QT1JULA0KICAJCQkJICAgJnNjLT5z Y19yZXNvdXJjZXMuaW9fcmlkWzNdLA0KLS0tIDI0MCwyNDYgLS0tLQ0KICAN CiAgCXNjLT5zY19yZXNvdXJjZXMuaW9fcmlkWzNdID0gMzsNCiAgCWJ1c19z ZXRfcmVzb3VyY2UoZGV2LCBTWVNfUkVTX0lPUE9SVCwgMywNCiEgCQlzYy0+ c2NfcG9ydC1IU0NYQl9PRkZTLCAweDIwKTsNCiAgCXNjLT5zY19yZXNvdXJj ZXMuaW9fYmFzZVszXSA9DQogIAkJYnVzX2FsbG9jX3Jlc291cmNlKGRldiwg U1lTX1JFU19JT1BPUlQsDQogIAkJCQkgICAmc2MtPnNjX3Jlc291cmNlcy5p b19yaWRbM10sDQo= --0-1889213078-951089695=:20564-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Feb 21 5:38:22 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from spree.nando.de (spree.nando.de [212.41.160.42]) by hub.freebsd.org (Postfix) with ESMTP id 46B4637BD4F for ; Mon, 21 Feb 2000 05:38:12 -0800 (PST) (envelope-from dave@turbocat.de) Received: from harvey.aball.de (root@harvey.aball.de [212.41.160.46]) by spree.nando.de (8.8.8/990525/wpv/CA-3) with ESMTP id OAA26570 for ; Mon, 21 Feb 2000 14:37:53 +0100 (MET) Received: from turbocat.de (uucp@localhost) by harvey.aball.de (8.9.3/8.9.3) with UUCP id OAA24853 for freebsd-isdn@FreeBSD.ORG; Mon, 21 Feb 2000 14:37:50 +0100 Received: from cat.turbocat.de (cat [212.41.163.194]) by alice.turbocat.de (8.8.8/8.8.8) with ESMTP id OAA23100 for ; Mon, 21 Feb 2000 14:37:18 +0100 (CET) Received: (from dave@localhost) by cat.turbocat.de (8.8.5/8.7.3) id OAA00329 for freebsd-isdn@FreeBSD.ORG; Mon, 21 Feb 2000 14:37:19 +0100 (MET) Message-Id: <200002211337.OAA00329@cat.turbocat.de> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) X-Nextstep-Mailer: Mail 4.0 (Enhance 2.0b4) Received: by NeXT.Mailer (1.148) From: David Wetzel Date: Mon, 21 Feb 2000 14:37:19 +0100 To: ISDN-List Subject: UP and RUNNING but no Connection. Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I do not know if that is related to Jan's problem: yesterday, I noticed that my web browser did not show some pages and I could not ping my own www server that is behind my ISDN link to the internet. A ifconfig isp0 down and ifconfig isp0 up after this fixed the problem. Today, the same error... I tried to call my answering machine and it worked. Normally that should not work because my Fritz! is connected to the same (internal Ackermann) S0 as my Siemens Gigaset 2016 ISDN. I replaced the handset by "pushing the red button" [TM] and used ifconfig as yesterday. The OS is still NetBSD 1.4.1. --- _ _ _(_)(_)_ David Wetzel, Turbocat's Development, (_) __ (_) Buchhorster Strasse 23, D-16567 Muehlenbeck/Berlin, FRG, _/ \_ Fax +49 33056 82835 NeXTmail dave@turbocat.de (______) http://www.turbocat.de/ DEVELOPMENT * CONSULTING * ADMINISTRATION To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Feb 21 7:29:40 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id 670D737BCAB for ; Mon, 21 Feb 2000 07:29:32 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by nets5.rz.rwth-aachen.de (8.9.1a/8.9.1/10) with ESMTP id QAA08480 for ; Mon, 21 Feb 2000 16:29:30 +0100 (MET) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by campino.informatik.rwth-aachen.de (8.9.1a/8.9.1/3) with ESMTP id QAA24133 for ; Mon, 21 Feb 2000 16:30:08 +0100 (MET) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.9.3/8.6.9) id QAA08839 for freebsd-isdn@freebsd.org; Mon, 21 Feb 2000 16:29:32 +0100 (CET) Date: Mon, 21 Feb 2000 16:29:32 +0100 (CET) From: Christoph Kukulies Message-Id: <200002211529.QAA08839@gil.physik.rwth-aachen.de> To: freebsd-isdn@freebsd.org Subject: doctor, it hurts - anamesis Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (FreeBSD 3.4R, i4b 0.83) Hellmuth - Dr. i4b - ;-) I'm sending you this syslog from a couple of minutes ago when my isdn connection went down and only a reboot of the system could revive it. I have solved the 'Putzfrau' syndrome by a cable strap meanwhile so it an unplugged cable cannot be the cause. I only can say that the situation has worsened since I'm using i4bisppp instead of hdlc/raw IP and fixed IP addresses before. Actually I've never seen this kind of problems before using i4bispp. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de Feb 21 08:39:30 isdn-gtwy squid[266]: Starting Squid Cache version 1.1.10 for i386-unknown-freebsd3.0... Feb 21 08:39:31 isdn-gtwy sshd[272]: log: RSA key generation complete. Feb 21 08:39:33 isdn-gtwy /kernel: i4b-L2-i4b_T202_timeout: unit 0, N202 = 3 Feb 21 08:39:33 isdn-gtwy /kernel: i4b: unit 0, assigned TEI = 101 = 0x65 Feb 21 08:39:36 isdn-gtwy squid[266]: Unlinkd pipe opened on FD 13 Feb 21 08:39:37 isdn-gtwy squid[266]: Ready to serve requests. Feb 21 08:39:41 isdn-gtwy login: login on ttyv0 as kuku Feb 21 16:04:55 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated Feb 21 16:04:57 isdn-gtwy last message repeated 2 times Feb 21 16:04:57 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07 Feb 21 16:04:57 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Feb 21 16:04:58 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated Feb 21 16:04:58 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07 Feb 21 16:04:58 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Feb 21 16:04:59 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated Feb 21 16:04:59 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07 Feb 21 16:04:59 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Feb 21 16:05:00 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated Feb 21 16:05:00 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07 Feb 21 16:05:00 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Feb 21 16:05:01 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated Feb 21 16:05:01 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated Feb 21 16:05:01 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07 Feb 21 16:05:01 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Feb 21 16:05:02 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated Feb 21 16:05:02 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated Feb 21 16:05:02 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07 Feb 21 16:05:02 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Feb 21 16:05:03 isdn-gtwy /kernel: i4b: unit 0, removed TEI = 101 = 0x65 Feb 21 16:05:03 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated Feb 21 16:05:03 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated Feb 21 16:05:05 isdn-gtwy /kernel: i4b-L2-i4b_T202_timeout: unit 0, N202 = 3 Feb 21 16:05:05 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated Feb 21 16:05:05 isdn-gtwy /kernel: i4b-L2-i4b_T202_timeout: unit 0, N202 = 2 Feb 21 16:05:05 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated Feb 21 16:05:07 isdn-gtwy /kernel: i4b-L2-i4b_T202_timeout: unit 0, N202 = 3 Feb 21 16:05:07 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated Feb 21 16:15:13 isdn-gtwy su: kuku to root on /dev/ttyp4 Feb 21 16:15:21 isdn-gtwy /kernel: i4b-L2-i4b_dl_data_req: unit 0 ERROR in state [ST_EST_AW_TEI], freeing mbuf Feb 21 16:15:51 isdn-gtwy /kernel: i4b-L3-T305_timeout: DISC not answered, cr = 82 Feb 21 16:15:51 isdn-gtwy /kernel: i4b-L2-i4b_dl_data_req: unit 0 ERROR in state [ST_EST_AW_TEI], freeing mbuf Feb 21 16:15:51 isdn-gtwy /kernel: pid 370 (qvwm), uid 100: exited on signal 6 (core dumped) Feb 21 16:15:55 isdn-gtwy /kernel: i4b-L3-T308_timeout: REL not answered, cr = 82 Feb 21 16:16:00 isdn-gtwy /kernel: i4b-L2-F_ILL: FSM function F_ILL executing Feb 21 16:16:00 isdn-gtwy /kernel: i4b-L2-i4b_next_l2state: FSM illegal state, state = ST_EST_AW_TEI, event = EV_DLESTRQ! Feb 21 16:16:04 isdn-gtwy /kernel: i4b-L3-T303_timeout: SETUP not answered, cr = 43 Feb 21 16:16:04 isdn-gtwy /kernel: i4b-L3-next_l3state: FSM illegal state, state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! Feb 21 16:16:22 isdn-gtwy su: kuku to root on /dev/ttyv0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 22 1: 5: 3 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id B270A37B63F; Tue, 22 Feb 2000 01:04:53 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.webweaving.org (dhcp36.calcaphon.com [10.0.1.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id JAA26808; Tue, 22 Feb 2000 09:04:50 GMT (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id XAA00450; Mon, 21 Feb 2000 23:31:57 GMT (envelope-from n_hibma@calcaphon.com) Date: Mon, 21 Feb 2000 23:31:56 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Hellmuth Michaelis Cc: Andrew Gordon , dfr@nlsystems.com, current@freebsd.org, freebsd-isdn@freebsd.org Subject: Re: Big ATA problems In-Reply-To: <20000220191947.A58381F17@bert.kts.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Maybe this is a silly suggestion, but could someone with a card like that boot it in a Windows environment and tell us what that hardware manager tells us about hardware requirements the card would have if it is configured for the '0x160' address (whatever that configuration is on the card I don't know)? Nick > > > A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC > > > chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b, > > > the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73. > > > > But in the case of the teles16.3, it does _not_ use offsets 0x00-0x3b in > > the HSCX or ISAC: the ASIC on the card has 'folded' the address space so > > that the fifo appears at an address 3 bytes after the last register (0x3e > > with the current scheme - see tels0163_read_fifo()). > > Oh yes, you are right! I was (and am still a bit) confused. > > So it uses 0x20-0x3e for the ISAC and 0x20-0x3e and 0x60-0x7e for the HSCX > and at least three bytes at its base address, right ? > > This makes sense. Now the real question left is are this the only locations > where the card is driving the bus ? > > hellmuth > -- > Hellmuth Michaelis hm@kts.org Hamburg, Europe > We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 22 2: 8:50 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from devil.intervisors.nl (office.intervisors.nl [194.109.13.117]) by hub.freebsd.org (Postfix) with ESMTP id 381B937B64E for ; Tue, 22 Feb 2000 02:08:48 -0800 (PST) (envelope-from luke@roberts.nl) Received: from roberts4 (roberts4.intranet.iv [192.168.0.8]) by devil.intervisors.nl (8.9.3/8.9.3) with ESMTP id LAA07316 for ; Tue, 22 Feb 2000 11:04:23 +0100 (CET) (envelope-from luke@roberts.nl) Message-Id: <4.2.2.20000222110540.00aafa30@pop.roberts.nl> X-Sender: luke@pop.roberts.nl X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Tue, 22 Feb 2000 11:10:25 +0100 To: freebsd-isdn@FreeBSD.ORG From: Luke Roberts Subject: small dialing in problem Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Every now and then when i4b 0.83 (using i4bisppp on Free BSD 3.2 with a Teles 16.3 ISA version 1.1) tries to dial in to my provider it won't get to the "switched to state 3" part of dialing in. It seems to hang at "Outgoing call active" and I see a few bytes going in and out and eventually the connection is broken. Manually hanging up the channel and causing a redial does the trick to get to "switched to state 3". Does anybody know what's going wrong here? Would upgrading to version 0.90 help? Thanks, Luke To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 22 6: 1:18 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from orion.vo.lu (orion.telephonie.lu [212.24.194.7]) by hub.freebsd.org (Postfix) with ESMTP id DB7C437B67D for ; Tue, 22 Feb 2000 06:01:15 -0800 (PST) (envelope-from jbh@ddl.lu) Received: from ddl.lu ([212.24.192.139]) by orion.vo.lu (Post.Office MTA v3.5.3 release 223 ID# 0-61327U6400L500S0V35) with ESMTP id lu for ; Tue, 22 Feb 2000 15:01:04 +0100 Message-ID: <38B29666.CF68D0E1@ddl.lu> Date: Tue, 22 Feb 2000 15:00:06 +0100 From: Joakim Hernberg Organization: Digital Design Luxembourg sarl X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-isdn@FreeBSD.ORG Subject: i4b message Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Anyone know what the following means ? i4b-L3-i4b_decode_q931: protocol discriminator 0x40 != Q.931 -- Joakim Hernberg Digital Design Luxembourg sarl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 22 6: 9:25 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from orion.vo.lu (orion.telephonie.lu [212.24.194.7]) by hub.freebsd.org (Postfix) with ESMTP id 40A4537B692 for ; Tue, 22 Feb 2000 06:09:22 -0800 (PST) (envelope-from jbh@ddl.lu) Received: from ddl.lu ([212.24.192.153]) by orion.vo.lu (Post.Office MTA v3.5.3 release 223 ID# 0-61327U6400L500S0V35) with ESMTP id lu for ; Tue, 22 Feb 2000 15:09:21 +0100 Message-ID: <38B2986C.D3C6FBDA@ddl.lu> Date: Tue, 22 Feb 2000 15:08:44 +0100 From: Joakim Hernberg Organization: Digital Design Luxembourg sarl X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-isdn@FreeBSD.ORG Subject: ppp disconnect problems ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I have a "funny" problem lately. I noticed that sometimes I could not connect to the internet, and that i4b had been connnecting once a minute for a few hours, after consulting with my provider they came up with the following answer. Their terminal servers consider me as logged in, and refuse the second connection, the reason being that the terminal servers never see that I have already disconnected. They claim that I am the only customer with such a problem. Is there some kind of protocol on either ppp or isdn level, which tells the remote that you are disconnecting, or is this a problem with their servers ? -- Joakim Hernberg Digital Design Luxembourg sarl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 22 6:43:48 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id A2A1037B69E for ; Tue, 22 Feb 2000 06:43:45 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1450 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Tue, 22 Feb 2000 15:43:01 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 7818038E2; Tue, 22 Feb 2000 15:43:00 +0100 (MET) Subject: Re: i4b message In-Reply-To: <38B29666.CF68D0E1@ddl.lu> from Joakim Hernberg at "Feb 22, 0 03:00:06 pm" To: jbh@ddl.lu (Joakim Hernberg) Date: Tue, 22 Feb 2000 15:43:00 +0100 (MET) Cc: freebsd-isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 640 Message-Id: <20000222144300.7818038E2@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Joakim Hernberg: > Anyone know what the following means ? > > i4b-L3-i4b_decode_q931: protocol discriminator 0x40 != Q.931 This means that non-Q.931 packets were detected on the D-channel. The protocol discriminator for Q.931 is 0x08. 0x040 and 0x041 were/are used by the old 1TR6 protocol. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 22 8:35:20 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from orion.vo.lu (orion.telephonie.lu [212.24.194.7]) by hub.freebsd.org (Postfix) with ESMTP id 8F30A37B6EA for ; Tue, 22 Feb 2000 08:35:17 -0800 (PST) (envelope-from jbh@ddl.lu) Received: from ddl.lu ([212.24.192.196]) by orion.vo.lu (Post.Office MTA v3.5.3 release 223 ID# 0-61327U6400L500S0V35) with ESMTP id lu; Tue, 22 Feb 2000 17:35:14 +0100 Message-ID: <38B2BA9D.2F9B008D@ddl.lu> Date: Tue, 22 Feb 2000 17:34:37 +0100 From: Joakim Hernberg Organization: Digital Design Luxembourg sarl X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: hm@hcs.de, freebsd-isdn@FreeBSD.ORG Subject: Re: i4b message References: <20000222144300.7818038E2@hcswork.hcs.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hellmuth Michaelis wrote: > This means that non-Q.931 packets were detected on the D-channel. The > protocol discriminator for Q.931 is 0x08. 0x040 and 0x041 were/are > used by the old 1TR6 protocol. Then this is something caused by the Philips ISDN PBX of the client, and can be safely ignored ? -- Joakim Hernberg Digital Design Luxembourg sarl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 22 9:55:12 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from alvman.RoBIN.de (alvman.robin.de [193.174.7.33]) by hub.freebsd.org (Postfix) with ESMTP id 4D84B37B797 for ; Tue, 22 Feb 2000 09:54:54 -0800 (PST) (envelope-from ah@haakh.de) Received: from haakh.de (louise.IbHaakh.de [192.168.63.11]) by alvman.RoBIN.de (8.9.3/8.9.3) with ESMTP id SAA15577; Tue, 22 Feb 2000 18:53:51 +0100 (CET) (envelope-from ah@haakh.de) Message-ID: <38B2CD2D.4ECFCA15@haakh.de> Date: Tue, 22 Feb 2000 18:53:50 +0100 From: Andreas Haakh Organization: =?iso-8859-1?Q?Ingenieurb=FCro=20f=FCr?= Baustatik X-Mailer: Mozilla 4.7 [de] (WinNT; I) X-Accept-Language: de,en,fr MIME-Version: 1.0 To: hm@hcs.de Cc: Joakim Hernberg , freebsd-isdn@FreeBSD.ORG Subject: Re: i4b message References: <20000222144300.7818038E2@hcswork.hcs.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hellmuth Michaelis schrieb: > >From the keyboard of Joakim Hernberg: > > > Anyone know what the following means ? > > > > i4b-L3-i4b_decode_q931: protocol discriminator 0x40 != Q.931 > > This means that non-Q.931 packets were detected on the D-channel. The > protocol discriminator for Q.931 is 0x08. 0x040 and 0x041 were/are > used by the old 1TR6 protocol. > > hellmuth > Is it possible to suppress these messages?? Andreas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 22 11: 0:29 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id 256BE37B751 for ; Tue, 22 Feb 2000 11:00:27 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by nets5.rz.rwth-aachen.de (8.9.1a/8.9.1/10) with ESMTP id UAA11282 for ; Tue, 22 Feb 2000 20:00:25 +0100 (MET) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by campino.informatik.rwth-aachen.de (8.9.1a/8.9.1/3) with ESMTP id UAA19671 for ; Tue, 22 Feb 2000 20:01:02 +0100 (MET) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.9.3/8.6.9) id UAA18594 for freebsd-isdn@freebsd.org; Tue, 22 Feb 2000 20:00:28 +0100 (CET) Date: Tue, 22 Feb 2000 20:00:28 +0100 (CET) From: Christoph Kukulies Message-Id: <200002221900.UAA18594@gil.physik.rwth-aachen.de> To: freebsd-isdn@freebsd.org Subject: i4b in -current source tree? Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I cvsuped src-all, built a 4.0-current system of today, built a kernel - phew, have things changed sinde 3.4 - my old isdnd seems to work but I also would like to be at the leading and bleeding edge with i4b. Where is i4b userland in the src tree, when I cvsup? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 22 11: 2:33 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from fep02-svc.mail.telepac.pt (fep02-svc.mail.telepac.pt [194.65.5.201]) by hub.freebsd.org (Postfix) with ESMTP id E330037B739; Tue, 22 Feb 2000 11:02:15 -0800 (PST) (envelope-from jpedras@webvolution.net) Received: from manecao.tafkap.priv ([194.65.206.92]) by fep02-svc.mail.telepac.pt (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000222190458.NCWD4775.fep02-svc.mail.telepac.pt@manecao.tafkap.priv>; Tue, 22 Feb 2000 19:04:58 +0000 Content-Length: 2719 Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 22 Feb 2000 19:01:24 -0000 (GMT) Reply-To: Joao Pedras From: Joao Pedras To: freebsd-net@freebsd.org Subject: dropping connection Cc: freebsd-isdn@freebsd.org Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all. I have been using FreeBSD to use ordinary pc's as routers. Several of those machines use the i4b daemon. Althought this IS NOT a FreeBSD or i4b problem, I would like to submit it to your consideration, so I could have an independent opinion about it. Several of these routers connect through one of the major isp in our country. Only in these installations I face the problem of disconnection when idle after 'x' time, to don't work (i.e. no matter how I configure the isdnd it never drops the connection). The exact same configuration on other isp works properly and performs the disconnect. The problem is that this particular isp has their routers configured to send some kind of keep alive, whenever the connection is idle. I ran tcpdump on the isp0 interface and got the following : 19:45:36.787026 ID-063 LCP: Echo-Request, Magic-Number=-495599889 093f 000c e275 beef 0258 d272 19:45:36.787052 ID-063 LCP: Echo-Reply, Magic-Number=1285595741 0a3f 000c 4ca0 a25d 0258 d272 19:45:46.789844 ID-064 LCP: Echo-Request, Magic-Number=-495599889 0940 000c e275 beef 0258 d272 19:45:46.789865 ID-064 LCP: Echo-Reply, Magic-Number=1285595741 0a40 000c 4ca0 a25d 0258 d272 19:45:56.793551 ID-065 LCP: Echo-Request, Magic-Number=-495599889 0941 000c e275 beef 0258 d272 19:45:56.793570 ID-065 LCP: Echo-Reply, Magic-Number=1285595741 0a41 000c 4ca0 a25d 0258 d272 19:46:06.796127 ID-066 LCP: Echo-Request, Magic-Number=-495599889 0942 000c e275 beef 0258 d272 19:46:06.796147 ID-066 LCP: Echo-Reply, Magic-Number=1285595741 0a42 000c 4ca0 a25d 0258 d272 Frankly, I do not know of to interpret this data. Do you find this situation normal ? I spoke with them and they didn't gave me any 'real' reason to be doing this. They said they won't change their configuration. They suggested me to write some kind of filter to ignore this. Is this easily achiavable ? Just for curiosity, I read in the IOS 12.0 Configurartion book, that the keep alive in Cisco routers could be enabled optionally. I really don't see any use to this configuration. ]:( Thanks for your help Joao ^\ /^ O O ----------------------------------------o00-(_)-00o-------------------------- I often quote myself; it adds spice to my conversation. -- G. B. Shaw ----------------------------------------------------------------------------- PGP key available upon request or may be cut at http://pedras.webvolution.net/pgpkey.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 22 11:50:32 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 7355537B766 for ; Tue, 22 Feb 2000 11:50:28 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1501 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Tue, 22 Feb 2000 20:49:53 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id E6A0238E2; Tue, 22 Feb 2000 20:49:51 +0100 (MET) Subject: Re: i4b message In-Reply-To: <38B2BA9D.2F9B008D@ddl.lu> from Joakim Hernberg at "Feb 22, 0 05:34:37 pm" To: jbh@ddl.lu (Joakim Hernberg) Date: Tue, 22 Feb 2000 20:49:51 +0100 (MET) Cc: hm@hcs.de, freebsd-isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 667 Message-Id: <20000222194951.E6A0238E2@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Joakim Hernberg: > > This means that non-Q.931 packets were detected on the D-channel. The > > protocol discriminator for Q.931 is 0x08. 0x040 and 0x041 were/are > > used by the old 1TR6 protocol. > > Then this is something caused by the Philips ISDN PBX of the client, Seems so. > and can be safely ignored ? Yes. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 22 11:55:48 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 013A637B743 for ; Tue, 22 Feb 2000 11:55:46 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (2053 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Tue, 22 Feb 2000 20:55:44 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 3C54038E2; Tue, 22 Feb 2000 20:55:44 +0100 (MET) Subject: Re: i4b message In-Reply-To: <38B2CD2D.4ECFCA15@haakh.de> from Andreas Haakh at "Feb 22, 0 06:53:50 pm" To: ah@haakh.de (Andreas Haakh) Date: Tue, 22 Feb 2000 20:55:43 +0100 (MET) Cc: freebsd-isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1243 Message-Id: <20000222195544.3C54038E2@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Andreas Haakh: > > > Anyone know what the following means ? > > > > > > i4b-L3-i4b_decode_q931: protocol discriminator 0x40 != Q.931 > > > > This means that non-Q.931 packets were detected on the D-channel. The > > protocol discriminator for Q.931 is 0x08. 0x040 and 0x041 were/are > > used by the old 1TR6 protocol. > > Is it possible to suppress these messages?? In my current sources, layer3/i4b_q931.c ~line 136 now looks like this: /* check protocol discriminator */ if(*msg_ptr != PD_Q931) { static int protoflag = -1; /* print only once .. */ if(*msg_ptr != protoflag) { DBGL3(L3_P_ERR, "i4b_decode_q931", ("unknown protocol discriminator 0x%x!\n", *msg_ptr)); protoflag = *msg_ptr; } return; } hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 22 15:27:50 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from awfulhak.org (dynamic-51.max3-du-ws.dialnetwork.pavilion.co.uk [212.74.9.51]) by hub.freebsd.org (Postfix) with ESMTP id 3E7D137B7EA for ; Tue, 22 Feb 2000 15:27:40 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@shift.lan.awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA48108; Tue, 22 Feb 2000 23:22:40 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA42638; Tue, 22 Feb 2000 23:22:37 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200002222322.XAA42638@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Joakim Hernberg Cc: freebsd-isdn@FreeBSD.org, brian@hak.lan.awfulhak.org Subject: Re: ppp disconnect problems ? In-Reply-To: Message from Joakim Hernberg of "Tue, 22 Feb 2000 15:08:44 +0100." <38B2986C.D3C6FBDA@ddl.lu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Feb 2000 23:22:37 +0000 From: Brian Somers Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hello, > > I have a "funny" problem lately. I noticed that sometimes I could not > connect to the internet, and that i4b had been connnecting once a minute > for a few hours, after consulting with my provider they came up with the > following answer. Their terminal servers consider me as logged in, and > refuse the second connection, the reason being that the terminal servers > never see that I have already disconnected. > > They claim that I am the only customer with such a problem. > > Is there some kind of protocol on either ppp or isdn level, which tells > the remote that you are disconnecting, or is this a problem with their > servers ? If you've got version 1.8 or less of i4b/drivers/i4b_rbch.c then the problem is local - you need at least version 1.9 which was committed to -current and -stable at the end of November last year. I've attached the [small] patch just in case - your symptoms sound *very* familiar.... > -- > > Joakim Hernberg > Digital Design Luxembourg sarl -- Brian Don't _EVER_ lose your sense of humour ! Index: i4b_rbch.c =================================================================== RCS file: /home/ncvs/src/sys/i4b/driver/i4b_rbch.c,v retrieving revision 1.8 retrieving revision 1.9 diff -r1.8 -r1.9 30c30 < * $FreeBSD: src/sys/i4b/driver/i4b_rbch.c,v 1.8 1999/09/25 18:24:18 phk Exp $ --- > * $FreeBSD: src/sys/i4b/driver/i4b_rbch.c,v 1.9 1999/11/28 16:17:01 brian Exp $ 308c308 < i4b_l4_disconnect_ind(rbch_softc[unit].cd); --- > i4b_l4_drvrdisc(BDRV_RBCH, unit); 556c556 < i4b_l4_disconnect_ind(rbch_softc[unit].cd); --- > i4b_l4_drvrdisc(BDRV_RBCH, unit); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Feb 23 7: 2: 3 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from godfather.webvolution.net (unknown.cust-X.hecenter.com [208.231.0.74]) by hub.freebsd.org (Postfix) with ESMTP id ABB3637B8E3; Wed, 23 Feb 2000 07:01:52 -0800 (PST) (envelope-from jpedras@webvolution.net) Received: (from nobody@localhost) by godfather.webvolution.net (13.5.3/13.5.3) id PAA37329; Wed, 23 Feb 2000 15:00:58 GMT (envelope-from jpedras@webvolution.net) Date: Wed, 23 Feb 2000 15:00:58 GMT Message-Id: <200002231500.PAA37329@godfather.webvolution.net> X-Authentication-Warning: godfather.webvolution.net: nobody set sender to jpedras@webvolution.net using -f From: Joao Pedras To: Gary Jennejohn Reply-To: Joao Pedras Cc: freebsd-net@freebsd.org, freebsd-isdn@freebsd.org References: <200002231102.MAA45542@peedub.muc.de> In-Reply-To: <200002231102.MAA45542@peedub.muc.de> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP3 Imap webMail Program 2.0.11 X-Originating-IP: 193.137.208.1 Subject: Re: dropping connection Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Quoting Gary Jennejohn : > Joao Pedras writes: > [snip keep-alives from ISP] > >Do you find this situation normal ? I spoke with them and they didn't gave > me > >any 'real' reason to be doing this. They said they won't change their > >configuration. > > > > They're probably doing it so they can catch connections which were not > shut down in a clean manner. It's a legitimate thing to do. But is it necessary to do it every 5/10 seconds ? > > >They suggested me to write some kind of filter to ignore this. > > > contrib/lcp-patch2.tar.uu in the isdn4bsd distribution is supposed to > fix this. The problem is that it turns off the normal short hold timeout > handling. And it's against a really old version of isdn4bsd. But it > may help. I will look into it. Thanks ------------------------------- Powered by Webvolution Networks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Feb 23 9: 1:29 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from morannon.fido.de (morannon.faho.RWTH-Aachen.DE [134.130.57.8]) by hub.freebsd.org (Postfix) with ESMTP id 03A3637B913 for ; Wed, 23 Feb 2000 09:01:17 -0800 (PST) (envelope-from tobi@bland.fido.de) Received: from gate.fido.de (news@localhost) by morannon.fido.de (8.9.3/8.9.3/redhat6-morannon-4.4) with FIDOGATE id SAA09199; Wed, 23 Feb 2000 18:01:03 +0100 Received: by sungate-ftn.fido.de (FIDOGATE 4.3.6) id AA09197; Wed, 23 Feb 2000 18:01:03 +0100 Date: Wed, 23 Feb 2000 17:26:14 +0100 From: tobi@bland.fido.de (Tobias Ernst) Reply-To: tobi@physcip.uni-stuttgart.de (Tobias Ernst) Subject: early hangup causing exorbitant telecom fees Message-ID: To: freebsd-isdn@freebsd.org Organization: Fido.DE domain gateway (Moving Bits e.V. / IN e.V.) Lines: 51 X-Gateway: FIDO morannon.fido.de [FIDOGATE 4.3.6] X-FTN-From: Tobias Ernst @ 242:7600/1.0 X-FTN-To: UUCP @ 242:4900/99.0 X-FTN-Via: 242:7600/0@fido.de @20000223.173257 CFR-OS/2 20000121-devel X-FTN-Via: FIDOGATE/ftntoss 242:1000/1.0, Wed Feb 23 2000 at 18:01:01 CET X-FTN-Domain: Z242@fidode MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hallo All! Could you please tell me, what was happening here (see below)? This went on for 14 hours and caused me about 2300 DM telecom fees (they charge at least 0.12 DM per connect here). I have configured isdnd with autodial and an idle timeout of 60 seconds, and it has worked for months now, so why on earth to I get a *local* disconnect after just one second here? This is an i4b bug, isn't it? Why does it say "local dissconnect / normal call cleareanc" when actually there must have been some error? This way, it thinks everything is OK and none of the timeout / retry counters that usually should prevent such a disaster get activated. And do you see any chance that I could argue the Telekom into not having to pay this abhorrent sum? (The remote site is an Ascend router run *by the Telekom* for our University, so if it is an error on the remote site, this could help a lot) Kind Regards, Tobias. 02.02.2000 02:03:15 CHD 00333 UNIHOME dialing out from 8700334 to 07116870180 02.02.2000 02:03:15 CHD 00333 UNIHOME outgoing call proceeding (ctl 0, ch 0) 02.02.2000 02:03:16 CHD 00333 UNIHOME outgoing call active (ctl 0, ch 0, isp0) 02.02.2000 02:03:16 DBG isp0: switched to state 3 02.02.2000 02:03:17 CHD 00333 UNIHOME outgoing call disconnected (local) 02.02.2000 02:03:17 CHD 00333 UNIHOME cause 0: normal call clearing (I4B) 02.02.2000 02:03:17 CHD 00333 UNIHOME charging: 0 units, 1 seconds 02.02.2000 02:03:17 CHD 00333 UNIHOME accounting: in 94, out 84 (in 0, out 0) 02.02.2000 02:03:17 CHD 00334 UNIHOME rate 60 sec/unit (aocd, default) 02.02.2000 02:03:17 CHD 00334 UNIHOME dialing out from 8700334 to 07116870180 02.02.2000 02:03:17 CHD 00334 UNIHOME outgoing call proceeding (ctl 0, ch 0) 02.02.2000 02:03:18 CHD 00334 UNIHOME outgoing call active (ctl 0, ch 0, isp0) 02.02.2000 02:03:18 DBG isp0: switched to state 3 02.02.2000 02:03:19 CHD 00334 UNIHOME outgoing call disconnected (local) 02.02.2000 02:03:19 CHD 00334 UNIHOME cause 0: normal call clearing (I4B) 02.02.2000 02:03:19 CHD 00334 UNIHOME charging: 0 units, 1 seconds 02.02.2000 02:03:19 CHD 00334 UNIHOME accounting: in 94, out 84 (in 0, out 0) 02.02.2000 02:03:19 CHD 00335 UNIHOME rate 60 sec/unit (aocd, default) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Feb 23 11: 4:24 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from spree.nando.de (spree.nando.de [212.41.160.42]) by hub.freebsd.org (Postfix) with ESMTP id E86E137B6F9 for ; Wed, 23 Feb 2000 11:01:07 -0800 (PST) (envelope-from dave@turbocat.de) Received: from harvey.aball.de (root@harvey.aball.de [212.41.160.46]) by spree.nando.de (8.8.8/990525/wpv/CA-3) with ESMTP id TAA01035 for ; Wed, 23 Feb 2000 19:59:27 +0100 (MET) Received: from turbocat.de (uucp@localhost) by harvey.aball.de (8.9.3/8.9.3) with UUCP id TAA21904 for freebsd-isdn@FreeBSD.ORG; Wed, 23 Feb 2000 19:59:21 +0100 Received: from cat.turbocat.de (cat [212.41.163.194]) by alice.turbocat.de (8.8.8/8.8.8) with ESMTP id TAA14872 for ; Wed, 23 Feb 2000 19:58:55 +0100 (CET) Received: (from dave@localhost) by cat.turbocat.de (8.8.5/8.7.3) id TAA00584 for freebsd-isdn@FreeBSD.ORG; Wed, 23 Feb 2000 19:59:03 +0100 (MET) Message-Id: <200002231859.TAA00584@cat.turbocat.de> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) X-Nextstep-Mailer: Mail 4.0 (Enhance 2.0b4) Received: by NeXT.Mailer (1.148) From: David Wetzel Date: Wed, 23 Feb 2000 19:59:03 +0100 To: ISDN-List Subject: compression for isp? Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Feb 23 19:54:04 alice /netbsd: isp0: ipcp parse opts: compression [rej] address send conf-rej Does this mean that the Cisco wants compression and i4b does not? BTW: alice is up 7 days now. The patch seemed to help. --- _ _ _(_)(_)_ David Wetzel, Turbocat's Development, (_) __ (_) Buchhorster Strasse 23, D-16567 Muehlenbeck/Berlin, FRG, _/ \_ Fax +49 33056 82835 NeXTmail dave@turbocat.de (______) http://www.turbocat.de/ DEVELOPMENT * CONSULTING * ADMINISTRATION To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Feb 23 11:14:53 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from morannon.fido.de (morannon.faho.RWTH-Aachen.DE [134.130.57.8]) by hub.freebsd.org (Postfix) with ESMTP id CEB6F37B965 for ; Wed, 23 Feb 2000 11:11:16 -0800 (PST) (envelope-from tobi@bland.fido.de) Received: from gate.fido.de (news@localhost) by morannon.fido.de (8.9.3/8.9.3/redhat6-morannon-4.4) with FIDOGATE id UAA13633; Wed, 23 Feb 2000 20:11:04 +0100 Received: by sungate-ftn.fido.de (FIDOGATE 4.3.6) id AA13631; Wed, 23 Feb 2000 20:11:04 +0100 Date: Wed, 23 Feb 2000 19:33:06 +0100 From: tobi@bland.fido.de (Tobias Ernst) Reply-To: tobi@physcip.uni-stuttgart.de (Tobias Ernst) Subject: early hangup causing exorbitant telecom fees Message-ID: To: freebsd-isdn@freebsd.org (UUCP) Organization: Fido.DE domain gateway (Moving Bits e.V. / IN e.V.) Lines: 10 X-Gateway: FIDO morannon.fido.de [FIDOGATE 4.3.6] X-FTN-From: Tobias Ernst @ 242:7600/1.0 X-FTN-To: UUCP @ 242:4900/99.0 X-FTN-Via: 242:7600/0@fido.de @20000223.193450 CFR-OS/2 20000121-devel X-FTN-Via: FIDOGATE/ftntoss 242:1000/1.0, Wed Feb 23 2000 at 20:11:03 CET X-FTN-Domain: Z242@fidode MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hallo! TE> Could you please tell me, what was happening here (see below)? This I forgot to mention: This is with the i4b 0.8.x version that came with FreeBSD 3.4-STABLE cvsupped araound January. Viele Gr=FC=DFe, Tobias To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Feb 23 12:33:42 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id F019637BF02 for ; Wed, 23 Feb 2000 12:33:37 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id VAA47847; Wed, 23 Feb 2000 21:30:00 +0100 (CET) Message-Id: <200002232030.VAA47847@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: David Wetzel Cc: ISDN-List Subject: Re: compression for isp? Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 23 Feb 2000 19:59:03 +0100." <200002231859.TAA00584@cat.turbocat.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Feb 2000 21:30:00 +0100 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David Wetzel writes: >Hi, > >Feb 23 19:54:04 alice /netbsd: isp0: ipcp parse opts: compression [rej] >address send conf-rej > >Does this mean that the Cisco wants compression and i4b does not? > correct >BTW: alice is up 7 days now. The patch seemed to help. that's good --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Feb 23 12:33:47 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 6928237BF02 for ; Wed, 23 Feb 2000 12:33:43 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id VAA47853; Wed, 23 Feb 2000 21:31:24 +0100 (CET) Message-Id: <200002232031.VAA47853@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: tobi@physcip.uni-stuttgart.de (Tobias Ernst) Cc: freebsd-isdn@FreeBSD.org Subject: Re: early hangup causing exorbitant telecom fees Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 23 Feb 2000 17:26:14 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Feb 2000 21:31:24 +0100 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tobias Ernst writes: >Hallo All! > >Could you please tell me, what was happening here (see below)? See below. >And do you see any chance that I could argue the Telekom into not >having to pay this abhorrent sum? (The remote site is an Ascend router >run *by the Telekom* for our University, so if it is an error on the >remote site, this could help a lot) > Maybe you can convince someone at the Uni that the Telekom is at fault. With a little backing from the Uni you might be able to get the Telekom to admit that they made a mistake (hah !). >02.02.2000 02:03:15 CHD 00333 UNIHOME dialing out from 8700334 to >07116870180 >02.02.2000 02:03:15 CHD 00333 UNIHOME outgoing call proceeding (ctl 0, >ch 0) >02.02.2000 02:03:16 CHD 00333 UNIHOME outgoing call active (ctl 0, ch >0, isp0) >02.02.2000 02:03:16 DBG isp0: switched to state 3 >02.02.2000 02:03:17 CHD 00333 UNIHOME outgoing call disconnected >(local) >02.02.2000 02:03:17 CHD 00333 UNIHOME cause 0: normal call clearing >(I4B) >02.02.2000 02:03:17 CHD 00333 UNIHOME charging: 0 units, 1 seconds >02.02.2000 02:03:17 CHD 00333 UNIHOME accounting: in 94, out 84 (in 0, >out 0) Looks like the authentication is failing (that's what phase 3 is). The small number of bytes exchanged seems to corroborate that. Maybe they changed something on their end and didn't tell you. The best way to confirm that is to turn on debugging (ifconfig isp0 debug) and make a connection. Examine the output from the connection attempt, which shoukd be in /var/log/messages. It should be pretty clear whether the authentication failed from the trace. The local disconnect would happen as a result of an authentication failure. There was obviously something happening on your machine which was causing the connects. Mail delivery, perhaps ? --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 24 0:16:52 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 8D3DE37BB42 for ; Thu, 24 Feb 2000 00:16:47 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (3052 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Thu, 24 Feb 2000 09:16:46 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 7ABFD38E2; Thu, 24 Feb 2000 09:16:41 +0100 (MET) Subject: Re: early hangup causing exorbitant telecom fees In-Reply-To: from Tobias Ernst at "Feb 23, 0 05:26:14 pm" To: tobi@physcip.uni-stuttgart.de Date: Thu, 24 Feb 2000 09:16:41 +0100 (MET) Cc: freebsd-isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2179 Message-Id: <20000224081641.7ABFD38E2@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Tobias Ernst: > Could you please tell me, what was happening here (see below)? This > went on for 14 hours and caused me about 2300 DM telecom fees Welcome to the club! :-( I'm very sorry to hear this. First of all, with regard to the subject: this has nothing to do with "early hangup" it even looks like it has nothing to do with the ISDN part of i4b at all. > charge at least 0.12 DM per connect here). I have configured isdnd with > autodial and an idle timeout of 60 seconds, and it has worked for > months now, so why on earth to I get a *local* disconnect after just > one second here? I guess you are using some sort of PPP. I guess that your machine tried to reach the remote machine and somehow the login/authorization failed. The PPP layer then tried to reach the remote end again and again. > This is an i4b bug, isn't it? From what i see it is not a bug in the i4b ISDN code. In case you are using sppp, you might have been hit by the lcp-loop bug. > Why does it say "local > dissconnect / normal call cleareanc" when actually there must have been > some error? This are messages from the ISDN part of i4b. The PPP layer above it seemed to have closed the line and this is no error for the ISDN part. In fact they don't know each other and this is what it is meant to be. > And do you see any chance that I could argue the Telekom into not > having to pay this abhorrent sum? I have heard from similar cases, that it might be that the Telecom will have mercy. They never had mercy with me, anyway. I would not even think about telling them that you are running something unapproved like i4b on your side .... > (The remote site is an Ascend router > run *by the Telekom* for our University, so if it is an error on the > remote site, this could help a lot) IIRC the sppp loop bug was seen with Ascends. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 24 0:20:21 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id B3A0637BAED for ; Thu, 24 Feb 2000 00:20:18 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1351 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Thu, 24 Feb 2000 09:20:17 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id F06A23890; Thu, 24 Feb 2000 09:20:16 +0100 (MET) Subject: Re: i4b in -current source tree? In-Reply-To: <200002221900.UAA18594@gil.physik.rwth-aachen.de> from Christoph Kukulies at "Feb 22, 0 08:00:28 pm" To: kuku@gilberto.physik.RWTH-Aachen.DE (Christoph Kukulies) Date: Thu, 24 Feb 2000 09:20:16 +0100 (MET) Cc: freebsd-isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 445 Message-Id: <20000224082016.F06A23890@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Christoph Kukulies: > Where is i4b userland in the src tree, when I cvsup? /usr/src/usr.sbin/i4b hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 24 5:29:32 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from majestix.cmr.no (majestix.cmr.no [129.177.31.53]) by hub.freebsd.org (Postfix) with ESMTP id A922037BADD for ; Thu, 24 Feb 2000 05:29:27 -0800 (PST) (envelope-from tl@cmr.no) Received: from shark.cmr.no (shark.cmr.no [129.177.31.34]) by majestix.cmr.no (8.9.3/8.9.3) with ESMTP id OAA03603 for ; Thu, 24 Feb 2000 14:29:23 +0100 (CET) Date: Thu, 24 Feb 2000 14:29:23 +0100 (CET) From: Tom Lislegaard To: freebsd-isdn@freebsd.org Subject: Question about callback Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can isdnd be configured to accept callback from a different number than the one dialed ? To elaborate somewhat, the situation is like this. I'm dialling into a router with a given number, say 9999xxxx. The router immediately returns the call, but the PBX assigns a 'generic' CLID, 99990000 so isdnd can't see that this is the call it's waiting for. Is it possible to work around this in a simple way or do I have to rely on the person in charge of the PBX to reprogram the numbering scheme? -tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 24 8:10:20 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 0C8BB37BBC4 for ; Thu, 24 Feb 2000 08:10:13 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id RAA50041; Thu, 24 Feb 2000 17:03:07 +0100 (CET) Message-Id: <200002241603.RAA50041@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: Tom Lislegaard Cc: freebsd-isdn@FreeBSD.org Subject: Re: Question about callback Reply-To: Gary Jennejohn In-reply-to: Your message of "Thu, 24 Feb 2000 14:29:23 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Feb 2000 17:03:07 +0100 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tom Lislegaard writes: >Can isdnd be configured to accept callback from a different number >than the one dialed ? > >To elaborate somewhat, the situation is like this. >I'm dialling into a router with a given number, say 9999xxxx. >The router immediately returns the call, but the PBX assigns >a 'generic' CLID, 99990000 so isdnd can't see that this is the >call it's waiting for. > >Is it possible to work around this in a simple way or do I have >to rely on the person in charge of the PBX to reprogram the >numbering scheme? > I think you'll have to modify isdnd to handle this. Shouldn't be too difficult, just a few lines of code. --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 24 8:45:47 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id C020537BB61 for ; Thu, 24 Feb 2000 08:45:44 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1657 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Thu, 24 Feb 2000 17:45:03 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id D406738E2; Thu, 24 Feb 2000 17:45:01 +0100 (MET) Subject: Re: Question about callback In-Reply-To: from Tom Lislegaard at "Feb 24, 0 02:29:23 pm" To: tl@cmr.no (Tom Lislegaard) Date: Thu, 24 Feb 2000 17:45:01 +0100 (MET) Cc: freebsd-isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 809 Message-Id: <20000224164501.D406738E2@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Tom Lislegaard: > Can isdnd be configured to accept callback from a different number > than the one dialed ? > > To elaborate somewhat, the situation is like this. > I'm dialling into a router with a given number, say 9999xxxx. > The router immediately returns the call, but the PBX assigns > a 'generic' CLID, 99990000 so isdnd can't see that this is the > call it's waiting for. Hmm, try it. remote-phone-dialout = 9999xxxx remote-phone-incoming = 99990000 hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 24 9:42:28 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 57A4237BCCF for ; Thu, 24 Feb 2000 09:42:25 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id SAA50726; Thu, 24 Feb 2000 18:32:19 +0100 (CET) Message-Id: <200002241732.SAA50726@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: hm@hcs.de Cc: tl@cmr.no (Tom Lislegaard), freebsd-isdn@FreeBSD.org Subject: Re: Question about callback Reply-To: Gary Jennejohn In-reply-to: Your message of "Thu, 24 Feb 2000 17:45:01 +0100." <20000224164501.D406738E2@hcswork.hcs.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Feb 2000 18:32:19 +0100 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hellmuth Michaelis writes: >>From the keyboard of Tom Lislegaard: > >> Can isdnd be configured to accept callback from a different number >> than the one dialed ? >> >> To elaborate somewhat, the situation is like this. >> I'm dialling into a router with a given number, say 9999xxxx. >> The router immediately returns the call, but the PBX assigns >> a 'generic' CLID, 99990000 so isdnd can't see that this is the >> call it's waiting for. > >Hmm, try it. > >remote-phone-dialout = 9999xxxx >remote-phone-incoming = 99990000 > yeah, but what about the magic in isdnd which notices that it's a callback from the number just called and hangs up the outgoing call (sometimes too) quickly ? I suspect this is what Tom was addressing. --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 24 11: 8:15 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from ixori.demon.nl (ixori.demon.nl [195.11.248.5]) by hub.freebsd.org (Postfix) with ESMTP id 823C537BC3C for ; Thu, 24 Feb 2000 11:08:05 -0800 (PST) (envelope-from bart@ixori.demon.nl) Received: from smtp-relay by ixori.demon.nl (8.9.3/8.9.2) with ESMTP id UAA15530; Thu, 24 Feb 2000 20:06:02 +0100 (CET) (envelope-from bart@ixori.demon.nl) Received: from network (intranet) by smtp-relay (Bart's intranet smtp server) Message-ID: <38B59D3A.D95C89BB@ixori.demon.nl> Date: Thu, 24 Feb 2000 20:06:02 -0100 From: Bart van Leeuwen X-Mailer: Mozilla 4.61 [en] (X11; I; IRIX 6.2 IP22) X-Accept-Language: en MIME-Version: 1.0 To: hm@hcs.de Cc: tobi@physcip.uni-stuttgart.de, freebsd-isdn@freebsd.org Subject: Re: early hangup causing exorbitant telecom fees References: <20000224081641.7ABFD38E2@hcswork.hcs.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hellmuth Michaelis wrote: > > And do you see any chance that I could argue the Telekom into not > > having to pay this abhorrent sum? > > I have heard from similar cases, that it might be that the Telecom will > have mercy. They never had mercy with me, anyway. Heh.. nor with me.. tho in the end the money did buy me something... my telecom costs were high enough to make them regard me as a special customer... so it at least bought me much better service (if my isdn breaks down they will be here within 4 hours to get it fixed and such) , but if I had the choice... I could have had a lot more fun with the money ;P Bart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Feb 25 3:13:16 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.unlisys.net (mail.unlisys.net [195.21.255.252]) by hub.freebsd.org (Postfix) with SMTP id 7CFAE37BEF1 for ; Fri, 25 Feb 2000 03:13:14 -0800 (PST) (envelope-from mscu.snafu.de!root@unlisys.net) Received: by mail.unlisys.net (Smail3.2.0.96inx) id ; Fri, 25 Feb 2000 12:13:06 +0100 (MET) Received: (from root@localhost) by mscu.snafu.de (8.9.3/8.9.3) id VAA01813; Thu, 24 Feb 2000 21:06:18 +0100 (CET) (envelope-from root) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000224164501.D406738E2@hcswork.hcs.de> Date: Thu, 24 Feb 2000 21:06:18 +0100 (CET) Reply-To: Matthias Schuendehuette Organization: Private UUCP site running FreeBSD From: Matthias Schuendehuette To: (Hellmuth Michaelis) Subject: Re: Question about callback Cc: freebsd-isdn@FreeBSD.ORG, (Tom Lislegaard) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 24-Feb-00 Hellmuth Michaelis wrote: > > Hmm, try it. > > remote-phone-dialout = 9999xxxx > remote-phone-incoming = 99990000 > This is what works for me for a long time now. I never had any problems with this setup since i4b 0.7.... :-)) Tom calls an ERICSSON PBX, isn't it? Ciao/BSD - Matthias --- ********************************************************************* Matthias Schündehütte E-Mail: Matthias Schuendehuette Solmsstrasse 44 Phone: +49-30-69409824 D-10961 Berlin Data/Fax: +49-30-69409825 GERMANY Handy: +49-170-8162912 This message was sent by XF-Mail on FreeBSD 3.4-STABLE ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Feb 25 8:39:38 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from devil.intervisors.nl (office.intervisors.nl [194.109.13.117]) by hub.freebsd.org (Postfix) with ESMTP id 7F2B437C371 for ; Fri, 25 Feb 2000 08:39:28 -0800 (PST) (envelope-from luke@roberts.nl) Received: from roberts4 (roberts4.intranet.iv [192.168.0.8]) by devil.intervisors.nl (8.9.3/8.9.3) with ESMTP id RAA11240 for ; Fri, 25 Feb 2000 17:35:03 +0100 (CET) (envelope-from luke@roberts.nl) Message-Id: <4.2.2.20000225173229.00aabd60@pop.roberts.nl> X-Sender: luke@pop.roberts.nl X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Fri, 25 Feb 2000 17:35:21 +0100 To: freebsd-isdn@FreeBSD.ORG From: Luke Roberts Subject: small dialing in problem Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I sent this mail to the list last week but I don't think anybody noticed it. 8-( Every now and then when i4b 0.83 (using i4bisppp on Free BSD 3.2 with a Teles 16.3 ISA version 1.1 non PnP) tries to dial in to my provider it won't get to the "switched to state 3" part of dialing in. It seems to hang at "Outgoing call active (ctl 0, ch0, isp0)" and I see a few bytes going in and out and eventually the connection is broken "outgoing call disconnected (local)". Manually hanging up the channel and causing a redial smoetimes does the trick to get to the next call "switched to state 3". Does anybody know what's going wrong here? Would upgrading to version 0.90 help? Is this the LCP loop bug? Thanks and have a nice weekend, Luke To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Feb 25 15:41:59 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id C541C37BDBD for ; Fri, 25 Feb 2000 15:41:55 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id AAA20795; Sat, 26 Feb 2000 00:40:40 +0100 (CET) Message-Id: <200002252340.AAA20795@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: Luke Roberts Cc: freebsd-isdn@FreeBSD.org Subject: Re: small dialing in problem Reply-To: Gary Jennejohn In-reply-to: Your message of "Fri, 25 Feb 2000 17:35:21 +0100." <4.2.2.20000225173229.00aabd60@pop.roberts.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 26 Feb 2000 00:40:40 +0100 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Luke Roberts writes: >Every now and then when i4b 0.83 (using i4bisppp on Free BSD 3.2 with a >Teles 16.3 ISA version 1.1 non PnP) tries to dial in to my provider it >won't get to the "switched to state 3" part of dialing in. It seems to hang >at "Outgoing call active (ctl 0, ch0, isp0)" and I see a few bytes going in >and out and eventually the connection is broken "outgoing call disconnected >(local)". > >Manually hanging up the channel and causing a redial smoetimes does the >trick to get to the next call "switched to state 3". > >Does anybody know what's going wrong here? >Would upgrading to version 0.90 help? >Is this the LCP loop bug? > I remember your mail, but the information you provide is much too vague to give you an answer. Turn on debugging on the interface and look at the log produced when you connect. That's the only way to find out what's happening. Take a look at the FAQ, it should help somewhat. --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Feb 26 2:35:47 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from widukind.bi.teuto.net (widukind.bi.teuto.net [212.8.197.28]) by hub.freebsd.org (Postfix) with ESMTP id 48B5A37BBE5 for ; Sat, 26 Feb 2000 02:35:43 -0800 (PST) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (IDENT:root@rumolt.teuto.de [212.8.203.81]) by widukind.bi.teuto.net (8.9.3/8.9.3) with ESMTP id LAA19582; Sat, 26 Feb 2000 11:35:28 +0100 Received: (from martin@localhost) by rumolt.teuto.de (8.9.3/8.8.8) id LAA05308; Sat, 26 Feb 2000 11:27:23 +0100 (MET) From: Martin Husemann Message-Id: <200002261027.LAA05308@rumolt.teuto.de> Subject: I4B does not install on NetBSD-current any more To: freebsd-isdn@FreeBSD.ORG, hm@kts.org (Hellmuth Michaelis) Date: Sat, 26 Feb 2000 11:27:23 +0100 (MET) Organization: Crusaders Catering Services Inc. ;-) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM951560843-5298-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ELM951560843-5298-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Just in case someone is tracking NetBSD-current: a few days ago the sys/conf/files file changed, so the patch we are using to integrate I4B support there fails in NetBSD/install-netbsd.sh. Attached is a new version (but this version will not work for older -current's) Martin --ELM951560843-5298-0_ Content-Type: application/x-sh Content-Disposition: attachment; filename=install-netbsd.sh Content-Description: replaces $I4B/NetBSD/install-netbsd.sh Content-Transfer-Encoding: 7bit #!/bin/sh #--------------------------------------------------------------------------- # # i4b installation script # ----------------------- # # last edit-date: [Sun Jan 4 08:05:28 1998] # # -hm tired to do it again and again.... # -mh ported to NetBSD # #--------------------------------------------------------------------------- #--------------------------------------------------------------------------- # Carefully adjust the values below. Then run this script from the # i4b/NetBSD directory as root. Then you can build your i4b kernel. # If you will be using the Diehl driver, you must copy the file dnload.bin # from your Diehl driver disk to the directory $DST/dev/microcode/daic # and run "make" in that directory. # The directory where the i4b distribution lives SRC=`(cd ..; pwd)` # Where the copy of your /usr/src/sys source tree lives. This copy is # modified to support i4b. You probably should not use your native /usr/src/sys # here! This working copy must exist, before you run this script! DST=/usr/src/sys-i4b #--------------------------------------------------------------------------- # YOU SHOULD NOT NEED TO CHANGE ANYTHING BELOW... # # This works with the NetBSD 1.4 release. #--------------------------------------------------------------------------- ISDN=$DST/i4b if [ ! -d $ISDN ] then mkdir $ISDN fi ln -s $SRC/layer1 $ISDN/layer1 ln -s $SRC/layer2 $ISDN/layer2 ln -s $SRC/layer3 $ISDN/layer3 ln -s $SRC/layer4 $ISDN/layer4 ln -s $SRC/driver $ISDN/driver ln -s $SRC/sppp $ISDN/sppp ln -s $SRC/include $ISDN/include ln -s $SRC/NetBSD/files.i4b $ISDN ln -s $SRC/NetBSD/files.i4b.isa $ISDN ln -s $SRC/NetBSD/files.i4b.pci $ISDN ln -s $SRC/NetBSD/files.i4b.pcmcia $ISDN ( cd $ISDN && ln -s $SRC/machine/*.h . ) ( cd $DST/arch/amiga/dev && ln -s $SRC/layer1/isic_supio.c . ) ( cd $DST/dev/isa && ln -s $SRC/layer1/isa_isic.c . ) ( cd $DST/dev/isa && ln -s $SRC/diehl/isadaic.c . ) ( cd $DST/dev/ic && ln -s $SRC/diehl/daic*.[hc] . ) ( cd $DST/dev/isapnp && ln -s $SRC/layer1/isapnp_isic.c . ) ( cd $DST/dev/pcmcia && ln -s $SRC/layer1/pcmcia_isic.c . ) ( cd $DST/dev/pci && ln -s $SRC/layer1/pci_isic.c . ) ( cd $DST/dev/microcode && mkdir daic && cd daic && ln -s $SRC/diehl/microcode/* . && make ) # ---------------------------------------------------------------------------- # Machine independed config file changes... # ---------------------------------------------------------------------------- cd $DST/conf || exit 1 patch << 'END_OF_PATCH' *** files.orig Fri Feb 25 13:52:07 2000 --- files Sat Feb 26 11:21:56 2000 *************** *** 747,757 **** file net/radix.c file net/raw_cb.c file net/raw_usrreq.c file net/route.c file net/rtsock.c ! file net/slcompress.c sl | ppp | strip file net/zlib.c (ppp & ppp_deflate) | ipsec file netatalk/aarp.c netatalk file netatalk/at_control.c netatalk file netatalk/at_proto.c netatalk file netatalk/at_rmx.c netatalkdebug --- 747,757 ---- file net/radix.c file net/raw_cb.c file net/raw_usrreq.c file net/route.c file net/rtsock.c ! file net/slcompress.c sl | ppp | strip | i4bipr file net/zlib.c (ppp & ppp_deflate) | ipsec file netatalk/aarp.c netatalk file netatalk/at_control.c netatalk file netatalk/at_proto.c netatalk file netatalk/at_rmx.c netatalkdebug END_OF_PATCH # ---------------------------------------------------------------------------- # Machine (architecture) specific patches follow... # ---------------------------------------------------------------------------- ARCH=`machine` if [ -f $SRC/NetBSD/sys-patch.$ARCH ] then . $SRC/NetBSD/sys-patch.$ARCH else echo "Unfortunately for your architecture no sys/config patch support" echo "has been added to i4b. It is easy to do, have a look at the" echo "existing stuff, create one for $ARCH and mail it to" echo "Martin Husemann (martin@rumolt.teuto.de)" fi --ELM951560843-5298-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Feb 26 2:36: 5 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from widukind.bi.teuto.net (widukind.bi.teuto.net [212.8.197.28]) by hub.freebsd.org (Postfix) with ESMTP id 0E77A37BCDA for ; Sat, 26 Feb 2000 02:36:03 -0800 (PST) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (IDENT:root@rumolt.teuto.de [212.8.203.81]) by widukind.bi.teuto.net (8.9.3/8.9.3) with ESMTP id LAA19586; Sat, 26 Feb 2000 11:35:30 +0100 Received: from martins (hwart.teuto.de [212.8.203.83]) by rumolt.teuto.de (8.9.3/8.8.8) with SMTP id LAA03497; Sat, 26 Feb 2000 11:12:59 +0100 (MET) From: "Martin Husemann" To: "Gary Jennejohn" , "Luke Roberts" Cc: Subject: RE: small dialing in problem Date: Sat, 26 Feb 2000 11:12:59 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-Reply-To: <200002252340.AAA20795@peedub.muc.de> Importance: Normal Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Turn on debugging on the interface and look at the log produced > when you connect. That's the only way to find out what's happening. I'm seeing this with an old version too, sometimes. Since that machine is (a) remote and (b) not using the latest and greates source, I simply reboot it when this happens and try to remember to debug it in detail if it still happens when I will have brought that one up to a modern version ;-) As far as I can tell either the effect never happens when debug is set on the interface or the debug output shows nothing special. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Feb 26 4:39: 5 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 7E66837B7A1 for ; Sat, 26 Feb 2000 04:39:03 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1220 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Sat, 26 Feb 2000 13:39:02 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id E193B36AB; Sat, 26 Feb 2000 13:39:01 +0100 (MET) Subject: T-ISDN@ctive / AODI To: freebsd-isdn@freebsd.org (ISDN Mailinglist) Date: Sat, 26 Feb 2000 13:39:01 +0100 (MET) Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 522 Message-Id: <20000226123901.E193B36AB@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, under http://www.telekom.de/dtag/ipl2/cda/t2/0,4260,10286,00.html the intial offering for AODI is available (in german only). AFAIK, this service will only be available to T-Online customers. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Feb 26 5:48:39 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from passat.ndh.net (passat.ndh.net [195.94.90.26]) by hub.freebsd.org (Postfix) with ESMTP id 8385137BC92 for ; Sat, 26 Feb 2000 05:48:36 -0800 (PST) (envelope-from hg@glaess.ndh.com) Received: (from uucp@localhost) by passat.ndh.net (8.9.3/8.9.3) with UUCP id OAA00670 for isdn@freebsd.org; Sat, 26 Feb 2000 14:48:26 +0100 (MET) From: hg@glaess.ndh.com Received: (qmail 4540 invoked from network); 26 Feb 2000 19:45:46 -0000 Received: from server.hgs.de (192.168.1.25) by server.hgs.de with SMTP; 26 Feb 2000 19:45:46 -0000 Message-ID: X-Mailer: XFMail 1.4.4 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 26 Feb 2000 14:45:46 -0500 (EST) Reply-To: hg@glaess.ndh.com Organization: glaess.ndh.com To: isdn@freebsd.org Subject: singnature wrong ? Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi all, i have here an old teles 16.3 card (with a/b adaptor on it) and i will run this card with i4b (under linux rus the card well). but i get an error message at the start of the system. isic0: error, signature 3 0x1f != 0x1c for teles 16.3 isic0: not found at 0xd80 what´ s happend the same card runs under a linux kernel 2.0.36 very well... --- E-Mail: hg@glaess.ndh.com Time:14:40:59 Date: 26-Feb-2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Feb 26 8: 7:35 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 231F537B553 for ; Sat, 26 Feb 2000 08:07:32 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1630 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Sat, 26 Feb 2000 17:07:30 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 05EEA3890; Sat, 26 Feb 2000 17:07:29 +0100 (MET) Subject: Re: singnature wrong ? In-Reply-To: from "hg@glaess.ndh.com" at "Feb 26, 0 02:45:46 pm" To: hg@glaess.ndh.com Date: Sat, 26 Feb 2000 17:07:29 +0100 (MET) Cc: isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 814 Message-Id: <20000226160729.05EEA3890@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of hg@glaess.ndh.com: > i have here an old teles 16.3 card (with a/b adaptor on it) and i will run this > card with i4b (under linux rus the card well). > > but i get an error message at the start of the system. > > isic0: error, signature 3 0x1f != 0x1c for teles 16.3 > isic0: not found at 0xd80 There is a line in the Teles 16.3 driver where a test for 0x1c is done, just change this line to something like: if((b2 != 0x1c) && (b2 != 0x1f)) and it should work. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Feb 26 8:32:50 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9]) by hub.freebsd.org (Postfix) with ESMTP id 1B01037BD12 for ; Sat, 26 Feb 2000 08:32:47 -0800 (PST) (envelope-from gaspode.franken.de!tanis@maulwurf.franken.de) Received: by maulwurf.franken.de via rmail with stdio id for freebsd-isdn@freebsd.org; Sat, 26 Feb 2000 17:32:46 +0100 (MET) (Smail-3.2 1996-Jul-4 #1 built DST-May-30) Received: (from tanis@localhost) by gaspode.franken.de (8.9.3/8.9.3) id RAA15927; Sat, 26 Feb 2000 17:32:13 +0100 (CET) (envelope-from tanis) Date: Sat, 26 Feb 2000 17:32:13 +0100 From: German Tischler To: hg@glaess.ndh.com Cc: freebsd-isdn@freebsd.org Subject: Re: singnature wrong ? Message-ID: <20000226173213.A14912@gaspode.franken.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from hg@glaess.ndh.com on Sat, Feb 26, 2000 at 02:54:31PM +0100 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Feb 26, 2000 at 02:54:31PM +0100, hg@glaess.ndh.com wrote: > hi all, > > i have here an old teles 16.3 card (with a/b adaptor on it) and i will run this > card with i4b (under linux rus the card well). > > but i get an error message at the start of the system. > > isic0: error, signature 3 0x1f != 0x1c for teles 16.3 > isic0: not found at 0xd80 > > what? s happend the same card runs under a linux kernel 2.0.36 very well... Is it a 16.3c ? (i4b doesn't support these.) -- German Tischler, tanis@gaspode.franken.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Feb 26 9: 1:30 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from morannon.fido.de (morannon.faho.RWTH-Aachen.DE [134.130.57.8]) by hub.freebsd.org (Postfix) with ESMTP id 2FDAE37BD81 for ; Sat, 26 Feb 2000 09:01:24 -0800 (PST) (envelope-from tobi@bland.fido.de) Received: from gate.fido.de (news@localhost) by morannon.fido.de (8.9.3/8.9.3/redhat6-morannon-4.4) with FIDOGATE id SAA21300; Sat, 26 Feb 2000 18:01:03 +0100 Received: by sungate-ftn.fido.de (FIDOGATE 4.3.6) id AA21298; Sat, 26 Feb 2000 18:01:03 +0100 Date: Sat, 26 Feb 2000 13:29:42 +0100 From: tobi@bland.fido.de (Tobias Ernst) Reply-To: tobi@physcip.uni-stuttgart.de (Tobias Ernst) Subject: Re: early hangup causing exorbitant telecom fees Message-ID: To: freebsd-isdn@FreeBSD.ORG Organization: Fido.DE domain gateway (Moving Bits e.V. / IN e.V.) Lines: 53 X-Gateway: FIDO morannon.fido.de [FIDOGATE 4.3.6] X-FTN-From: Tobias Ernst @ 242:7600/1.0 X-FTN-To: UUCP @ 242:4900/99.0 X-FTN-Via: 242:7600/0@fido.de @20000226.173204 CFR-OS/2 20000121-devel X-FTN-Via: FIDOGATE/ftntoss 242:1000/1.0, Sat Feb 26 2000 at 18:01:02 CET X-FTN-Domain: Z242@fidode MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Original to: hm@hcs.de (Hellmuth Michaelis) * Carbon Copies: freebsd-isdn@FreeBSD.ORG Hallo Hellmuth! HM> I guess you are using some sort of PPP. HM> I guess that your machine tried to reach the remote machine Yes, yes. HM> and somehow the login/authorization failed. HM> The PPP layer then tried to reach the remote end again and again. Unfortunately, this does not show up in any of the logs. I am using kernel PPP. HM> From what i see it is not a bug in the i4b ISDN code. In case you are HM> using sppp, you might have been hit by the lcp-loop bug. Do I understand this right that if I switch to user ppp I would not have to fear to be hit by the lcp loop bug again, assuming that it was the lcp loop bug that caused the problem? I just tried it with user ppp and it works. I also like user ppp better, I was just using sppp because when I started with i4b, using user ppp was not yet an option. >> And do you see any chance that I could argue the Telekom into not >> having to pay this abhorrent sum? HM> I have heard from similar cases, that it might be that the Telecom HM> will have mercy. They never had mercy with me, anyway. HM> I would not even think about telling them that you are running HM> something unapproved like i4b on your side .... Of course. Do you think it is safe to tell them I am using FreeBSD in combination with an external (BZT approoved) TA? I have enough of them floating around and also configuration files for it, so I could easily switch to this solution for the time until the matter is settled. Or should I set up a Windows solution ? HM> IIRC the sppp loop bug was seen with Ascends. Does this indicate that the problem was essentially a bug in my FreeBSD code, but that this was triggered by some sort of misbehaviour in the Ascend? Viele Gr=FC=DFe, Tobias To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Feb 26 11: 3:32 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (Postfix) with ESMTP id E935137B56F for ; Sat, 26 Feb 2000 11:03:24 -0800 (PST) (envelope-from hm@kts.org) Received: from mailstore.ppp.net (pop3.ppp.net [212.18.80.90]) by mail.ppp.net (8.8.8/8.8.8) with ESMTP id UAA09385; Sat, 26 Feb 2000 20:03:19 +0100 Received: (from uucp@localhost) by mailstore.ppp.net (8.9.3/8.9.3/Debian/GNU) with UUCP id TAA22963; Sat, 26 Feb 2000 19:57:03 +0100 Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 7422F52C23; Sat, 26 Feb 2000 19:56:58 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id 2A9071F17; Sat, 26 Feb 2000 19:56:55 +0100 (CET) Subject: Re: early hangup causing exorbitant telecom fees In-Reply-To: from Tobias Ernst at "Feb 26, 2000 1:29:42 pm" To: tobi@physcip.uni-stuttgart.de Date: Sat, 26 Feb 2000 19:56:55 +0100 (CET) Cc: freebsd-isdn@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000226185655.2A9071F17@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tobias Ernst wrote: > HM> From what i see it is not a bug in the i4b ISDN code. In case you > are > HM> using sppp, you might have been hit by the lcp-loop bug. > > Do I understand this right that if I switch to user ppp I would not > have to fear to be hit by the lcp loop bug again, assuming that it was > the lcp loop bug that caused the problem? It seems that userland ppp is more robust and has more features available than sppp. It is unlikely that you will be hit by this bug again with userland ppp but this will not save you from other bugs in your or the remote end implementation of ppp. There were some proposals in the past to introduce a keyword for the entry section in isdnd.rc which should limit the maximum number of dials per time unit: this would be IMHO the best way to protect for such desasters. > HM> IIRC the sppp loop bug was seen with Ascends. > > Does this indicate that the problem was essentially a bug in my FreeBSD > code, but that this was triggered by some sort of misbehaviour in the > Ascend? I am only guessing here, but it seems that the problem is a bug in some versions of sppp which is triggered by some sort of behaviour in some versions of an Ascend. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message