From owner-freebsd-isdn Sun Apr 8 4: 1:46 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mailout05.sul.t-online.com (mailout05.sul.t-online.com [194.25.134.82]) by hub.freebsd.org (Postfix) with ESMTP id A17DD37B422; Sun, 8 Apr 2001 04:01:41 -0700 (PDT) (envelope-from martin@duskware.de) Received: from fwd04.aul.t-online.de by mailout05.sul.t-online.com with smtp id 14mCwu-0005Ix-08; Sun, 08 Apr 2001 13:01:40 +0200 Received: from night-porter.duskware.de (520038743430-0001@[217.0.156.254]) by fmrl04.sul.t-online.com with esmtp id 14mCwi-0PmTIWC; Sun, 8 Apr 2001 13:01:28 +0200 Received: (from martin@localhost) by night-porter.duskware.de (8.11.3/8.11.0) id f38B1GT00379; Sun, 8 Apr 2001 13:01:16 +0200 (MEST) From: Martin Husemann Message-Id: <200104081101.f38B1GT00379@night-porter.duskware.de> Subject: Re: PPP encapsulation In-Reply-To: "from (env: martin) at Apr 7, 2001 02:25:16 pm" To: martin@night-porter.duskware.de Date: Sun, 8 Apr 2001 13:01:16 +0200 (MEST) Cc: Brian Somers , Martin Husemann , freebsd-isdn@FreeBSD.org, joerg@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL78 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Sender: 520038743430-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok, tried it: did not work. Actually the framing implemented by if_spppsubr.c is not a complete implementation of RFC 1662 framing, it does not add the flag byte (0x7e) nor FCS. (The FCS was my main concern.) So it only prepends one byte adress (0xff for PPP = all stations), and a controll byte (unnumbered HDLC information element, 0x03). Not doing this makes the PPP conversation not work. Anyone know where this "sync PPP header" (see struct ppp_header in if_spppsubr.c) is specified? While there I noted that some comments and the statisitcs (bytes output, bytes received) always add 3 bytes, from comments indicating exactly the missing parts of RFC 1662 framing (one byte "flag", two byte FCS). IMHO both the comments and the +3 calculation are wrong. Maybe if in CISCO encapsulation mode, the sync hardware does add these, which means we should not add 3 bytes when in PPP mode. Probably best solution would be to add an element in strupt sppp giving the constant byte number added by hardware and always using that (which would be 0 in the PPP over ISDN case, 3 in the sync hardware case and yet something else in the application I'm currently working on). Anyone care to sanity check this? Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Apr 8 4:51:24 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id E279037B422 for ; Sun, 8 Apr 2001 04:51:19 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id NAA29961; Sun, 8 Apr 2001 13:50:20 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f38BT0j01298; Sun, 8 Apr 2001 13:29:00 +0200 (MET DST) (envelope-from j) Date: Sun, 8 Apr 2001 13:29:00 +0200 From: J Wunsch To: Brian Somers Cc: Martin Husemann , freebsd-isdn@FreeBSD.org Subject: Re: PPP encapsulation Message-ID: <20010408132900.H89922@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: <200104071129.f37BTjl55848@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200104071129.f37BTjl55848@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Sat, Apr 07, 2001 at 12:29:44PM +0100 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Brian Somers wrote: > I've cc'd Joerg in case I'm talking out my ass - I believe he wrote > sppp originally :-) Well, no, Sergej Vakulenko originally wrote it, but the original version lacked most of the features required by RFC 1661, it was a stripped-down version only intended to be run over hardware HDLC devices. >> For reasons completely unrelated to ISDN I'm currently modifying >> if_spppsubr.c to optionally work without adding/expeccting serial >> encapsulation (PPP in HDLC-like Framing, RFC 1662). I'm not sure i can follow you here... All PPP over ISDN implementations operate the way we do (and we can interoperate with them quite well). Sergej wrote the code for synchronous serial links, so it is obvious that even those links use some form of framing. I don't think you can just omit it. Give it a try, i'd be surprised if you could talk e. g. to a Cisco still afterwards. The RFCs are a bit vague at this. RFC 1618 talks about bit-synchronous HDLC to be used by default, with a reference to RFC 1549 (which has been obsoleted by 1662 later). RFC 1662 describes the framing in section 3, and then describes the octet stuffing in section 4 (which is used e. g. for asynchronous links), and the bit stuffing in section 5. I read this the way that section 3 always applies, while the methods described in section 4 and 5 are being used as alternatives, depending on the features of the underlying transport. Btw., i plan to re-merge the i4b additions into /sys/net/if_spppsubr.c in FreeBSD. The split never should have happened at all. I've already got the i4b CVS repo from Hellmuth, and examined all the diffs. There isn't that much at all, it's basically a few missing features (VJ header compression being the most notable). I've also examined the changes in NetBSD, and i think all of them look very interesting -- IPv6CP has been implemented, and they fixed a blatant operator precedence bug which i think is responsible for the problems some people have had with `half-dead IPCP' layers (where i recently committed a workaround in FreeBSD since i didn't see the original bug). In the end, i'd be interested in maintaining a single version of the file for both OSes, if possible. I see that NetBSD still seems to have all the #ifdef FreeBSD stuff in it, and thus i would retain the #ifdef NetBSD stuff in the FreeBSD version as well, so both files do not diverge too heavily. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Apr 8 5:17:41 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.com [194.25.134.81]) by hub.freebsd.org (Postfix) with ESMTP id 4129337B424 for ; Sun, 8 Apr 2001 05:17:38 -0700 (PDT) (envelope-from martin@duskware.de) Received: from fwd06.aul.t-online.de by mailout03.sul.t-online.com with smtp id 14mE8P-00040U-03; Sun, 08 Apr 2001 14:17:37 +0200 Received: from night-porter.duskware.de (520038743430-0001@[217.0.156.254]) by fmrl06.sul.t-online.com with esmtp id 14mE8N-0uAePYC; Sun, 8 Apr 2001 14:17:35 +0200 Received: (from martin@localhost) by night-porter.duskware.de (8.11.3/8.11.0) id f38CH6o06770; Sun, 8 Apr 2001 14:17:07 +0200 (MEST) From: Martin Husemann Message-Id: <200104081217.f38CH6o06770@night-porter.duskware.de> Subject: Re: PPP encapsulation In-Reply-To: <20010408132900.H89922@uriah.heep.sax.de> "from J Wunsch at Apr 8, 2001 01:29:00 pm" To: Joerg Wunsch Date: Sun, 8 Apr 2001 14:17:06 +0200 (MEST) Cc: Brian Somers , Martin Husemann , freebsd-isdn@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL78 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Sender: 520038743430-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm not sure i can follow you here... All PPP over ISDN > implementations operate the way we do (and we can interoperate with > them quite well). Yeah, found out in the mean time ;-) Note that I came to this from a completely different point of view where I need the ppp packet without any framing (i.e. starting with the protocol identifier). I've just been curious, as the RFC realy is not that clear. > Btw., i plan to re-merge the i4b additions into /sys/net/if_spppsubr.c > in FreeBSD. The split never should have happened at all. Good plan. For extra joy you might try merging the NetBSD version into that as well (it has IPv6 support). If you punt on that (which I surely could understand), I'll take the opposite route and merge your result into the NetBSD version. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Apr 8 12:35:42 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from smtp.kdt.de (ns2.kdt.de [195.8.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 46A4937B422 for ; Sun, 8 Apr 2001 12:35:27 -0700 (PDT) (envelope-from is@beverly.kleinbus.org) Received: from jocelyn.sub-etha.wtal.de (line0632.kdt.de [213.240.147.50]) by smtp.kdt.de (8.8.8/8.8.8) with ESMTP id VAA11901 for ; Sun, 8 Apr 2001 21:35:25 +0200 Received: from marie.sub-etha.wtal.de (marie.sub-etha.wtal.de [213.240.145.124]) by jocelyn.sub-etha.wtal.de (Postfix) with ESMTP id 670092A8 for ; Sun, 8 Apr 2001 21:20:47 +0200 (CEST) Received: by marie.sub-etha.wtal.de (Postfix, from userid 1501) id BC04E64DE; Sun, 8 Apr 2001 21:19:42 +0200 (CEST) Date: Sun, 8 Apr 2001 21:19:42 +0200 From: Ignatios Souvatzis Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: PPP encapsulation Message-ID: <20010408211942.A10788@beverly.kleinbus.org> References: <200104071129.f37BTjl55848@hak.lan.Awfulhak.org> <20010408132900.H89922@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010408132900.H89922@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Sun, Apr 08, 2001 at 01:29:00PM +0200 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Apr 08, 2001 at 01:29:00PM +0200, J Wunsch wrote: > The RFCs are a bit vague at this. RFC 1618 talks about > bit-synchronous HDLC to be used by default, with a reference to RFC > 1549 (which has been obsoleted by 1662 later). RFC 1662 describes the > framing in section 3, and then describes the octet stuffing in section > 4 (which is used e. g. for asynchronous links), and the bit stuffing > in section 5. I read this the way that section 3 always applies, > while the methods described in section 4 and 5 are being used as > alternatives, depending on the features of the underlying transport. right. Please forgive me if I iterate stuff that all of you know. Basically, HDLC consists of several layers... a) some sort of bit/byte stuffing and framing and basic data integrity. a1) On sync links, a frame is delimited by 01111110 .... 01111110. After each 5 consecutive 1 in the data, a 0 is inserted on the wire (and removed on reception), so that 0x7E can be transmitted. A packet is (usually) ended by a 16 bit crc using the polynomial we all love. a2) On async, character-oriented links, the character-stuffing rules apply: 0x7E ... 0x7E are the frame delimiters 0x7E is used to escape 0x7E (and others that need it), and the escaped octet is xored with 0x20. crc is applied as above. a3) in theory, HDLC could be done over any other transport that gives you known-sized, crc-or-similar-secured (in the sense of "known to be good or ignored if known to be bad") data packets. PPP over some media makes use of this, most infamous being PPPoE. b) above that, HDLC gives you: - addressing. a HDLC packet starts with an address, which is potentially variable sized... the first n-1 bytes are even, the last one is odd. In theory, HDLC could be applied to links with more than 2 stations. especially, there is the all-stations address, 0xff, which is received by any station that sees it. - a control byte distinguishing several types of packets. 1. connection state control packets for link state control, if you need this. 2. sequence numbered data packets with retransmission and flow control, vaguely similar to a simplified TCP. (e.g. X.25 uses this to transmits its control and data reliably to the next station; I think ISDN D-channel communication uses this, too, to talk to the switch at the other end). 3. unnumbered data packets, (officially: unnumbered information), whose code is --- surprise surprise --- 0x03. - the data following is packet type dependent, with unnumbered information packets you have only the user data. Now, _usually_, PPP uses the all-stations addressing, and puts the higher level data (be it LCP, IPCP, IP, ...) inside UI frames, resulting in the ff 03 at the start of packets. If and only if this is the case, LCP makes it possible to negotiate with your peer that you want to compress those bytes by eliminating them. LCP is always sent with address and control in front, so that it always works even if the peers have somehow lost synchronization. (btw, PPP (RFC 1662 again) discourages this (as well as compressing the PPP packet type into one byte) because ff, 03, and two bytes of packet type give you longword alignment, which is nice for DMA hardware). Synchronoous HDLC hardware usually handles bit stuffing, framing and CRC detection. (If I recall right, adding TWO crcs might work, you only end up with 2 bytes of garbage before the next frame delimiting flag, or rather, at the end of the data.) Regards, Ignatios To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Apr 8 13:57:54 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 8A03D37B423 for ; Sun, 8 Apr 2001 13:57:51 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id WAA16765; Sun, 8 Apr 2001 22:57:50 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f38Kcx300556; Sun, 8 Apr 2001 22:38:59 +0200 (MET DST) (envelope-from j) Date: Sun, 8 Apr 2001 22:38:59 +0200 From: J Wunsch To: Martin Husemann Cc: freebsd-isdn@FreeBSD.org Subject: Re: PPP encapsulation Message-ID: <20010408223859.B518@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: <200104081101.f38B1GT00379@night-porter.duskware.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200104081101.f38B1GT00379@night-porter.duskware.de>; from martin@duskware.de on Sun, Apr 08, 2001 at 01:01:16PM +0200 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Martin Husemann wrote: > Actually the framing implemented by if_spppsubr.c is not a complete > implementation of RFC 1662 framing, it does not add the flag byte (0x7e) nor > FCS. (The FCS was my main concern.) I also wondered how this is supposed to happen, yes. Well, the flag _byte_ is only for octet stuffing (aka. running over an async line), while bit stuffing uses a flag bit sequence. My guess is that this flag sequence is already handled in hardware anyway (at least that's how i remember it from the old Z80 SIO which could do hardware HDLC). I have no idea about the FCS... The way it's done right now is what i have inherited from Sergej when i started modifying sppp(4). Since it happens to work against a good number of peers, i never thought about it. We could dump the raw ISDN data and analyze it... -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Apr 10 0: 4:37 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from princess.vanderfeest.nl (princess.vanderfeest.nl [212.204.230.181]) by hub.freebsd.org (Postfix) with ESMTP id 25D6C37B422 for ; Tue, 10 Apr 2001 00:04:29 -0700 (PDT) (envelope-from psd+freebsd-isdn@vanderfeest.nl) Received: (from syswww@localhost) by princess.vanderfeest.nl (8.11.2/8.11.2/psd) id f3A70RH21172 for freebsd-isdn@freebsd.org; Tue, 10 Apr 2001 09:00:27 +0200 (CEST) To: freebsd-isdn@freebsd.org Subject: ISDN doesn't work suddenly; kernel errors? Message-ID: <986886027.3ad2af8b4c11b@webmail.vanderfeest.nl> Date: Tue, 10 Apr 2001 09:00:27 +0200 (CEST) From: Paul Dekkers MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Prince Productions WEBMAIL X-Originating-IP: 213.227.129.201 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have a dial-on-demand box with an ISDN-card running on 4.1-RELEASE; after some restarts suddenly things don't work anymore; My kernel gives me: i4b: ISDN call control device attached i4bisppp: 4 ISDN SyncPPP device(s) attached (VJ header compression) i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 4 ISDN trace device(s) attached but also: i4b-L2 i4b_T202_timeout: unit 0, N202 = 3 i4b-L3 T303_timeout: SETUP not answered, cr = 75 i4b-L3 next_l3state: FSM illegal state, state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! i4b-L1 dchan_receive: bad read status 0xb0 i4b-L2 i4b_ph_data_ind: ERROR, S-frame < 6 octetts! i4b-L1 dchan_receive: bad read status 0xb0 i4b-L2 i4b_ph_data_ind: ERROR, S-frame < 6 octetts! i4b-L2 i4b_T202_timeout: unit 0, N202 = 3 i4b-L3 T303_timeout: SETUP not answered, cr = 78 i4b-L3 next_l3state: FSM illegal state, state = ST_OW - Out Wait EST, event = EV _T303EXP - T303 timeout! (where things go wrong I think...) And when I try to dialout using my ppp (userland) it gives me: Phase: deflink: hangup -> opening Phase: deflink: Enter pause (3) for redialing. Phase: deflink: Connected! Phase: deflink: opening -> dial Phase: deflink: dial -> carrier Phase: deflink: /dev/i4brbch0: No carrier (increase ``set cd'' from 6 ?) Phase: deflink: Disconnected! Phase: deflink: carrier -> hangup Phase: deflink: Connect time: 6 secs: 0 octets in, 0 octets out Phase: total 0 bytes/sec, peak 0 bytes/sec on Sat Apr 7 11:30:53 2001 Where it used to connect to my ISP. Is this a sign of a broken card? Or broken line? (Other devices on my ISDN conection work, and I also tried to replace the cable...) Thank you in advance, Paul Dekkers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Apr 10 2:26:37 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id 8DB3B37B422 for ; Tue, 10 Apr 2001 02:26:34 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de (hcswork.hcs.de [172.24.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id B16DBBA27; Tue, 10 Apr 2001 11:26:33 +0200 (CEST) Received: by hcswork.hcs.de (Postfix, from userid 200) id 8E512533; Tue, 10 Apr 2001 11:26:33 +0200 (METDST) Subject: Re: ISDN doesn't work suddenly; kernel errors? In-Reply-To: <986886027.3ad2af8b4c11b@webmail.vanderfeest.nl> "from Paul Dekkers at Apr 10, 2001 09:00:27 am" To: Paul Dekkers Date: Tue, 10 Apr 2001 11:26:33 +0200 (METDST) Cc: freebsd-isdn@freebsd.org Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL84 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20010410092633.8E512533@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 Paul Dekkers: > I have a dial-on-demand box with an ISDN-card running on 4.1-RELEASE; > after some restarts suddenly things don't work anymore; What card do you have and what i4b release do you use ? 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 Apr 10 11:24:16 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from princess.vanderfeest.nl (princess.vanderfeest.nl [212.204.230.181]) by hub.freebsd.org (Postfix) with ESMTP id 7B58437B422 for ; Tue, 10 Apr 2001 11:24:12 -0700 (PDT) (envelope-from paul@princeproductions.nl) Received: (from psd@localhost) by princess.vanderfeest.nl (8.11.2/8.11.2/psd) id f3AIJxI22683; Tue, 10 Apr 2001 20:19:59 +0200 (CEST) Date: Tue, 10 Apr 2001 20:19:59 +0200 From: Paul Dekkers To: Hellmuth Michaelis Cc: freebsd-isdn@freebsd.org Subject: Re: ISDN doesn't work suddenly; kernel errors? Message-ID: <20010410201959.A22678@princess.vanderfeest.nl> References: <986886027.3ad2af8b4c11b@webmail.vanderfeest.nl> <20010410092633.8E512533@hcswork.hcs.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20010410092633.8E512533@hcswork.hcs.de>; from hm@hcs.de on Tue, Apr 10, 2001 at 11:26:33AM +0200 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, On Tue, Apr 10, 2001 at 11:26:33AM +0200, Hellmuth Michaelis wrote: > From the keyboard of Paul Dekkers: > > > I have a dial-on-demand box with an ISDN-card running on 4.1-RELEASE; > > after some restarts suddenly things don't work anymore; > > What card do you have and what i4b release do you use ? It's a Dynalink card, I believe the IS128PH(?) The kernel says: iwic0: port 0xe000-0xe0ff mem 0xd5001000-0xd5001fff irq 10 at device 12.0 on pci0 iwic0: passive stack unit 0 I use beta Version 0.96.00 / October 2000 This morning, after a shutdown for 5 minutes, it worked again, but after a few hours it stopped. Strange. A simple reboot doesn't help (I think I have to turn it on, but I have no physical access to the machine by now...) BTW, Some new errors: i4b: unit 0, assigned TEI = 97 = 0x61 i4b-L4 i4b_l4_setup_timeout_fix_unit: 986889578: ERROR: idletime[900]+earlyhup[5] > unitlength[60]! i4b-L4 i4b_l4_setup_timeout_fix_unit: 986889992: ERROR: idletime[900]+earlyhup[5] > unitlength[60]! i4b-L4 i4b_l4_setup_timeout_fix_unit: 986890010: ERROR: idletime[900]+earlyhup[5] > unitlength[60]! i4b-L4 i4b_l4_setup_timeout_fix_unit: 986890211: ERROR: idletime[900]+earlyhup[5] > unitlength[60]! i4b-L1 dchan_receive: bad read status 0xb0 i4b-L2 i4b_ph_data_ind: ERROR, I-frame < 6 octetts! i4b-L1 dchan_receive: bad read status 0xb0 i4b-L2 i4b_ph_data_ind: ERROR, S-frame < 6 octetts! i4b-L1 dchan_receive: bad read status 0xb0 i4b-L2 i4b_ph_data_ind: ERROR, S-frame < 6 octetts! sio0: 60 more interrupt-level buffer overflows (total 60) Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Apr 10 11:36: 7 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id F0D5337B422; Tue, 10 Apr 2001 11:36:04 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de (hcswork.hcs.de [172.24.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id E3538BA29; Tue, 10 Apr 2001 20:36:03 +0200 (CEST) Received: by hcswork.hcs.de (Postfix, from userid 200) id BA8D6535; Tue, 10 Apr 2001 20:36:03 +0200 (METDST) Subject: Re: ISDN doesn't work suddenly; kernel errors? In-Reply-To: <20010410201959.A22678@princess.vanderfeest.nl> "from Paul Dekkers at Apr 10, 2001 08:19:59 pm" To: Paul Dekkers Date: Tue, 10 Apr 2001 20:36:03 +0200 (METDST) Cc: freebsd-isdn@freebsd.org Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL84 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20010410183603.BA8D6535@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 Paul Dekkers: > The kernel says: > iwic0: port 0xe000-0xe0ff mem 0xd5001000-0xd5001fff irq 10 at device 12.0 on pci0 There is a fix for this problem available at http://www.freebsd-support.de/i4b/tmp/iwic-160101.tar.gz It replaces the files in the iwic driver subdirectory. This has been fixed in -current and the -current i4b is also available for 4.x by using the scripts and files found in http://www.freebsd-support.de/i4b/addons/i4b-co2stable-kit.tar.gz 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 Apr 10 23:36:35 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from princess.vanderfeest.nl (princess.vanderfeest.nl [212.204.230.181]) by hub.freebsd.org (Postfix) with ESMTP id 5859637B422 for ; Tue, 10 Apr 2001 23:36:33 -0700 (PDT) (envelope-from paul@princeproductions.nl) Received: (from psd@localhost) by princess.vanderfeest.nl (8.11.2/8.11.2/psd) id f3B6WLC23963; Wed, 11 Apr 2001 08:32:21 +0200 (CEST) Date: Wed, 11 Apr 2001 08:32:21 +0200 From: Paul Dekkers To: Hellmuth Michaelis Cc: freebsd-isdn@freebsd.org Subject: Re: ISDN doesn't work suddenly; kernel errors? Message-ID: <20010411083221.A23954@princess.vanderfeest.nl> References: <20010410201959.A22678@princess.vanderfeest.nl> <20010410183603.BA8D6535@hcswork.hcs.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20010410183603.BA8D6535@hcswork.hcs.de>; from hm@hcs.de on Tue, Apr 10, 2001 at 08:36:03PM +0200 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, On Tue, Apr 10, 2001 at 08:36:03PM +0200, Hellmuth Michaelis wrote: > > > The kernel says: > > iwic0: port 0xe000-0xe0ff mem 0xd5001000-0xd5001fff irq 10 at device 12.0 on pci0 > > There is a fix for this problem available at > > http://www.freebsd-support.de/i4b/tmp/iwic-160101.tar.gz I replaces the files in my /home/.../layer1_nb/iwic directory, and did a 'make depend', and 'make' & 'make install'... Still, no connection, and; i4b-L2 i4b_T202_timeout: unit 0, N202 = 3 i4b-L3 T303_timeout: SETUP not answered, cr = 37 i4b-L3 next_l3state: FSM illegal state, state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! Strange, because the card worked for about a month without any problems. Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Apr 11 4:45:59 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from princess.vanderfeest.nl (princess.vanderfeest.nl [212.204.230.181]) by hub.freebsd.org (Postfix) with ESMTP id 1893937B422 for ; Wed, 11 Apr 2001 04:45:56 -0700 (PDT) (envelope-from psd+freebsd-isdn@vanderfeest.nl) Received: (from syswww@localhost) by princess.vanderfeest.nl (8.11.2/8.11.2/psd) id f3BBfYJ26700 for freebsd-isdn@freebsd.org; Wed, 11 Apr 2001 13:41:34 +0200 (CEST) To: freebsd-isdn@freebsd.org Subject: Serial ISDN device Message-ID: <986989294.3ad442ee4b8a5@webmail.vanderfeest.nl> Date: Wed, 11 Apr 2001 13:41:34 +0200 (CEST) From: Paul Dekkers MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Prince Productions WEBMAIL X-Originating-IP: 213.227.129.103 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Because of my not working ISDN-card, I tried, as a temporary solution, an external adapter. This was also without any luck; I have my ppp.conf entry included below. This should work, shouldn't it? When I use cu -l /dev/cuaa0 and connect to my ISP using ATDT I get 'CONNECT HDsomething'... Why doesn't my ppp negotiate? It tells me there is a carrier (cuaa0: CD detect) and that it's busy with lcp... After that it disconnects and shows it sent some bytes. Maybe there is something wrong with my config? Thank you in advance, and I hope that there is some solution for my other problem... (I'm sure I run the new kernel, because of uname...) Paul default: isp: set phone ... set authname ... set authkey ... nat enable yes set dial "ABORT BUSY ABORT NO\\sCARRIER \"\" ATZ OK-ATZ-OK ATDT\\T CONNECT" # set enddisc mac # enable lqr set reconnect 3 5 set redial 3 10 # set lqrperiod 45 # disable pred1 deflate # deny pred1 deflate set timeout 60 120 set device /dev/cuaa0 set speed 115200 set ifaddr 127.1.1.1/0 127.2.2.2/0 255.255.255.0 add 0 0 127.2.2.2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Apr 11 5:37:47 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from speer.nl.uu.net (speer.nl.uu.net [193.67.79.174]) by hub.freebsd.org (Postfix) with ESMTP id 8CAF837B422 for ; Wed, 11 Apr 2001 05:37:43 -0700 (PDT) (envelope-from jak01@pop3.NL.net) Received: from 1Cust82.tnt27.rtm1.nl.uu.net ([213.116.148.82]:1139 "EHLO pop3.NL.net") by speer.nl.uu.net with ESMTP id ; Wed, 11 Apr 2001 14:37:28 +0200 Message-ID: <3AD4502F.AF99CD0C@pop3.NL.net> Date: Wed, 11 Apr 2001 14:38:07 +0200 From: Arjan Knepper X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-isdn@FreeBSD.ORG Cc: Paul Dekkers Subject: Re: Serial ISDN device References: <986989294.3ad442ee4b8a5@webmail.vanderfeest.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Paul Dekkers wrote: > Hi, > > Because of my not working ISDN-card, I tried, as a temporary solution, an > external adapter. This was also without any luck; What kind of ISDN-card do you have? > I have my ppp.conf entry included below. This should work, shouldn't it? Here is a working ppp.conf entry for use with a external Victory TA128A isdn adapter. Make sure to set the serialport speed of the TA and PC to the same value. >----------------------------------------------< default: set log Phase Chat LCP IPCP CCP tun command set ifaddr .... ISP: set device /dev/cuaa0 set speed 115200 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATE0Q0 OK-AT-OK \\dATD\\T TIMEOUT 40 CONNECT ATE0Q1" set phone 1234567890 add default HISADDR set authname .. set authkey ... set timeout 90 # filters set filter ..... .... >----------------------------------------------< > > > When I use cu -l /dev/cuaa0 and connect to my ISP using ATDT I get 'CONNECT > HDsomething'... Why doesn't my ppp negotiate? It tells me there is a carrier > (cuaa0: CD detect) and that it's busy with lcp... After that it disconnects and > shows it sent some bytes. > > Maybe there is something wrong with my config? > > Thank you in advance, and I hope that there is some solution for my other > problem... (I'm sure I run the new kernel, because of uname...) > > Paul > > default: > > isp: > set phone ... > set authname ... > set authkey ... > > nat enable yes > > set dial "ABORT BUSY ABORT NO\\sCARRIER \"\" ATZ OK-ATZ-OK ATDT\\T CONNECT" > > # set enddisc mac > > # enable lqr > set reconnect 3 5 > set redial 3 10 > # set lqrperiod 45 > # disable pred1 deflate > # deny pred1 deflate > > set timeout 60 120 > > set device /dev/cuaa0 > set speed 115200 > > set ifaddr 127.1.1.1/0 127.2.2.2/0 255.255.255.0 > add 0 0 127.2.2.2 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isdn" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message