From owner-freebsd-isdn Sun Jun 27 1:38: 5 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (Postfix) with ESMTP id 10D661518E for ; Sun, 27 Jun 1999 01:37:59 -0700 (PDT) (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 KAA46646; Sun, 27 Jun 1999 10:35:13 +0200 (CEST) Message-Id: <199906270835.KAA46646@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: Andras Wappel Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: hisaddr problem Reply-To: Gary Jennejohn In-reply-to: Your message of "Sat, 26 Jun 1999 18:28:50 +0300." <3774F1B2.446B9B3D@kolumbus.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Jun 1999 10:35:13 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andras Wappel writes: >Hello ISDN people, > >Jun 26 17:02:41 icebreaker /kernel: isp0: ipcp parse opt values: address >193.229.42.1 [not agreed] send conf-nak >^^^^^^^^^^^^^ >My spppcontrol lines from /etc/rc.isdn: >ifconfig isp0 link1 0.0.0.0 193.229.10.1 netmask 0xffffff00 >debug >ifconfig isp0 >down > >spppcontrol isp0 authproto=pap myauthname='mylogin' >myauthsecret='mypass' callin hisauthproto=none > >So what should I change so I can accept any gateway address, not just >193.229.10.1 ? Or is the problem something else ? > use 0.0.0.1, as explained in the sppp man page. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Jun 27 4:33:40 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from smtp.kolumbus.fi (smtp.kolumbus.fi [193.229.0.51]) by hub.freebsd.org (Postfix) with ESMTP id 7BC1B14DA8 for ; Sun, 27 Jun 1999 04:33:34 -0700 (PDT) (envelope-from andras@kolumbus.fi) Received: from icebreaker.kolumbus.fi (kf111u2hel.dial.kolumbus.fi [193.229.45.111]) by smtp.kolumbus.fi (8.9.0/8.9.0) with ESMTP id OAA21591; Sun, 27 Jun 1999 14:34:18 +0300 (EET DST) Received: from andras by icebreaker.kolumbus.fi with local (Exim 2.12 #1 (Debian)) id 10yDHf-0002jl-00; Sun, 27 Jun 1999 14:39:39 +0300 Date: Sun, 27 Jun 1999 14:39:39 +0300 From: Andras Wappel To: Gary Jennejohn Cc: freebsd-isdn@freebsd.org Subject: Re: hisaddr problem Message-ID: <19990627143939.A10492@icebreaker> References: <3774F1B2.446B9B3D@kolumbus.fi> <199906270835.KAA46646@peedub.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199906270835.KAA46646@peedub.muc.de>; from Gary Jennejohn on Sun, Jun 27, 1999 at 10:35:13AM +0200 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Jun 27, 1999 at 10:35:13AM +0200, Gary Jennejohn wrote: > > use 0.0.0.1, as explained in the sppp man page. > Thanks, so it was a simple rtfm. I was looking at the wrong docs apparently. I have two other questions though: 1. Is there an archive of this list on the web ? 2. When the link goes down (ifconfig isp0 down), sometimes I see messages on the console ( only emergency messages are configured to go to the console ) like this: i4b-L1-isic_isac_irq: unit 0: CRC error i4b-L1-isic_isac_irq: unit 0: Receive Aborted error i4b-L1-timer4_expired: state = F3 Deactivated I can connect again after this message is output. So is this a harmless message, or something is wrong with my card/driver/setup ? ( my card is Teles S0/16.3 rev 1.1, default io,irq setting) ( FreeBSD 3.1-STABLE, builtin i4b driver ) options "TEL_S0_16_3" device isic0 at isa? port 0xd80 net irq 5 flags 3 pseudo-device "i4bq921" pseudo-device "i4bq931" pseudo-device "i4b" pseudo-device "i4btrc" 4 pseudo-device "i4bctl" pseudo-device "i4brbch" 4 pseudo-device "i4btel" 2 pseudo-device "i4bipr" 4 options IPR_VJ pseudo-device "i4bisppp" 4 pseudo-device "sppp" 4 Thanks, Andras To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Jun 27 6:16: 1 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (Postfix) with ESMTP id 7276D1529F for ; Sun, 27 Jun 1999 06:15:57 -0700 (PDT) (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 PAA00650; Sun, 27 Jun 1999 15:05:18 +0200 (CEST) Message-Id: <199906271305.PAA00650@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: Andras Wappel Cc: freebsd-isdn@freebsd.org Subject: Re: hisaddr problem Reply-To: Gary Jennejohn In-reply-to: Your message of "Sun, 27 Jun 1999 13:39:39 +0200." <19990627143939.A10492@icebreaker> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Jun 1999 15:05:18 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andras Wappel writes: >1. Is there an archive of this list on the web ? > yes, see www.freedsd.org. If you look under the search item it will lead to a page with all the mailing lists. You can search the lists. >2. When the link goes down (ifconfig isp0 down), sometimes > I see messages on the console ( only emergency messages > are configured to go to the console ) like this: > > i4b-L1-isic_isac_irq: unit 0: CRC error > i4b-L1-isic_isac_irq: unit 0: Receive Aborted error > i4b-L1-timer4_expired: state = F3 Deactivated > > I can connect again after this message is output. > So is this a harmless message, or something is wrong with my card/driver/s >etup ? > I suspect that this is a result of your downing the interface. Evidently there was still traffic on the link, which you basically forcefully put an end to. It's just an informational message and obviously is not an indication of an error. Somehow I get the impression that a lot of users do not trust the automatic short hold mechanism (/etc/isdn/isdnd.rates). Believe me, it works just fine and there's no need to manually shut down. I run 7/24 with i4b always active and the Telekom is not making a fortune off of me ;-) Of course, in Finnland it may be a different story. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Jun 27 11: 3:57 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from pollux.use.ch (pollux.use.ch [212.28.139.25]) by hub.freebsd.org (Postfix) with ESMTP id EB13D1506C for ; Sun, 27 Jun 1999 11:03:46 -0700 (PDT) (envelope-from schlegel@use.ch) Received: from castor (uucp@localhost) by pollux.use.ch (8.9.1/8.9.1) with bsmtp id TAA16799 for freebsd-isdn@freebsd.org; Sun, 27 Jun 1999 19:51:38 +0200 Received: (from root@localhost) by castor.use.ch (8.9.2/8.9.2) id RAA01856 for freebsd-isdn@freebsd.org; Sun, 27 Jun 1999 17:14:27 +0200 (CEST) (envelope-from schlegel) From: Caspar Schlegel Message-Id: <199906271514.RAA01856@castor.use.ch> Subject: CRC-Errors (was: Re: hisaddr problem) In-Reply-To: <199906271305.PAA00650@peedub.muc.de> from Gary Jennejohn at "Jun 27, 1999 3: 5:18 pm" To: freebsd-isdn@freebsd.org Date: Sun, 27 Jun 1999 17:14:27 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL43 (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 [CRC-Errors after downing the link:] Gary writes: > I suspect that this is a result of your downing the interface. Evidently > there was still traffic on the link, which you basically forcefully put > an end to. It's just an informational message and obviously is not an > indication of an error. Here in Switzerland I had these messages when the exchange switched layer 1 off. (Power-Saving reasons). As soon as I requested Swisscom not to switch it off these messages disappeared... Caspar. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Jun 27 12:57:50 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from munich.netsurf.de (laurin.munich.netsurf.de [194.64.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2D75214DAA for ; Sun, 27 Jun 1999 12:57:46 -0700 (PDT) (envelope-from Klaus.Herrmann@gmx.net) Received: from wunderland (ns1153.munich.netsurf.de [195.180.235.153]) by munich.netsurf.de (8.8.5/8.7) with SMTP id VAA03329; Sun, 27 Jun 1999 21:57:44 +0200 (MET DST) From: Klaus Herrmann To: Gary Jennejohn Subject: Re: hisaddr problem Date: Sun, 27 Jun 1999 17:23:16 +0200 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain Cc: freebsd-isdn@freebsd.org References: <199906271305.PAA00650@peedub.muc.de> MIME-Version: 1.0 Message-Id: <99062717263700.00320@wunderland> Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Somehow I get the impression that a lot of users do not trust the autom= atic > short hold mechanism (/etc/isdn/isdnd.rates). Believe me, it works just > fine and there's no need to manually shut down. I run 7/24 with i4b alw= ays > active and the Telekom is not making a fortune off of me ;-) this is rather a problem of trusting other programs than trusting this mechanism. for example netscape tries to connect my proxy-server every startup (even when i read local files), and there are some more progs out there which start useless connections. it saves some money to do manual connecting to avoid useless connections. =09--klaus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Jun 28 7:41:28 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from fep09-svc.tin.it (mta09-acc.tin.it [212.216.176.40]) by hub.freebsd.org (Postfix) with ESMTP id 961D41518F for ; Mon, 28 Jun 1999 07:41:15 -0700 (PDT) (envelope-from giorgio.bozio@ag2000.it) Received: from giorgio ([212.216.41.193]) by fep09-svc.tin.it (InterMail v4.0 201-221-105) with SMTP id <19990628144111.LUAI29796.fep09-svc@giorgio>; Mon, 28 Jun 1999 16:41:11 +0200 From: giorgio.bozio@ag2000.it To: Klaus Herrmann Date: Mon, 28 Jun 1999 16:35:38 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: hisaddr problem Cc: freebsd-isdn@freebsd.org In-reply-to: <99062717263700.00320@wunderland> X-mailer: Pegasus Mail for Win32 (v3.01d) Message-Id: <19990628144111.LUAI29796.fep09-svc@giorgio> Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org first of all thank you Klaus for the support to get isdn to work. Now it works! but it works even too much. i reported the same errors others have written about on the list but I noted that if I isolate the freebsd pc from the other win pc on the lan the errors and the opening of useless connections cease. I suspect that some broadcast messages get to the isp0 interface and from that to the gateway on the other side of the connection since I putted up nat and ipfw to allow internet sharing on the lan. Could it be this to spark the few bytes connections? if yes how can I avoid ipfw to divert this packets? thank you Ciao, Giorgio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Jun 28 11:34:22 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from bamf.demon.co.uk (bamf.demon.co.uk [158.152.173.140]) by hub.freebsd.org (Postfix) with SMTP id C54DA15240 for ; Mon, 28 Jun 1999 11:34:12 -0700 (PDT) (envelope-from rich@dynamite.org) Received: from clyde (unverified [192.168.1.2]) by clyde.chugaboom.net (EMWAC SMTPRS 0.83) with SMTP id ; Mon, 28 Jun 1999 19:34:04 +0100 Message-ID: From: "Rich Wood" Organization: dynamite.org To: freebsd-isdn@freebsd.org Date: Mon, 28 Jun 1999 19:34:04 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Teles S0/8 problem Reply-To: rich@dynamite.org X-mailer: Pegasus Mail for Win32 (v3.11) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've just installed a Teles S0/8 card (thanks to Hellmuth) into one of my FreeBSD boxes. However, when booting with the new kernel it is failing as follows.... isic0 at irq1 maddr 0xd000 msized 4096 flags 0x1 on isa Fatal trap12: page fault while in kernel mode fault virtual address = 0x20 fault code = supervisor read, page not present instruction pointer = 0x8:0x20 stack pointer = 0x10:0xc02e4ed4 frame pointer = 0x10:0xc02e4ef0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 () interrupt mask = net tty bio cam trap number = 12 panic: page fault The machine is running FreeBSD 3.2-RELEASE upgraded with i4b 0.81 beta using FreeBSD/overinstall.sh The Kernel config file has had the following added to it.... #ISDN bit options "TEL_S0_8" device isic0 at isa? iomem 0xd0000 net irq 5 flags 1 vector isicintr pseudo-device "i4bq921" pseudo-device "i4bq931" pseudo-device "i4b" pseudo-device "i4btrc" 4 pseudo-device "i4bctl" pseudo-device "i4brbch" 4 pseudo-device "i4btel" 2 pseudo-device "i4bipr" 4 options IPR_VJ pseudo-device "i4bisppp" 4 pseudo-device "sppp" Any suggestions as to what is going wrong? Rich -- rich@dynamite.org If that's what they call normal, I'd rather be insane. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Jun 28 15:32:11 1999 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 5F24F14CE3 for ; Mon, 28 Jun 1999 15:32:06 -0700 (PDT) (envelope-from ernie!bert.kts.org!hm@ppp.net) Received: from casparc.ppp.net (casparc2.ppp.net [194.64.12.42]) by mail.ppp.net (8.8.8/8.8.8) with SMTP id AAA15570; Tue, 29 Jun 1999 00:32:05 +0200 Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m10yjwb-002ZjjC; Tue, 29 Jun 99 00:32 MET DST Received: from bert.kts.org([194.55.156.2]) (1718 bytes) by ernie.kts.org via sendmail with P:smtp/R:smart_host/T:uux (sender: ) id for ; Mon, 28 Jun 1999 21:57:36 +0200 (CEST) (Smail-3.2.0.103 1998-Oct-9 #5 built 1999-Apr-19) Received: from localhost (1268 bytes) by bert.kts.org via sendmail with P:stdio/R:smart_host/T:smtp (sender: ) (ident using unix) id for ; Mon, 28 Jun 1999 22:00:09 +0200 (CEST) (Smail-3.2.0.103 1998-Oct-9 #4 built 1998-Dec-26) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: Teles S0/8 problem In-Reply-To: from Rich Wood at "Jun 28, 1999 7:34: 4 pm" To: rich@dynamite.org Date: Mon, 28 Jun 1999 22:00:09 +0200 (CEST) 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 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Rich Wood wrote: > I've just installed a Teles S0/8 card (thanks to Hellmuth) into one of my > FreeBSD boxes. However, when booting with the new kernel it is failing as > follows.... > > isic0 at irq1 maddr 0xd000 msized 4096 flags 0x1 on isa ^^^^ > options "TEL_S0_8" > device isic0 at isa? iomem 0xd0000 net irq 5 flags 1 vector isicintr ^^^^^ These two don't fit together. I don't know if this is a bug, i'll have a look at another machine running 3.2 stable where i have such a card running. 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 Tue Jun 29 0:44:30 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from post.ruh-bath.swest.nhs.uk (hide14.nhs.uk [194.6.81.14]) by hub.freebsd.org (Postfix) with ESMTP id CF23214E96 for ; Tue, 29 Jun 1999 00:44:22 -0700 (PDT) (envelope-from rich@ruh-bath.swest.nhs.uk) Received: by post.ruh-bath.swest.nhs.uk with Internet Mail Service (5.5.2448.0) id ; Tue, 29 Jun 1999 08:45:47 +0100 Message-ID: <930BFA16390CD3119E010000F6E660C9A4B3@fear.ruh-bath.swest.nhs.uk> From: "Wood, Richard" To: "'hm@kts.org'" Cc: "'freebsd-isdn@freebsd.org'" Subject: RE: Teles S0/8 problem Date: Tue, 29 Jun 1999 08:45:46 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -----Original Message----- > From: hm@kts.org [mailto:hm@kts.org] > Subject: Re: Teles S0/8 problem > These two don't fit together. I don't know if this is a bug, > i'll have a > look at another machine running 3.2 stable where i have such > a card running. Probably a typo when I transcribed the error message :-( However, I moved the card into an older machine, and it was detected fine with no panics. Rich -- Rich Wood Home: rich@dynamite.org Work: rich@ruh-bath.swest.nhs.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Jun 29 10:14:44 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from tomservo.ee.calpoly.edu (tomservo.ee.calpoly.edu [129.65.26.123]) by hub.freebsd.org (Postfix) with ESMTP id 580F614BEF for ; Tue, 29 Jun 1999 10:14:41 -0700 (PDT) (envelope-from kwayman@tomservo.ee.calpoly.edu) Received: (from kwayman@localhost) by tomservo.ee.calpoly.edu (8.9.3/8.9.3) id KAA42849 for freebsd-isdn@FreeBSD.ORG; Tue, 29 Jun 1999 10:13:43 -0700 (PDT) (envelope-from kwayman) From: Kyle Wayman Message-Id: <199906291713.KAA42849@tomservo.ee.calpoly.edu> Subject: Motorolla Bitsurfer To: freebsd-isdn@FreeBSD.ORG Date: Tue, 29 Jun 1999 10:13:43 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL43 (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 I have checked the FreeBSD FAQ and it says that the bitsurfer will definitely work, but are there any step-by-step instructions for people who are new to ISDN and are having trouble getting the card (yes, it's internal) to work. (like me) :) -Kyle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Jul 1 10:47:21 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from smtp.kolumbus.fi (smtp.kolumbus.fi [193.229.0.51]) by hub.freebsd.org (Postfix) with ESMTP id 66EC214CBE for ; Thu, 1 Jul 1999 10:47:05 -0700 (PDT) (envelope-from andras@kolumbus.fi) Received: from icebreaker (mail@kc176u2hel.dial.kolumbus.fi [193.229.42.176]) by smtp.kolumbus.fi (8.9.0/8.9.0) with ESMTP id UAA15397 for ; Thu, 1 Jul 1999 20:47:48 +0300 (EET DST) Received: from andras by icebreaker with local (Exim 2.05 #1 (Debian)) id 10zl8T-0000MF-00; Thu, 1 Jul 1999 21:00:33 +0300 Date: Thu, 1 Jul 1999 21:00:33 +0300 From: Andras Wappel To: freebsd-isdn@freebsd.org Subject: can't connect, "danger will robinson" ? Message-ID: <19990701210033.A305@kolumbus.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, The dynamic gateway ip now works ok, but meanwhile I got another problem. I can't connect in freebsd, only in w*n and linux. It happens about every second day, maybe it's connected with one specific gateway at my isp ? ... Jul 1 20:18:03 icebreaker /kernel: isic0 at 0xd80 irq 5 flags 0x3 on isa Jul 1 20:18:03 icebreaker /kernel: isic0: Teles S0/16.3 Jul 1 20:18:03 icebreaker /kernel: isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x960) Jul 1 20:18:03 icebreaker /kernel: isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x160, AddrB=0x560) ... Jul 1 20:18:03 icebreaker /kernel: i4btrc: 4 ISDN trace device(s) attached Jul 1 20:18:03 icebreaker /kernel: i4brbch: 4 raw B channel access device(s) attached Jul 1 20:18:03 icebreaker /kernel: i4btel: 2 ISDN telephony interface device(s) attached Jul 1 20:18:03 icebreaker /kernel: i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) Jul 1 20:18:03 icebreaker /kernel: i4bctl: ISDN system control port attached Jul 1 20:18:03 icebreaker /kernel: i4bispp Jul 1 20:18:03 icebreaker /kernel: p: 4 ISDN SyncPPP device(s) attached Jul 1 20:18:03 icebreaker /kernel: i4b: ISDN call control device attached Jul 1 20:18:03 icebreaker /kernel: changing root device to wd0s2a Jul 1 20:18:03 icebreaker /kernel: isp0: lcp close(initial) Jul 1 20:18:03 icebreaker /kernel: isp0: lcp close(initial) Jul 1 20:18:45 icebreaker login: ROOT LOGIN (root) ON ttyv0 Jul 1 20:21:25 icebreaker /kernel: isp0: lcp open(initial) Jul 1 20:21:25 icebreaker /kernel: isp0: phase establish Jul 1 20:21:26 icebreaker /kernel: i4b: unit 0, assigned TEI = 69 = 0x45 Jul 1 20:21:26 icebreaker /kernel: isp0: Up event Jul 1 20:21:26 icebreaker /kernel: isp0: lcp up(starting) Jul 1 20:21:26 icebreaker /kernel: isp0: lcp output Jul 1 20:21:26 icebreaker /kernel: isp0: lcp input(req-sent): Jul 1 20:21:26 icebreaker /kernel: isp0: lcp parse opts: auth-proto magic 0x11 [rej] 0x13 [rej] send conf-rej Jul 1 20:21:26 icebreaker /kernel: isp0: lcp output Jul 1 20:21:26 icebreaker /kernel: isp0: lcp input(req-sent): Jul 1 20:21:26 icebreaker /kernel: isp0: lcp input(ack-rcvd): Jul 1 20:21:26 icebreaker /kernel: isp0: lcp parse opts: auth-proto magic Jul 1 20:21:26 icebreaker /kernel: isp0: lcp parse opt values: auth-proto magic 0xe2445218 send conf-ack Jul 1 20:21:26 icebreaker /kernel: isp0: lcp output Jul 1 20:21:26 icebreaker /kernel: isp0: lcp tlu Jul 1 20:21:26 icebreaker /kernel: isp0: phase authenticate Jul 1 20:21:26 icebreaker /kernel: isp0: pap output Jul 1 20:21:27 icebreaker /kernel: isp0: pap success Jul 1 20:21:27 icebreaker /kernel: isp0: phase network Jul 1 20:21:27 icebreaker /kernel: isp0: ipcp open(initial) Jul 1 20:21:27 icebreaker /kernel: isp0: ipcp up(starting) Jul 1 20:21:27 icebreaker /kernel: isp0: ipcp output Jul 1 20:21:27 icebreaker /kernel: isp0: ipcp input(req-sent): Jul 1 20:21:27 icebreaker /kernel: isp0: ipcp parse opts: address Jul 1 20:21:27 icebreaker /kernel: isp0: ipcp parse opt values: address 0.0.0.1 [ack] send conf-ack Jul 1 20:21:27 icebreaker /kernel: isp0: ipcp output Jul 1 20:21:28 icebreaker /kernel: isp0: ipcp TO(ack-sent) rst_counter = 10 Jul 1 20:21:28 icebreaker /kernel: isp0: ipcp output Jul 1 20:21:28 icebreaker /kernel: isp0: lcp input(opened): Jul 1 20:21:28 icebreaker /kernel: isp0: lcp: ignoring RXJ (proto-rej) for proto 0x8021, danger will robinson ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Jul 1 20:21:29 icebreaker /kernel: isp0: ipcp TO(ack-sent) rst_counter = 9 Jul 1 20:21:29 icebreaker /kernel: isp0: ipcp output Jul 1 20:21:30 icebreaker /kernel: isp0: ipcp TO(ack-sent) rst_counter = 8 Jul 1 20:21:30 icebreaker /kernel: isp0: ipcp output Jul 1 20:21:30 icebreaker /kernel: isp0: lcp input(opened): Jul 1 20:21:30 icebreaker /kernel: isp0: got lcp echo req, sending echo rep Jul 1 20:21:30 icebreaker /kernel: isp0: lcp output Jul 1 20:21:31 icebreaker /kernel: isp0: ipcp TO(ack-sent) rst_counter = 7 Jul 1 20:21:31 icebreaker /kernel: isp0: ipcp output Jul 1 20:21:32 icebreaker /kernel: isp0: ipcp TO(ack-sent) rst_counter = 6 Jul 1 20:21:32 icebreaker /kernel: isp0: ipcp output Jul 1 20:21:33 icebreaker /kernel: isp0: ipcp TO(ack-sent) rst_counter = 5 Jul 1 20:21:33 icebreaker /kernel: isp0: ipcp output Jul 1 20:21:34 icebreaker /kernel: isp0: ipcp TO(ack-sent) rst_counter = 4 Jul 1 20:21:34 icebreaker /kernel: isp0: ipcp output Jul 1 20:21:35 icebreaker /kernel: isp0: ipcp TO(ack-sent) rst_counter = 3 Jul 1 20:21:35 icebreaker /kernel: isp0: ipcp output Jul 1 20:21:36 icebreaker /kernel: isp0: ipcp TO(ack-sent) rst_counter = 2 Jul 1 20:21:36 icebreaker /kernel: isp0: ipcp output Jul 1 20:21:37 icebreaker /kernel: isp0: ipcp TO(ack-sent) rst_counter = 1 Jul 1 20:21:37 icebreaker /kernel: isp0: ipcp output Jul 1 20:21:38 icebreaker /kernel: isp0: ipcp TO(ack-sent) rst_counter = 0 Jul 1 20:21:38 icebreaker /kernel: isp0: lcp close(opened) Jul 1 20:21:38 icebreaker /kernel: isp0: phase terminate Jul 1 20:21:38 icebreaker /kernel: isp0: lcp output Jul 1 20:21:38 icebreaker /kernel: isp0: lcp input(closing): Jul 1 20:21:38 icebreaker /kernel: isp0: phase dead Jul 1 20:21:38 icebreaker /kernel: isp0: lcp down(closed) Jul 1 20:21:38 icebreaker /kernel: isp0: Down event (carrier loss) Jul 1 20:22:23 icebreaker /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error Jul 1 20:22:23 icebreaker /kernel: i4b-L1-isic_isac_irq: unit 0: Receive Aborted error Jul 1 20:22:24 icebreaker /kernel: i4b-L1-timer4_expired: state = F3 Deactivated (driver is the built-in verison in 3.1-stable) So why is the IPCP (0x8021) protocol is rejected all of a sudden ? Thanks for any tips on this, Andras To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message