From owner-freebsd-isdn Sun Jun 11 5:14:44 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from ns.engels.san.ru (ns.engels.san.ru [213.242.33.130]) by hub.freebsd.org (Postfix) with ESMTP id 15A8137B832 for ; Sun, 11 Jun 2000 05:14:40 -0700 (PDT) (envelope-from west@engels.san.ru) Received: from e2 ([213.242.33.147]) by ns.engels.san.ru (8.9.3/8.9.3) with SMTP id QAA23243 for ; Sun, 11 Jun 2000 16:17:19 +0400 (MSD) Message-ID: <000901bfd39e$85413580$8621f2d5@e2.engels.san.ru> From: "Sergey S. West" To: Subject: Date: Sun, 11 Jun 2000 16:10:57 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! How to point ISDN card Asuscom ISDN link 128K Adapter (ASU1688) in the configuration file of a kernel (FreeBSD-4.0)? In the file of /sys/src/i4b/FreeBSD/CONFIG of such card is not present. I tried to point #Teles S0/16.3 PnP card (PnP): options "TEL_S0_16_3_P" device isic0 # It does not work, writes /kernel: unknown: < ISDN CARD.... > can " t assign resources Sergey West. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Jun 11 7:59:15 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from smtp-out.freegates.be (smtp-out.freegates.be [212.35.2.51]) by hub.freebsd.org (Postfix) with ESMTP id 4DD4A37B702 for ; Sun, 11 Jun 2000 07:59:12 -0700 (PDT) (envelope-from lorenzo@linuxbe.org) Received: from ppp-18-222.freegates.be ([212.35.18.223] helo=natalie) by smtp-out.freegates.be with smtp (Exim on FreeGates) id 1319Cg-0001cR-00 for ; Sun, 11 Jun 2000 16:59:10 +0200 Message-ID: <000301bfd3b5$625d82a0$0101a8c0@natalie> From: "Sansonetti Laurent" To: Subject: US-R Sportster ISDN adapter on FreeBSD 4.0 Date: Sun, 11 Jun 2000 16:57:35 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I want to use my US-ROBOTICS sportster internal ISDN adapter on my freebsd 4.0. I saw in the file Cards with the i4b 0.90 beta that this card is only supported on fbsd 3.4. Is there a way to make it works on fbsd 4.0 ? Thanks for all, and sorry for my horrible english ;) -- Sansonetti Laurent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Jun 11 12:43: 7 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from numbertwo.domainfactory.de (numbertwo.domainfactory.de [194.221.134.226]) by hub.freebsd.org (Postfix) with SMTP id 854E337B64C for ; Sun, 11 Jun 2000 12:43:03 -0700 (PDT) (envelope-from milagro@soundex.org) Received: (qmail 26903 invoked from network); 11 Jun 2000 19:43:02 -0000 Received: from pec-88-123.tnt6.b2.uunet.de (HELO faust.soundex.org) ([149.225.88.123]) (envelope-sender ) by numbertwo.domainfactory.de (qmail-ldap-1.03) with SMTP for ; 11 Jun 2000 19:43:02 -0000 Date: Sun, 11 Jun 2000 21:45:27 +0200 From: milagro X-Mailer: The Bat! (v1.42f) UNREG / CD5BF9353B3B7091 Reply-To: milagro X-Priority: 3 (Normal) Message-ID: <3512775912.20000611214527@soundex.org> To: freebsd-isdn@FreeBSD.ORG Subject: automatic redial.... 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 Hi, how can tell i4b to redial after the connection has been reset for whatever reason? My provider disconnects me after 24h of constant usage so I want i4b to connect again right after they kicked my connection. thanx Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Jun 11 13: 1:16 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 6D26737B9E6 for ; Sun, 11 Jun 2000 13:01:07 -0700 (PDT) (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 VAA30286; Sun, 11 Jun 2000 21:02:36 +0100 (BST) (envelope-from brian@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 VAA02494; Sun, 11 Jun 2000 21:02:33 +0100 (BST) (envelope-from brian@Awfulhak.org) Message-Id: <200006112002.VAA02494@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: milagro Cc: freebsd-isdn@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: automatic redial.... In-Reply-To: Message from milagro of "Sun, 11 Jun 2000 21:45:27 +0200." <3512775912.20000611214527@soundex.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 11 Jun 2000 21:02:33 +0100 From: Brian Somers Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > > how can tell i4b to redial after the connection > has been reset for whatever reason? My provider > disconnects me after 24h of constant usage so I want > i4b to connect again right after they kicked my > connection. Use ``set reconnect'' in ppp(8) :-) > thanx > Alex -- 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 Jun 11 13: 7:13 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from alice.turbocat.de (gate.turbocat.de [212.41.163.6]) by hub.freebsd.org (Postfix) with ESMTP id D187F37B814 for ; Sun, 11 Jun 2000 13:07:07 -0700 (PDT) (envelope-from dave@turbocat.de) Received: from cat.turbocat.de (cat.turbocat.de [212.41.163.194]) by alice.turbocat.de (8.10.1/8.10.1/07072000/dw/1) with ESMTP id e5BK74P07877; Sun, 11 Jun 2000 22:07:04 +0200 (CEST) Received: (from dave@localhost) by cat.turbocat.de (8.8.5/8.7.3) id WAA00233; Sun, 11 Jun 2000 22:07:04 +0200 (MET DST) Message-Id: <200006112007.WAA00233@cat.turbocat.de> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) In-Reply-To: <3512775912.20000611214527@soundex.org> X-Nextstep-Mailer: Mail 4.0 (Enhance 2.0b4) Received: by NeXT.Mailer (1.148) From: David Wetzel Date: Sun, 11 Jun 2000 22:07:03 +0200 To: milagro Subject: Re: automatic redial.... Cc: freebsd-isdn@FreeBSD.ORG References: <3512775912.20000611214527@soundex.org> Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > how can tell i4b to redial after the connection > has been reset for whatever reason? My provider > disconnects me after 24h of constant usage so I want > i4b to connect again right after they kicked my > connection. ping -i 5 some.other.host.com --- _ _ _(_)(_)_ 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 Sun Jun 11 14:20: 3 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 2CD3F37BAB3 for ; Sun, 11 Jun 2000 14:19:37 -0700 (PDT) (envelope-from bitbucket@adenzel.demon.nl) Received: from [212.238.95.18] (helo=adenzel.demon.nl) by post.mail.nl.demon.net with esmtp (Exim 3.14 #2) id 131F5H-00019Z-00 for freebsd-isdn@FreeBSD.ORG; Sun, 11 Jun 2000 21:15:55 +0000 Message-ID: <39440408.B64D7D7@adenzel.demon.nl> Date: Sun, 11 Jun 2000 21:26:32 +0000 From: Alex van Denzel X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.32 i586) X-Accept-Language: en MIME-Version: 1.0 To: ISDN4BSD Mailing list Subject: help Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org help -- Alex Replace bitbucket with anything else. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Jun 11 14:51:35 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 815E737C92C for ; Sun, 11 Jun 2000 14:51:24 -0700 (PDT) (envelope-from bitbucket@adenzel.demon.nl) Received: from [212.238.95.18] (helo=adenzel.demon.nl) by post.mail.nl.demon.net with esmtp (Exim 3.14 #2) id 131Fdb-0001VQ-00 for freebsd-isdn@FreeBSD.ORG; Sun, 11 Jun 2000 21:51:23 +0000 Message-ID: <39440C58.89999D04@adenzel.demon.nl> Date: Sun, 11 Jun 2000 22:02:00 +0000 From: Alex van Denzel X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.32 i586) X-Accept-Language: en MIME-Version: 1.0 To: ISDN4BSD Mailing list Subject: Re: help References: <39440408.B64D7D7@adenzel.demon.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alex van Denzel wrote: > > help Sorry. Wrong email address -- Alex Replace bitbucket with anything else. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Jun 12 1:21:35 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id CB5A837BE3D for ; Mon, 12 Jun 2000 01:21:30 -0700 (PDT) (envelope-from pherman@at12.de) Received: from bagabeedaboo.security.at12.de (dial-194-8-209-16.netcologne.de [194.8.209.16]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id KAA26438 for ; Mon, 12 Jun 2000 10:21:28 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.1/8.10.1) with ESMTP id e5C8LIm00597 for ; Mon, 12 Jun 2000 10:21:18 +0200 (CEST) Date: Mon, 12 Jun 2000 10:21:18 +0200 (CEST) From: Paul Herman To: freebsd-isdn@freebsd.org Subject: only getting as far as "Ppp" with user ppp over raw B channel 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 Hello ISDNers, I checked handbook, faq, and mailing lists, and came up dry, so here goes... When I use ppp over /dev/i4brbch0 it somehow doesn't want to continue into IPCP even though PAP is sucessfuly authenticaed. I'm running FreeBSD 3.4-RELEASE, i4b 0.83, PPP Version 2.24. i4b works great when I use sppp/isp0, and PPP works fine when I use a modem over serial port, so I must have a config problem somewhere... Per PPP FAQ I've tried many different configurations including disable/deny pred1 deflate deflate24 protocomp acfcomp shortseq vj with the same results. "enable lqr", "set lqrperiod" and "set cd 6" as shown in /usr/share/examples/ppp/ppp.conf.isdn also have no effect. I'm very familiar with PPP, but over /dev/i4brbch0 I know of no way to sniff traffic to see what's going on (like with 'ifconfig isp0 debug' or 'tcpdump -i isp0' for example), so can only rely on what's in /var/log/ppp.log. Any ideas on what I'm doing wrong? last part of /var/log/ppp.log: ppp[518]: tun0: LCP: deflink: RecvConfigAck(1) state = Ack-Sent ppp[518]: tun0: LCP: deflink: State change Ack-Sent --> Opened ppp[518]: tun0: LCP: deflink: LayerUp ppp[518]: tun0: Phase: bundle: Authenticate ppp[518]: tun0: Phase: deflink: his = PAP, mine = PAP ppp[518]: tun0: Phase: Pap Output: loginname ******** ppp[518]: tun0: Phase: Pap Input: SUCCESS () ------ here it hangs until I close the link, or i4b times out ----- /etc/ppp/ppp.conf (phone/login/passwd changed): nc: set device /dev/i4brbch0 set log phase chat lcp ipcp ccp tun set phone 1234567 set speed sync set authname loginname set authkey xxxxxxx enable pap accept pap disable chap set redial 5 10 set timeout 60 set ifaddr 10.0.0.1/0 10.0.0.2/0 add! default HISADDR set dial set login set hangup set mrru 1500 Thanks, -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Jun 12 3:31:15 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 4A18637BDC9 for ; Mon, 12 Jun 2000 03:31:07 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id LAA75624; Mon, 12 Jun 2000 11:31:04 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id LAA01352; Mon, 12 Jun 2000 11:31:01 +0100 (BST) (envelope-from brian@Awfulhak.org) Message-Id: <200006121031.LAA01352@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Paul Herman Cc: freebsd-isdn@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: only getting as far as "Ppp" with user ppp over raw B channel In-Reply-To: Message from Paul Herman of "Mon, 12 Jun 2000 10:21:18 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Jun 2000 11:31:01 +0100 From: Brian Somers Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ``Ppp'' means that authentication hasn't yet completed. This is because you've got ``enable pap'' in your config - insisting that your ISP authenticates themselves. Remove the ``enable pap'' and everything should work ok. > Hello ISDNers, > > I checked handbook, faq, and mailing lists, and came up dry, so here > goes... > > When I use ppp over /dev/i4brbch0 it somehow doesn't want to > continue into IPCP even though PAP is sucessfuly authenticaed. > > I'm running FreeBSD 3.4-RELEASE, i4b 0.83, PPP Version 2.24. i4b > works great when I use sppp/isp0, and PPP works fine when I use a > modem over serial port, so I must have a config problem somewhere... > > Per PPP FAQ I've tried many different configurations including > disable/deny pred1 deflate deflate24 protocomp acfcomp shortseq vj > with the same results. "enable lqr", "set lqrperiod" > and "set cd 6" as shown in /usr/share/examples/ppp/ppp.conf.isdn > also have no effect. > > I'm very familiar with PPP, but over /dev/i4brbch0 I know of no way to > sniff traffic to see what's going on (like with 'ifconfig isp0 debug' > or 'tcpdump -i isp0' for example), so can only rely on what's in > /var/log/ppp.log. > > Any ideas on what I'm doing wrong? > > last part of /var/log/ppp.log: > > ppp[518]: tun0: LCP: deflink: RecvConfigAck(1) state = Ack-Sent > ppp[518]: tun0: LCP: deflink: State change Ack-Sent --> Opened > ppp[518]: tun0: LCP: deflink: LayerUp > ppp[518]: tun0: Phase: bundle: Authenticate > ppp[518]: tun0: Phase: deflink: his = PAP, mine = PAP > ppp[518]: tun0: Phase: Pap Output: loginname ******** > ppp[518]: tun0: Phase: Pap Input: SUCCESS () > ------ here it hangs until I close the link, or i4b times out ----- > > /etc/ppp/ppp.conf (phone/login/passwd changed): > nc: > set device /dev/i4brbch0 > set log phase chat lcp ipcp ccp tun > set phone 1234567 > set speed sync > set authname loginname > set authkey xxxxxxx > enable pap > accept pap > disable chap > set redial 5 10 > set timeout 60 > set ifaddr 10.0.0.1/0 10.0.0.2/0 > add! default HISADDR > set dial > set login > set hangup > set mrru 1500 > > Thanks, > -Paul. -- 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 Mon Jun 12 4:14:25 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F2C.dip.t-dialin.net [62.155.143.44]) by hub.freebsd.org (Postfix) with ESMTP id ED9E237CA7D for ; Mon, 12 Jun 2000 04:14:20 -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 NAA30802; Mon, 12 Jun 2000 13:09:03 +0200 (CEST) Message-Id: <200006121109.NAA30802@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Sansonetti Laurent" Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: US-R Sportster ISDN adapter on FreeBSD 4.0 Reply-To: Gary Jennejohn In-reply-to: Your message of "Sun, 11 Jun 2000 16:57:35 +0200." <000301bfd3b5$625d82a0$0101a8c0@natalie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Jun 2000 13:09:03 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Sansonetti Laurent" writes: >Hello, > >I want to use my US-ROBOTICS sportster internal ISDN adapter on my freebsd >4.0. > >I saw in the file Cards with the i4b 0.90 beta that this card is only >supported on fbsd 3.4. > >Is there a way to make it works on fbsd 4.0 ? > >Thanks for all, and sorry for my horrible english ;) > I ported it on February 21, 2000. It should work in 4.0. Just try it. Use what's in /sys/i4b, NOT the beta ! --- Gary Jennejohn / garyj@muc.de 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 Mon Jun 12 4:55:27 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id DCC7337B634 for ; Mon, 12 Jun 2000 04:55:21 -0700 (PDT) (envelope-from kwah@gmx.net) Received: from gmx.net (dial-194-8-195-109.netcologne.de [194.8.195.109]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id NAA13863; Mon, 12 Jun 2000 13:55:19 +0200 (MET DST) Message-ID: <3944D256.9E238756@gmx.net> Date: Mon, 12 Jun 2000 14:06:46 +0200 From: Emre X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-isdn@FreeBSD.ORG Subject: Remote dialin fails with CBCP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm having a couple of problems creating a profile for a dialin where my end is being called back. I have two ISP's to connect, one 'normal', the other with CBCP. Dialing my 'normal' ISP works great, but when I use a second dialout profile with CBCP the call coming back is not processed by I4b (as far as I can say). The configuration is as follows: isdnd.rc: # Second Profile (Callback) entry name = mb usrdevicename = rbch usrdeviceunit = 0 isdncontroller = 0 isdnchannel = -1 local-phone-incoming = nr_myself remote-phone-incoming = nr_isp local-phone-dialout = nr_myself remote-phone-dialout = nr_isp remdial-handling = last dialin-reaction = accept dialout-type = calledback b1protocol = hdlc idletime-incoming = 240 idletime-outgoing = 30 ratetype = 0 unitlength = 90 unitlengthsrc = rate dialretries = 3 dialrandincr = on recoverytime = 30 usedown = off downtries = 2 downtime = 30 calledbackwait = 10 ppp.conf: mb: set authname myname set authkey mypw set phone nr_isp set timeout 300 set bandwidth 65536 set mrru 1500 set callback cbcp set cbcp * clone 1,2 link deflink rm link * set mode auto set autoload 10 100 30 The PPP negotiation seems to work fine: [...] Jun 12 13:55:53 SinCity ppp[1129]: tun0: LCP: 1: LayerUp Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: bundle: Authenticate Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: 1: his = PAP, mine = none Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: Pap Output: myname ******** Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: Pap Input: SUCCESS () Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: 1: lcp -> cbcp Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: 1: cbcp -> lcp Jun 12 13:55:53 SinCity ppp[1129]: tun0: LCP: 1: LayerDown Jun 12 13:55:53 SinCity ppp[1129]: tun0: LCP: 1: SendTerminateReq(24) state = Opened Jun 12 13:55:53 SinCity ppp[1129]: tun0: LCP: 1: State change Opened --> Closing Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: 1: CBCP: Peer will dial back Jun 12 13:55:53 SinCity ppp[1129]: tun0: LCP: 1: RecvTerminateAck(24) state = Closing Jun 12 13:55:53 SinCity ppp[1129]: tun0: LCP: 1: LayerFinish Jun 12 13:55:53 SinCity ppp[1129]: tun0: LCP: 1: State change Closing --> Closed Jun 12 13:55:53 SinCity ppp[1129]: tun0: LCP: 1: State change Closed --> Initial Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: 1: Disconnected! Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: 1: lcp -> logout Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: 1: logout -> hangup Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: 1: Disconnected! I do receive a call from the remote end, but it's not known/answered by isdnd: 12.06.2000 13:53:55 CHD 00130 mb dialing out from nr_myself to nr_isp 12.06.2000 13:53:56 CHD 00130 mb outgoing call proceeding (ctl 0, ch 0) 12.06.2000 13:53:57 CHD 00130 mb outgoing call active (ctl 0, ch 0, rbch0) 12.06.2000 13:53:59 CHD 00130 mb outgoing call disconnected (local) 12.06.2000 13:53:59 CHD 00130 mb cause 0: normal call clearing (I4B) 12.06.2000 13:53:59 CHD 00130 mb charging: 1 units, 2 seconds 12.06.2000 13:53:59 CHD 00130 mb accounting: in 0, out 0 12.06.2000 13:54:02 CHD 00131 incoming call from nr_isp to nr_myself I'm wondering why the incoming call is being called "unknown", though I have entered the number in my isdnd.rc ?! I'm running FreeBSD 4 with isdnd 00.90.1. Does anyone have an idea why things won't work ? Thanks. kwaH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Jun 12 5:40:11 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 4E4C237B773 for ; Mon, 12 Jun 2000 05:39:58 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id NAA76438; Mon, 12 Jun 2000 13:39:53 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA02197; Mon, 12 Jun 2000 13:39:43 +0100 (BST) (envelope-from brian@Awfulhak.org) Message-Id: <200006121239.NAA02197@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Emre Cc: freebsd-isdn@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: Remote dialin fails with CBCP In-Reply-To: Message from Emre of "Mon, 12 Jun 2000 14:06:46 +0200." <3944D256.9E238756@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Jun 2000 13:39:43 +0100 From: Brian Somers Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ppp doesn't attempt to deal with the callback. You need to set up an independent configuration that will accept the incoming call and invoke ppp with the appropriate profile. The tricky thing about doing this is executing ppp with stdin as a readable *and* writable descriptor. FreeBSD's sh doesn't support <>, but bash does. > Hi, > > I'm having a couple of problems creating a profile for a dialin > where my end is being called back. > > I have two ISP's to connect, one 'normal', the other with CBCP. > Dialing my 'normal' ISP works great, but when I use a second dialout > profile > with CBCP the call coming back is not processed by I4b (as far as > I can say). > > The configuration is as follows: > > isdnd.rc: > > # Second Profile (Callback) > > entry > name = mb > usrdevicename = rbch > usrdeviceunit = 0 > isdncontroller = 0 > isdnchannel = -1 > local-phone-incoming = nr_myself > remote-phone-incoming = nr_isp > local-phone-dialout = nr_myself > remote-phone-dialout = nr_isp > remdial-handling = last > dialin-reaction = accept > dialout-type = calledback > b1protocol = hdlc > idletime-incoming = 240 > idletime-outgoing = 30 > ratetype = 0 > unitlength = 90 > unitlengthsrc = rate > dialretries = 3 > dialrandincr = on > recoverytime = 30 > usedown = off > downtries = 2 > downtime = 30 > calledbackwait = 10 > > ppp.conf: > > mb: > set authname myname > set authkey mypw > set phone nr_isp > set timeout 300 > set bandwidth 65536 > set mrru 1500 > set callback cbcp > set cbcp * > clone 1,2 > link deflink rm > link * set mode auto > set autoload 10 100 30 > > The PPP negotiation seems to work fine: > [...] > Jun 12 13:55:53 SinCity ppp[1129]: tun0: LCP: 1: LayerUp > Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: bundle: Authenticate > Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: 1: his = PAP, mine = > none > Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: Pap Output: myname > ******** > Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: Pap Input: SUCCESS () > Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: 1: lcp -> cbcp > Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: 1: cbcp -> lcp > Jun 12 13:55:53 SinCity ppp[1129]: tun0: LCP: 1: LayerDown > Jun 12 13:55:53 SinCity ppp[1129]: tun0: LCP: 1: SendTerminateReq(24) > state = Opened > Jun 12 13:55:53 SinCity ppp[1129]: tun0: LCP: 1: State change Opened --> > Closing > Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: 1: CBCP: Peer will dial > back > Jun 12 13:55:53 SinCity ppp[1129]: tun0: LCP: 1: RecvTerminateAck(24) > state = Closing > Jun 12 13:55:53 SinCity ppp[1129]: tun0: LCP: 1: LayerFinish > Jun 12 13:55:53 SinCity ppp[1129]: tun0: LCP: 1: State change Closing > --> Closed > Jun 12 13:55:53 SinCity ppp[1129]: tun0: LCP: 1: State change Closed --> > Initial > Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: 1: Disconnected! > Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: 1: lcp -> logout > Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: 1: logout -> hangup > Jun 12 13:55:53 SinCity ppp[1129]: tun0: Phase: 1: Disconnected! > > > I do receive a call from the remote end, but it's not known/answered by > isdnd: > > 12.06.2000 13:53:55 CHD 00130 mb dialing out from nr_myself to nr_isp > 12.06.2000 13:53:56 CHD 00130 mb outgoing call proceeding (ctl 0, ch 0) > 12.06.2000 13:53:57 CHD 00130 mb outgoing call active (ctl 0, ch 0, > rbch0) > 12.06.2000 13:53:59 CHD 00130 mb outgoing call disconnected (local) > 12.06.2000 13:53:59 CHD 00130 mb cause 0: normal call clearing (I4B) > 12.06.2000 13:53:59 CHD 00130 mb charging: 1 units, 2 seconds > 12.06.2000 13:53:59 CHD 00130 mb accounting: in 0, out 0 > 12.06.2000 13:54:02 CHD 00131 incoming call from nr_isp to > nr_myself > > I'm wondering why the incoming call is being called "unknown", though I > have > entered the number in my isdnd.rc ?! > > I'm running FreeBSD 4 with isdnd 00.90.1. > > Does anyone have an idea why things won't work ? > > Thanks. > > kwaH -- 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 Mon Jun 12 6: 0:33 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 899BB37BC3E for ; Mon, 12 Jun 2000 06:00:06 -0700 (PDT) (envelope-from pherman@at12.de) Received: from bagabeedaboo.security.at12.de (dial-195-14-251-105.netcologne.de [195.14.251.105]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id PAA19241; Mon, 12 Jun 2000 15:00:01 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.1/8.10.1) with ESMTP id e5CCxbx02004; Mon, 12 Jun 2000 14:59:37 +0200 (CEST) Date: Mon, 12 Jun 2000 14:59:37 +0200 (CEST) From: Paul Herman To: Brian Somers Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: only getting as far as "Ppp" with user ppp over raw B channel In-Reply-To: <200006121031.LAA01352@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 Hi Brian, > > [...Paul had problems with ppp hanging in authentification mode...] > > > ``Ppp'' means that authentication hasn't yet completed. This is > because you've got ``enable pap'' in your config - insisting that > your ISP authenticates themselves. > > Remove the ``enable pap'' and everything should work ok. Yup, that did it. I got tripped up on the enable vs. accept and disable vs. deny difference. I somehow just didn't connect the idea with something like DO vs. WILL and DON't vs. WON'T, like in telnet negotiation. Anyway, now I know, it makes perfect sense, and I'll never forget it again. I might be slow, but I only have to learn once. :) Thanks Brian! -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Jun 13 4: 5:26 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.squidge.com (ns0.squidge.com [195.10.252.4]) by hub.freebsd.org (Postfix) with ESMTP id 6E36537B9E5 for ; Tue, 13 Jun 2000 04:05:22 -0700 (PDT) (envelope-from si@mystery-machine.com) Received: from simonh ([193.133.98.226]) by mail.squidge.com (8.9.3/8.9.3) with SMTP id MAA91195 for ; Tue, 13 Jun 2000 12:12:51 +0100 (BST) (envelope-from si@mystery-machine.com) Message-ID: <02b801bfd527$58181f80$430110ac@billco.internal> Reply-To: "Simon Holliday" From: "Simon Holliday" To: Subject: Fw: PPP client/server Date: Tue, 13 Jun 2000 12:05:24 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org posted to freebsd-isp before I realised there was an ISDN list.... oops. > I have a situation where I want two machines to talk to each other over > ISDN. One box will have no other connections, and the other will be on a > network but won't be routing between ISDN and network. I want both boxes to > run PPP client and server so they can both dial each other and create a > two-machine subnet to throw files around when appropriate. > > Not having done anything with modems or ISDN on FreeBSD before, I've been > reading the handbook, but from the look of it, these documents appear a > little out of date. > > Can any of you point me to any documentation on the best way to set up the > above situation? > > Thanks, > > > Si. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Jun 13 4:30:14 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id F2D0137B7B0 for ; Tue, 13 Jun 2000 04:30:08 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id MAA64937; Tue, 13 Jun 2000 12:30:03 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id MAA42618; Tue, 13 Jun 2000 12:29:55 +0100 (BST) (envelope-from brian@Awfulhak.org) Message-Id: <200006131129.MAA42618@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Simon Holliday" Cc: freebsd-isdn@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: Fw: PPP client/server In-Reply-To: Message from "Simon Holliday" of "Tue, 13 Jun 2000 12:05:24 +0100." <02b801bfd527$58181f80$430110ac@billco.internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Jun 2000 11:29:54 +0000 From: Brian Somers Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > posted to freebsd-isp before I realised there was an ISDN list.... oops. Replied to on -isp before I realised you'd posted here :-D -- 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 Tue Jun 13 7:20:40 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from manatee.lf.net (manatee.LF.net [212.9.160.168]) by hub.freebsd.org (Postfix) with ESMTP id 5F5F437BE47 for ; Tue, 13 Jun 2000 07:20:37 -0700 (PDT) (envelope-from sc@manatee.lf.net) Received: by manatee.lf.net (Smail3.2.0.111/manatee.lf.net) via LF.net GmbH Internet Services for hub.FreeBSD.ORG id m131rYR-000OYOC; Tue, 13 Jun 2000 16:20:35 +0200 (CEST) Date: Tue, 13 Jun 2000 16:20:35 +0200 From: Sergio Campos To: freebsd-isdn@FreeBSD.ORG Subject: Questions Archive Message-ID: <20000613162034.I77691@manatee.LF.net> Reply-To: Sergio Campos Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, - I'm a regular reader of this list and I have a question: does it exit an archive of this list? - if yes .. does anybody has the web-site? - TNX -- Gruss / Best regards | LF.net GmbH | fon +49 711 90074-29 Sergio Campos | Vor dem Lauch 23 | fax +49 711 7289041 sc@LF.net | D-70567 Stuttgart | Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Jun 13 7:41:53 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from popmail.space.net (popmail.Space.Net [195.30.0.14]) by hub.freebsd.org (Postfix) with SMTP id 8391B37B603 for ; Tue, 13 Jun 2000 07:41:50 -0700 (PDT) (envelope-from stammeier@definion.com) Received: (qmail 26610 invoked from network); 13 Jun 2000 14:41:48 -0000 Received: from host-1277.i-dial.de (HELO reinsch.hpsd-intern.de) (193.149.53.215) by popmail.space.net with SMTP; 13 Jun 2000 14:41:48 -0000 Received: from goedel ([192.168.0.28]) by reinsch.hpsd-intern.de (8.9.3/8.9.3) with SMTP id RAA04233 for ; Tue, 13 Jun 2000 17:03:54 +0200 Message-ID: <009001bfd545$4427c520$1c00a8c0@hpsdintern.de> From: "Thomas Stammeier" To: References: <20000613162034.I77691@manatee.LF.net> Subject: Re: Questions Archive Date: Tue, 13 Jun 2000 16:40:06 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Sergio, I think you can find it at http://docs.freebsd.org/mail/current/freebsd-isdn.html Thomas > Hi, > > - I'm a regular reader of this list and I have a question: > does it exit an archive of this list? > - if yes .. does anybody has the web-site? > > - TNX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Jun 13 17:52:37 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 39FC337BE59 for ; Tue, 13 Jun 2000 17:52:34 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id CAA23769 for freebsd-isdn@FreeBSD.ORG; Wed, 14 Jun 2000 02:52:32 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id CAA28246 for ; Wed, 14 Jun 2000 02:51:13 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <01b801bfd59a$b4c5b940$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: Subject: reject Date: Wed, 14 Jun 2000 02:46:03 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I wanted somebody to be blocked from calling me on my regular isdn-phones. So I let isdn4bsd reject the calls from his number, but my phones rang anyway. Also, if somebody is calling, and I press reject on my isdn-phone (DeTeWe), this phone stops ringing, but the rest keeps ringing. So reject does really mean "This unit (TA, phone, "modem") will not "ring" anymore for this call, it doesn't mean "exchange, kick this caller out" Or what? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Jun 13 17:58: 0 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from alice.turbocat.de (gate.turbocat.de [212.41.163.6]) by hub.freebsd.org (Postfix) with ESMTP id BDF2637BE7D for ; Tue, 13 Jun 2000 17:57:56 -0700 (PDT) (envelope-from dave@turbocat.de) Received: from cat.turbocat.de (cat.turbocat.de [212.41.163.194]) by alice.turbocat.de (8.10.1/8.10.1/07072000/dw/1) with ESMTP id e5E0vrP16569; Wed, 14 Jun 2000 02:57:53 +0200 (CEST) Received: (from dave@localhost) by cat.turbocat.de (8.8.5/8.7.3) id CAA00284; Wed, 14 Jun 2000 02:57:51 +0200 (MET DST) Message-Id: <200006140057.CAA00284@cat.turbocat.de> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) In-Reply-To: <01b801bfd59a$b4c5b940$0e00a8c0@neland.dk> X-Nextstep-Mailer: Mail 4.0 (Enhance 2.0b4) Received: by NeXT.Mailer (1.148) From: David Wetzel Date: Wed, 14 Jun 2000 02:57:51 +0200 To: "Leif Neland" Subject: Re: reject Cc: References: <01b801bfd59a$b4c5b940$0e00a8c0@neland.dk> Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > From: "Leif Neland" what you want is a very fast answering machine :-) the code that decides if i4b should answer a call is not very clever but I had not time to enhance this jet. --- _ _ _(_)(_)_ 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 Jun 14 3:16:56 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F52.dip.t-dialin.net [62.155.143.82]) by hub.freebsd.org (Postfix) with ESMTP id ECF3837BC43 for ; Wed, 14 Jun 2000 03:16:52 -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 MAA37568; Wed, 14 Jun 2000 12:11:29 +0200 (CEST) Message-Id: <200006141011.MAA37568@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Simon Holliday" Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: Fw: PPP client/server Reply-To: Gary Jennejohn In-reply-to: Your message of "Tue, 13 Jun 2000 12:05:24 BST." <02b801bfd527$58181f80$430110ac@billco.internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Jun 2000 12:11:29 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Simon Holliday" writes: >posted to freebsd-isp before I realised there was an ISDN list.... oops. > > >> I have a situation where I want two machines to talk to each other over >> ISDN. One box will have no other connections, and the other will be on a >> network but won't be routing between ISDN and network. I want both boxes >to >> run PPP client and server so they can both dial each other and create a >> two-machine subnet to throw files around when appropriate. >> >> Not having done anything with modems or ISDN on FreeBSD before, I've been >> reading the handbook, but from the look of it, these documents appear a >> little out of date. >> >> Can any of you point me to any documentation on the best way to set up the >> above situation? >> AFAIK there's no way to directly connect 2 ISDN cards to one another. You always need an S0 bus in between. If you have a PBX with an S0 bus then you can just plug the ISDN cards into it, assign a number to each and set up isdnd.rc appropriately so the computers can call each other. With user-ppp on top of ISDN it should be simple. man ppp(8) and isdnd.rc(5). If you don't have a PBX then each time you connect you'll have to pay for the call, but if you're willing to do that then the mechanism will be the same. Of course, you may run out of numbers since each card has to have its own unique number. --- Gary Jennejohn / garyj@muc.de 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 Jun 14 13:30:50 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F28.dip.t-dialin.net [62.155.143.40]) by hub.freebsd.org (Postfix) with ESMTP id 1C0E137C267 for ; Wed, 14 Jun 2000 13:30:34 -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 WAA38231; Wed, 14 Jun 2000 22:25:51 +0200 (CEST) Message-Id: <200006142025.WAA38231@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: David Wetzel Cc: "Leif Neland" , freebsd-isdn@FreeBSD.ORG Subject: Re: reject Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 14 Jun 2000 02:57:51 +0200." <200006140057.CAA00284@cat.turbocat.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Jun 2000 22:25:50 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David Wetzel writes: >> From: "Leif Neland" > >what you want is a very fast answering machine :-) > >the code that decides if i4b should answer a call is not very clever but I >had not time to enhance this jet. > Wait a second. If you have 2 devices on an S0 bus responding to the same number then I would expect a race condition to result. It doesn't seem reasonable to me to expect isdnd to reject calls for other devices on the bus. In fact, I would suspect that it would violate some standard. IMHO that's a function which a PBX should carry out. --- Gary Jennejohn / garyj@muc.de 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 Jun 14 13:49:37 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from alice.turbocat.de (gate.turbocat.de [212.41.163.6]) by hub.freebsd.org (Postfix) with ESMTP id 37C7A37B664 for ; Wed, 14 Jun 2000 13:49:33 -0700 (PDT) (envelope-from dave@turbocat.de) Received: from cat.turbocat.de (cat.turbocat.de [212.41.163.194]) by alice.turbocat.de (8.10.1/8.10.1/07072000/dw/1) with ESMTP id e5EKnVP01693; Wed, 14 Jun 2000 22:49:31 +0200 (CEST) Received: (from dave@localhost) by cat.turbocat.de (8.8.5/8.7.3) id WAA00914; Wed, 14 Jun 2000 22:49:32 +0200 (MET DST) Message-Id: <200006142049.WAA00914@cat.turbocat.de> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) In-Reply-To: <200006142025.WAA38231@peedub.muc.de> X-Nextstep-Mailer: Mail 4.0 (Enhance 2.0b4) Received: by NeXT.Mailer (1.148) From: David Wetzel Date: Wed, 14 Jun 2000 22:49:31 +0200 To: Gary Jennejohn Subject: Re: reject Cc: "Leif Neland" , freebsd-isdn@FreeBSD.ORG References: <200006142025.WAA38231@peedub.muc.de> Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > From: Gary Jennejohn > Wait a second. If you have 2 devices on an S0 bus responding to the > same number then I would expect a race condition to result. It doesn't > seem reasonable to me to expect isdnd to reject calls for other devices > on the bus. In fact, I would suspect that it would violate some standard. > IMHO that's a function which a PBX should carry out. No. i4b/the anwering machine should answer the call and hang up. --- _ _ _(_)(_)_ 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 Jun 14 14:10:30 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F28.dip.t-dialin.net [62.155.143.40]) by hub.freebsd.org (Postfix) with ESMTP id 2C36337B537 for ; Wed, 14 Jun 2000 14:10:28 -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 XAA38649; Wed, 14 Jun 2000 23:05:48 +0200 (CEST) Message-Id: <200006142105.XAA38649@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: David Wetzel Cc: "Leif Neland" , freebsd-isdn@FreeBSD.ORG Subject: Re: reject Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 14 Jun 2000 22:49:38 +0200." <200006142049.WAA00914@cat.turbocat.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Jun 2000 23:05:48 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David Wetzel writes: >> From: Gary Jennejohn > >> Wait a second. If you have 2 devices on an S0 bus responding to the >> same number then I would expect a race condition to result. It doesn't >> seem reasonable to me to expect isdnd to reject calls for other devices >> on the bus. In fact, I would suspect that it would violate some standard. >> IMHO that's a function which a PBX should carry out. > >No. i4b/the anwering machine should answer the call and hang up. > Oh, the _answering machine_ handles it. Now I understand. But I had the impression from his mail that he wanted isdnd to reject calls for other devices on the S0 bus, which can't work AFAICT. --- Gary Jennejohn / garyj@muc.de 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 Jun 15 3:31:46 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 743AC37B520 for ; Thu, 15 Jun 2000 03:31:42 -0700 (PDT) (envelope-from pherman@at12.de) Received: from bagabeedaboo.security.at12.de (dial-195-14-251-40.netcologne.de [195.14.251.40]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id MAA08330 for ; Thu, 15 Jun 2000 12:31:35 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.1/8.10.1) with ESMTP id e5FATli00613 for ; Thu, 15 Jun 2000 12:29:47 +0200 (CEST) Date: Thu, 15 Jun 2000 11:49:21 +0200 (CEST) From: Paul Herman To: freebsd-isdn@freebsd.org Subject: i4b hangs during boot with ELSA Microlink 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 Hi, I have an ELSA Microlink PCI ISDN card, and i4b hangs when I boot. The card gets detected and shows: isic0: rev 0x01 int a irq 10 on pci0.11.0 isic0: IPAC PSB2115 Version 1.2 ...and the kernel continues to detect other devices. Later at the end (after npx0) before it is *supposed* to display i4b: ISDN call control device attached i4bctl: ISDN system control port attached i4brbch: 2 raw B channel access device(s) attached i4btrc: 1 ISDN trace device(s) attached ...it displays nothing, and locks up. I have DDB compiled in with debug kernel, but it locks up so hard, it won't even break with Ctl-Alt-Esc so sorry, no backtraces! SOLUTION: If I disconnect the ISDN cable during kernel boot, and then put it back when the system comes up into multiuser, i4b *does indeed* get attached and the card works beautifuly (that's how I sent this email) Card also works fine under Win2000 without these cable games so I think hardware can be ruled out. :( QUESTIONS: Is this a known problem? Am I the only one? What can I do to help? Does the card need to first be reset by i4b somehow? I'd love to hack around in the kernel, but without a backtrace or familiarity with i4b layer1 code, I don't know where to start. Tell me what I can do / where to start to debug this. Help! Without magical $5,000 robotic arm to disconnect and reconnect cable during boot, this is totally inadequate for a standalone server! ;-) SETUP: FreeBSD 3.4-RELEASE ELSA Microlink 1000 PCI ISDN Adapter i4b 0.83 with IPAC V1.2 patches posted on the list i4b 0.90 with IPAC V1.2 patches posted on the list, also no luck. P.S. I tried Fritz! AVM PCI and it works fine (i.e. don't need to play cable games.) Thanks, -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Jun 15 12:18:50 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id AC38137B553 for ; Thu, 15 Jun 2000 12:18:46 -0700 (PDT) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 15317 invoked by uid 0); 15 Jun 2000 19:18:45 -0000 Received: from p3e9d5123.dip.t-dialin.net (HELO speedy.gsinet) (62.157.81.35) by mail05.rzmi.gmx.net with SMTP; 15 Jun 2000 19:18:45 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id SAA03159 for freebsd-isdn@FreeBSD.ORG; Thu, 15 Jun 2000 18:00:29 +0200 Date: Thu, 15 Jun 2000 18:00:29 +0200 From: Gerhard Sittig To: freebsd-isdn@FreeBSD.ORG Subject: Re: reject Message-ID: <20000615180028.M9883@speedy.gsinet> Mail-Followup-To: freebsd-isdn@FreeBSD.ORG References: <200006142049.WAA00914@cat.turbocat.de> <200006142105.XAA38649@peedub.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200006142105.XAA38649@peedub.muc.de>; from garyj@peedub.muc.de on Wed, Jun 14, 2000 at 11:05:48PM +0200 Organization: System Defenestrators Inc. Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jun 14, 2000 at 23:05 +0200, Gary Jennejohn wrote: > David Wetzel writes: > >> From: Gary Jennejohn > > > >> Wait a second. If you have 2 devices on an S0 bus responding > >> to the same number then I would expect a race condition to > >> result. It doesn't seem reasonable to me to expect isdnd to > >> reject calls for other devices on the bus. In fact, I would > >> suspect that it would violate some standard. IMHO that's a > >> function which a PBX should carry out. > > > >No. i4b/the anwering machine should answer the call and hang > >up. Accepting the call with an AM and immediately hanging up is one solution. But regarding immediate _rejection_ this *is* possible (and we've been through that a few years ago in another project). AFAICT (I'm not an communications expert and might use the wrong terms, but you surely get the idea) an incoming call is just signalled to the internal bus(ses). *Every* device has the opportunity to - ignore the call ("not mine, I don't care") - accept the call ("I _could_ handle this" in the meaning of "I apply for getting this job"!) - reject the call ("not for me _and_for_nobody_else_ I can think of") There's a chance for multiple devices to accept the signalled call (not to get them, that's something the PBX will handle due to the packets' serialisation on the bus). And I consider this to be a feature. Think of signalling a voice call on many phones and have the user decide where to pick up the receiver. Or have a few remote control computers sit there and have them choose whether it's their working hour and whom they respond to. That's where they can share a MSN quite well. To summarize: There is a rejection message a device can emit speaking for *everyone* on the bus. It's just rarely used and might not be available at a userland command level. And it's very rare cases where this message is appropriate. > Oh, the _answering machine_ handles it. Now I understand. But I > had the impression from his mail that he wanted isdnd to reject > calls for other devices on the S0 bus, which can't work AFAICT. See above. We really suffered from this and it took quite some time to find out there's even such a feature and it's used in the software. Actually this tough rejection completely prevented the neighbour machines from getting any call (although they *saw* them). But this sounds like it absolutely is what's wanted here. (Mis)using the AM will accept the connection for a moment and lead to cost and a blocked B channel (i.e. data channel in contrast to the rejection completely handled in D channel messages). This should be considered -- unless one wants to "punish" the to be banned caller. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Jun 15 12:36:31 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 3BC8837B86F for ; Thu, 15 Jun 2000 12:36:16 -0700 (PDT) (envelope-from bart@ixori.demon.nl) Received: from smtp-relay by ixori.demon.nl (8.9.3/8.9.2) with ESMTP id VAA10619; Thu, 15 Jun 2000 21:39:23 +0200 (CEST) (envelope-from bart@ixori.demon.nl) Received: from network (intranet) by smtp-relay (Bart's intranet smtp server) Date: Thu, 15 Jun 2000 21:40:25 +0200 (CEST) From: Bart van Leeuwen To: Gerhard Sittig Cc: freebsd-isdn@freebsd.org Subject: Re: reject In-Reply-To: <20000615180028.M9883@speedy.gsinet> 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 Thu, 15 Jun 2000, Gerhard Sittig wrote: > On Wed, Jun 14, 2000 at 23:05 +0200, Gary Jennejohn wrote: > Accepting the call with an AM and immediately hanging up is one > solution. But regarding immediate _rejection_ this *is* possible > (and we've been through that a few years ago in another project). > > AFAICT (I'm not an communications expert and might use the wrong > terms, but you surely get the idea) an incoming call is just > signalled to the internal bus(ses). *Every* device has the > opportunity to > - ignore the call ("not mine, I don't care") > - accept the call ("I _could_ handle this" in the meaning of "I > apply for getting this job"!) > - reject the call ("not for me _and_for_nobody_else_ I can think > of") Hmm. with some experimentation I see the following: As long as any device says it cn handle the call (regardless of if it is actually going to handle it) then the pbx here will keep signalling the incomming call, even when another device rejects it. As long as noone ever responds to it, the pbx will signal the other side that the number does not exist (!!) This might be the particular, and as the past learned, often slightly non standard isdn environment used in the part of the Netherlands where I live... ;-) > > There's a chance for multiple devices to accept the signalled > call (not to get them, that's something the PBX will handle due > to the packets' serialisation on the bus). And I consider this > to be a feature. Think of signalling a voice call on many phones > and have the user decide where to pick up the receiver. Or have > a few remote control computers sit there and have them choose > whether it's their working hour and whom they respond to. That's > where they can share a MSN quite well. > > To summarize: There is a rejection message a device can emit > speaking for *everyone* on the bus. It's just rarely used and > might not be available at a userland command level. And it's > very rare cases where this message is appropriate. > > > Oh, the _answering machine_ handles it. Now I understand. But I > > had the impression from his mail that he wanted isdnd to reject > > calls for other devices on the S0 bus, which can't work AFAICT. > > See above. We really suffered from this and it took quite some > time to find out there's even such a feature and it's used in the > software. Actually this tough rejection completely prevented the > neighbour machines from getting any call (although they *saw* > them). But this sounds like it absolutely is what's wanted here. > > (Mis)using the AM will accept the connection for a moment and > lead to cost and a blocked B channel (i.e. data channel in > contrast to the rejection completely handled in D channel > messages). This should be considered -- unless one wants to > "punish" the to be banned caller. > Hmm. I dono about how this works where you live, but the caller pays regardless of this in my country. Ok, this may cause additional cost, but that is maybe 10% above the cost already caused by simply pickng up a phone and dialing the number. (yes, the KPN is insane for charging for this, and something should be done about it... but still, thats how it works right now here) Bart. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Jun 17 3: 0:14 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 8C05637B7F1 for ; Sat, 17 Jun 2000 03:00:06 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-195-14-251-182.netcologne.de [195.14.251.182]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id LAA02629 for ; Sat, 17 Jun 2000 11:59:58 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.1/8.10.1) with ESMTP id e5H9xoo00496 for ; Sat, 17 Jun 2000 11:59:50 +0200 (CEST) Date: Sat, 17 Jun 2000 11:59:49 +0200 (CEST) From: Paul Herman To: freebsd-isdn@FreeBSD.ORG Subject: Re: i4b hangs during boot with ELSA Microlink 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 Thu, 15 Jun 2000, Paul Herman wrote: > I have an ELSA Microlink PCI ISDN card, and i4b hangs when I boot. > The card gets detected and shows: It's me again. I wrote this a few days ago, but I got no answer. Is this even the right list? Is there another i4b specific list for hackers? Anyway, I've got some news. Maybe this will help track down the problem. After playing around with the code (printf() in the kernel is a great thing!) I noticed the following: when i4b locks up on me, it gets stuck in the for(;;) loop in isic_pci_intr_sc() in layer1/i4b_isic_pci.c here: else /* IPAC interrupt routine */ { register u_char ipac_irq_stat; for(;;) { [...snip!...] ...blah, blah, blah, picks up HSCX A/B and ISAC interrupts as long as there are any... [...snip!...] if(ipac_irq_stat & (IPAC_ISTA_ICD | IPAC_ISTA_EXD)) { /* ISAC interrupt */ isic_isac_irq(sc, ISAC_READ(I_ISTA)); } } } it loops forever in this for(;;) loop and calls isic_isac_irq() over and over and over with an ista value of 0x00 !!! Occasionally a ISAC_ISTA_RME (0x80) comes off the card, but that is normal, I guess. Is this perhaps a bug in ISAC_READ? I have no specs for this card (Elsa Microlink PCI), and I must say, am not at all an expert in these things. (All I know is that it doesn't hang if the ISDN cable is disconnected first :) Thanks, -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Jun 17 3:11:56 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from kens.com (kens.com [129.250.30.40]) by hub.freebsd.org (Postfix) with ESMTP id DFCB937B53C for ; Sat, 17 Jun 2000 03:11:45 -0700 (PDT) (envelope-from rsocha@kens.com) Received: (from rsocha@localhost) by kens.com (8.9.3/8.9.3) id GAA84362 for freebsd-isdn@FreeBSD.ORG; Sat, 17 Jun 2000 06:13:19 -0400 (EDT) (envelope-from rsocha) Date: Sat, 17 Jun 2000 06:13:19 -0400 From: "Robin S. Socha" To: freebsd-isdn@FreeBSD.ORG Subject: OpenBSD / i4l / AVM Fritz PCI or teles 16c? Message-ID: <20000617061319.A84247@kens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-Editor: Vim-506 http://www.vim.org/ Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear all, I'm in the process of switching from DeadRat Linux (well, I've been using this setup for 4 years through various upgrades, and it isn't bad, but...) to OpenBSD, having taken a FreeBSD detour (in the course of which I've "accidentally" moved our company servers to FreeBSD, hehe...). From what I've read in the docs, deja.com and the ML archives, it is next to impossible to make the combination mentioned in the subject run. Since I know OpenBSD only a little, hardly any C, don't develop kernels often or hack them, I wonder if Hellmuth Michaelis' statement from http://www.geocrawler.com/archives/3/161/2000/3/0/3475464/ is still valid or if there is a chance to get i4b to work with OpenBSD 2.7. Thanks a lot in advance, Robin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Jun 17 7:14:34 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from disorder.ruhr.de (p3E9BF1B0.dip0.t-ipconnect.de [62.155.241.176]) by hub.freebsd.org (Postfix) with ESMTP id F118237BA46 for ; Sat, 17 Jun 2000 07:14:31 -0700 (PDT) (envelope-from joerg@disorder.ruhr.de) Received: by disorder.ruhr.de (Postfix, from userid 1003) id BFA6D155061; Sat, 17 Jun 2000 13:36:24 +0200 (CEST) Date: Sat, 17 Jun 2000 13:36:24 +0200 From: Joerg Bornschein To: freebsd-isdn@freebsd.org Subject: OpenBSD 2.7 and i4b Message-ID: <20000617133624.A718@disorder.ruhr.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi" X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable =20 Hi, =20 Those willing to setup a OpenBSD router may find these patches useful: http://www.zilium.de/joerg =20 Everything seems stable -- im running a 64/128kbit line for about 2 weeks without problems. =20 I did not do any serious development -- just made sure evrything applies cleanly. =20 =20 thanks for listening =20 =20 Joerg =20 --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE5S2K4RIjNbP9C21kRAfCVAKCZ5X3S8jkYisHq+LkLngQGC6avKQCfWKxh fOMBDJ8TzMOkPoPd9U5PlDI= =cFVi -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Jun 17 12:18: 4 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 1C22437B592 for ; Sat, 17 Jun 2000 12:18:01 -0700 (PDT) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 9153 invoked by uid 0); 17 Jun 2000 19:17:59 -0000 Received: from p3e9e7981.dip.t-dialin.net (HELO speedy.gsinet) (62.158.121.129) by mail.gmx.net with SMTP; 17 Jun 2000 19:17:59 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id PAA07269 for freebsd-isdn@FreeBSD.ORG; Sat, 17 Jun 2000 15:56:09 +0200 Date: Sat, 17 Jun 2000 15:56:09 +0200 From: Gerhard Sittig To: freebsd-isdn@FreeBSD.ORG Subject: Re: i4b hangs during boot with ELSA Microlink Message-ID: <20000617155609.X9883@speedy.gsinet> Mail-Followup-To: freebsd-isdn@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from pherman@frenchfries.net on Sat, Jun 17, 2000 at 11:59:49AM +0200 Organization: System Defenestrators Inc. Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jun 17, 2000 at 11:59 +0200, Paul Herman wrote: > > On Thu, 15 Jun 2000, Paul Herman wrote: > > > I have an ELSA Microlink PCI ISDN card, and i4b hangs when I > > boot. The card gets detected and shows: > > It's me again. I wrote this a few days ago, but I got no > answer. Is this even the right list? Is there another i4b > specific list for hackers? Anyway, I've got some news. Maybe > this will help track down the problem. Well, I didn't want to throw in the L-word (some people around here seem to react badly on it, but I hope I'm wrong on this). The Linux driver (HiSax) had a similar problem in a former version -- it hung at load time when the Elsa card was plugged into an active bus. Do I remember right that you saw the very same symptom? Maybe it's helpful to browse the Changelog of the Linux driver from, say 2.2.10 up to now (2.2.16). virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Jun 17 15:35: 3 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F28.dip.t-dialin.net [62.155.143.40]) by hub.freebsd.org (Postfix) with ESMTP id ADDD737B50F for ; Sat, 17 Jun 2000 15:34: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 AAA00643; Sun, 18 Jun 2000 00:29:21 +0200 (CEST) Message-Id: <200006172229.AAA00643@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Robin S. Socha" Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: OpenBSD / i4l / AVM Fritz PCI or teles 16c? Reply-To: Gary Jennejohn In-reply-to: Your message of "Sat, 17 Jun 2000 06:13:19 EDT." <20000617061319.A84247@kens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Jun 2000 00:29:21 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Robin S. Socha" writes: >Dear all, > >I'm in the process of switching from DeadRat Linux (well, I've been >using this setup for 4 years through various upgrades, and it isn't bad, >but...) to OpenBSD, having taken a FreeBSD detour (in the course of >which I've "accidentally" moved our company servers to FreeBSD, >hehe...). > >>From what I've read in the docs, deja.com and the ML archives, it is >next to impossible to make the combination mentioned in the subject run. >Since I know OpenBSD only a little, hardly any C, don't develop kernels often >or hack them, I wonder if Hellmuth Michaelis' statement from >http://www.geocrawler.com/archives/3/161/2000/3/0/3475464/ is still >valid or if there is a chance to get i4b to work with OpenBSD 2.7. > This has nothing to do with your question, but why OpenBSD ? After all the time I spent getting you up and running on FreeBSD you want to switch to OpenBSD ?!?! Traitor. :) Anyway, did you see this ? From: Joerg Bornschein Subject: OpenBSD 2.7 and i4b Hi, Those willing to setup a OpenBSD router may find these patches useful: http://www.zilium.de/joerg Everything seems stable -- im running a 64/128kbit line for about 2 weeks without problems. I did not do any serious development -- just made sure evrything applies cleanly. thanks for listening Joerg --- Gary Jennejohn / garyj@muc.de gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message