From owner-freebsd-isdn Sun Feb 21 1:32:10 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (Postfix) with ESMTP id 1D3AF10E6E for ; Sun, 21 Feb 1999 01:32:05 -0800 (PST) (envelope-from ernie!bert.kts.org!hm@ppp.net) Received: from casparc.ppp.net (casparc2.ppp.net [194.64.12.42]) by mail.ppp.net (8.8.8/8.8.8) with SMTP id KAA14886; Sun, 21 Feb 1999 10:32:03 +0100 Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m10EVF5-002ZjZC; Sun, 21 Feb 99 10:32 MET Received: from bert.kts.org([194.55.156.2]) (2191 bytes) by ernie.kts.org via sendmail with P:smtp/R:smart_host/T:uux (sender: ) id for ; Sun, 21 Feb 1999 09:50:09 +0100 (CET) (Smail-3.2.0.103 1998-Oct-9 #3 built 1998-Dec-9) Received: from localhost (1742 bytes) by bert.kts.org via sendmail with P:stdio/R:smart_host/T:smtp (sender: ) (ident using unix) id for ; Sun, 21 Feb 1999 09:50:17 +0100 (CET) (Smail-3.2.0.103 1998-Oct-9 #4 built 1998-Dec-26) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: error message in the logs - 00.70 In-Reply-To: <199902202126.WAA26244@gilberto.physik.RWTH-Aachen.DE> from Christoph Kukulies at "Feb 20, 1999 10:26:48 pm" To: kuku@gilberto.physik.RWTH-Aachen.DE (Christoph Kukulies) Date: Sun, 21 Feb 1999 09:50:17 +0100 (CET) Cc: freebsd-isdn@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christoph Kukulies wrote: > Feb 20 22:27:06 bgate /kernel: i4b-L2-i4b_rxd_ack: ((N(R)-1)=124) != (UA=125) !!! Somehow a packet got lost (wherever) and this is an indication that the protocol recovery mechanisms are doing their work. BTW, recently there was a question what i4b-L1-isic_hscx_waitxfw: HSCX wait for XFW timeout! means, and i forgot to answer that one. This is an indication that an IRQ from the HSCX (the chip handling the B-channel) got lost - most likely because someone else blocked interrupts for a long time. It does no harm in case an error correcting protocol (such as TCP) runs on the B-channel. I have a machine here which used to have SCSI disks and at that time i never saw that message. Now some time ago i could not resist to buy a dirt cheap IDE disk and since then i see those messages once or twice a week even after tuning the wdc driver with some flags values. I'll stay away from IDE now. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 21 3:22:40 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from rvc1.informatik.ba-stuttgart.de (rvc1.informatik.ba-stuttgart.de [141.31.112.22]) by hub.freebsd.org (Postfix) with ESMTP id 0220511715 for ; Sun, 21 Feb 1999 03:22:33 -0800 (PST) (envelope-from helbig@rvc1.informatik.ba-stuttgart.de) Received: (from helbig@localhost) by rvc1.informatik.ba-stuttgart.de (8.8.8/8.8.8) id MAA00243 for freebsd-isdn@FreeBSD.ORG; Sun, 21 Feb 1999 12:22:36 +0100 (CET) Date: Sun, 21 Feb 1999 12:22:36 +0100 (CET) From: Wolfgang Helbig Message-Id: <199902211122.MAA00243@rvc1.informatik.ba-stuttgart.de> To: freebsd-isdn@FreeBSD.ORG Subject: HSCX wait for XFW timeout (was Re: error message in the logs - 00.70) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > BTW, recently there was a question what > > i4b-L1-isic_hscx_waitxfw: HSCX wait for XFW timeout! > > means, and i forgot to answer that one. This is an indication that an IRQ > from the HSCX (the chip handling the B-channel) got lost - most likely Hmm. This timeout occurs while waiting for the transmit buffer to accept another 32 bytes to transmit. I don't see how a lost interrupt can cause this timeout. (Even if you have IDE drives) To better understand whats going on, I suggest to enable the L1_H_XFRERR (HSCX data xfer errors) debug flag: isdndebug -l1 -s0x1a29 Wolfgang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 21 8: 2: 7 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (Postfix) with ESMTP id 20F6510E61 for ; Sun, 21 Feb 1999 08:02:04 -0800 (PST) (envelope-from ernie!bert.kts.org!hm@ppp.net) Received: from casparc.ppp.net (casparc2.ppp.net [194.64.12.42]) by mail.ppp.net (8.8.8/8.8.8) with SMTP id RAA17858; Sun, 21 Feb 1999 17:02:02 +0100 Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m10EbKT-002ZjcC; Sun, 21 Feb 99 17:02 MET Received: from bert.kts.org([194.55.156.2]) (2329 bytes) by ernie.kts.org via sendmail with P:smtp/R:smart_host/T:uux (sender: ) id for ; Sun, 21 Feb 1999 16:58:04 +0100 (CET) (Smail-3.2.0.103 1998-Oct-9 #3 built 1998-Dec-9) Received: from localhost (1880 bytes) by bert.kts.org via sendmail with P:stdio/R:smart_host/T:smtp (sender: ) (ident using unix) id for ; Sun, 21 Feb 1999 16:58:10 +0100 (CET) (Smail-3.2.0.103 1998-Oct-9 #4 built 1998-Dec-26) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: HSCX wait for XFW timeout (was Re: error message in the logs - 00.70) In-Reply-To: <199902211122.MAA00243@rvc1.informatik.ba-stuttgart.de> from Wolfgang Helbig at "Feb 21, 1999 12:22:36 pm" To: helbig@Informatik.BA-Stuttgart.DE (Wolfgang Helbig) Date: Sun, 21 Feb 1999 16:58:10 +0100 (CET) Cc: freebsd-isdn@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wolfgang Helbig wrote: > > i4b-L1-isic_hscx_waitxfw: HSCX wait for XFW timeout! > > > > means, and i forgot to answer that one. This is an indication that an IRQ > > from the HSCX (the chip handling the B-channel) got lost - most likely > > Hmm. This timeout occurs while waiting for the transmit buffer > to accept another 32 bytes to transmit. I don't see how a lost interrupt > can cause this timeout. (Even if you have IDE drives) My theory is, that while waiting, someone else blocks the interrupt for that long time, that another HSCX transaction starts immediately (by chance out of the blocked interrupt in which another HSCX interrupt occurs) which clears implicitely the flag we are waiting for (perhaps i should introduce a flag signalling that we are in such a wait status, and see what happenes and who might clear it, but i'm too lazy to do that right now ....). When the system in question was changed from SCSI to IDE (nothing else did change) those messages started to occur, with SCSI i never saw a single such message. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Feb 22 13:25: 0 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from dominik.saargate.de (domi.saargate.de [193.158.76.59]) by hub.freebsd.org (Postfix) with ESMTP id 2B7C211588 for ; Mon, 22 Feb 1999 13:24:35 -0800 (PST) (envelope-from domi@saargate.de) Received: from localhost (localhost [127.0.0.1]) by dominik.saargate.de (8.8.8/8.8.7) with ESMTP id WAA08424 for ; Mon, 22 Feb 1999 22:24:24 +0100 (CET) (envelope-from domi@saargate.de) Date: Mon, 22 Feb 1999 22:24:24 +0100 (CET) From: Dominik Brettnacher To: freebsd-isdn@freebsd.org Subject: connectprog Parameters 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 I see some parameters that my "connectprog" script is given by isdnd. Can somebody explain what they mean? Where is that documented? -- Dominik To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 23 2: 1:19 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (Postfix) with ESMTP id 743391102E for ; Tue, 23 Feb 1999 02:01:03 -0800 (PST) (envelope-from stefan.bethke@hanse.de) Received: from d225.promo.de (d225.Promo.DE [194.45.188.225]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id LAA04777 for ; Tue, 23 Feb 1999 11:01:01 +0100 (CET) Date: Tue, 23 Feb 1999 11:01:03 +0100 From: Stefan Bethke To: freebsd-isdn@freebsd.org Subject: Patch: sppp fails to assign address to remote Message-ID: <119878.3128756463@d225.promo.de> Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry Demo (MacOS) [1.4.2b2, s/n Evaluation] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="==========00136745==========" Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --==========00136745========== Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline When dialling into i4b from a Mac or Windows machine (haven't tried = another i4b yet), something goes wrong when the remote requests an IP address (conf-req 0.0.0.0). Everything works fine with debug set on the interface; when I turn off debug, sppp seems to conf-nak the request with address 0.0.0.0 instead of the interface address. The problem seemingly is a misplaced brace in if_spppsubr.c around line 2705 in sppp_ipcp_RCR(). The following patch should eliminate the problem, and should make dial-in from Windows and Mac work.. Cheers, Stefan -- M=FChlendamm 12 | Voice +49-40-256848, +49-177-3504009 D-22089 Hamburg | e-mail: stefan.bethke@hanse.de Germany | stb@freebsd.org --==========00136745========== Content-Type: text/plain; charset=us-ascii; name="sppp-patch.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="sppp-patch.txt"; size=623 *** if_spppsubr.c.orig Tue Dec 1 21:20:21 1998 --- if_spppsubr.c Tue Feb 23 10:55:28 1999 *************** *** 2701,2712 **** else addlog("%s [not agreed] ", sppp_dotted_quad(desiredaddr)); - - p[2] = hisaddr >> 24; - p[3] = hisaddr >> 16; - p[4] = hisaddr >> 8; - p[5] = hisaddr; } break; } } --- 2701,2712 ---- else addlog("%s [not agreed] ", sppp_dotted_quad(desiredaddr)); } + + p[2] = hisaddr >> 24; + p[3] = hisaddr >> 16; + p[4] = hisaddr >> 8; + p[5] = hisaddr; break; } } --==========00136745==========-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 23 7: 9:51 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 2DF06110E1 for ; Tue, 23 Feb 1999 07:09:07 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id QAA25923; Tue, 23 Feb 1999 16:08:55 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Stefan Bethke Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: Patch: sppp fails to assign address to remote In-reply-to: Your message of "Tue, 23 Feb 1999 11:01:03 +0100." <119878.3128756463@d225.promo.de> Date: Tue, 23 Feb 1999 16:08:54 +0100 Message-ID: <25921.919782534@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Committed thanks! -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Feb 23 15: 4:18 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from linteuto.teuto.de (linteuto.teuto.de [194.77.23.26]) by hub.freebsd.org (Postfix) with ESMTP id 454C010FF5 for ; Tue, 23 Feb 1999 15:04:11 -0800 (PST) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (root@rumolt.teuto.de [212.8.203.81]) by linteuto.teuto.de (8.8.7/8.8.7) with ESMTP id AAA07862; Wed, 24 Feb 1999 00:04:07 +0100 Received: (from martin@localhost) by rumolt.teuto.de (8.8.8/8.8.7) id AAA07171; Wed, 24 Feb 1999 00:03:56 +0100 (MET) From: Martin Husemann Message-Id: <199902232303.AAA07171@rumolt.teuto.de> Subject: Re: connectprog Parameters To: domi@saargate.de (Dominik Brettnacher) Date: Wed, 24 Feb 1999 00:03:56 +0100 (MET) Cc: freebsd-isdn@FreeBSD.ORG In-Reply-To: from "Dominik Brettnacher" at Feb 22, 99 10:24:24 pm Organization: Crusaders Catering Services Inc. ;-) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I see some parameters that my "connectprog" script is given by isdnd. Can > somebody explain what they mean? Where is that documented? For the later I'll have to pass - though I think I added a comment to some manpages when I wrote that code ;-) Anyway: both connect and disconnect prog get the following parameters: -d (device) -f (flag) [ -a (addr) ] where device name of device, e.g. "isp0" flag "up" if connection just got up, or "down" if interface changed to down state addr (optional, only if it can be figured by isdnd) the address that got assigned to the interface as a dotted-quad ip address The "-a (addr)" parameter may be replaced by others for different protocols later. You can look up the details in isdnd/exec.c, function exec_connect_prog. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Feb 24 13:26: 0 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from linteuto.teuto.de (linteuto.teuto.de [194.77.23.26]) by hub.freebsd.org (Postfix) with ESMTP id B43D911579 for ; Wed, 24 Feb 1999 13:23:40 -0800 (PST) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (root@rumolt.teuto.de [212.8.203.81]) by linteuto.teuto.de (8.8.7/8.8.7) with ESMTP id WAA30505 for ; Wed, 24 Feb 1999 22:15:52 +0100 Received: (from martin@localhost) by rumolt.teuto.de (8.8.8/8.8.7) id WAA01926 for freebsd-isdn@FreeBSD.ORG; Wed, 24 Feb 1999 22:15:58 +0100 (MET) From: Martin Husemann Message-Id: <199902242115.WAA01926@rumolt.teuto.de> Subject: Problems with PAP authentication To: freebsd-isdn@FreeBSD.ORG Date: Wed, 24 Feb 1999 22:15:53 +0100 (MET) Organization: Crusaders Catering Services Inc. ;-) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We had a big problem with one router connecting to t-online. Every now and then the authentication started to fail, so we got an ISDN connection, but where rejected by the remote site. We dialed again and where rejected again. This happened rappidly for a long time. My boss nearly killed me when he got the bill... I don't know what the problem is, every time I watch that system, everything is fine, and t-online accepts the PAP authentication. Anyway, the big problem is (IMHO) a big design flaw in isdnd: everything works on the ISDN layer, so the retry-count/put interface down stuff doesn't catch this. With PPP connections we should count a connection attempt to be successful only if the connection got up (which the daemon knows since the last release, due to the 'interface up' message used to trigger the ip-up script). I was in a hurry and didn't want to look that deep into the problem, so I made the change attached below. Due to local policies at that site this is an ideal solution for our problem: every time the PAP authentication failes the interface is configured down and only reactivated "manualy" - which in this case is an hourly job looking for mails. Your mileage may vary, and of course we should realy fix the underlying PAP problem as well as change isdnd as outlined above... Martin *** if_spppsubr.c.orig Wed Feb 24 11:27:41 1999 --- if_spppsubr.c Wed Feb 24 11:32:53 1999 *************** *** 3557,3569 **** if (len > 5 && name_len) { addlog(": "); sppp_print_string((char*)(h+1), name_len); } addlog("\n"); ! } else ! log(LOG_INFO, SPP_FMT "pap failure\n", SPP_ARGS(ifp)); /* await LCP shutdown by authenticator */ break; default: /* Unknown PAP packet type -- ignore. */ --- 3557,3571 ---- if (len > 5 && name_len) { addlog(": "); sppp_print_string((char*)(h+1), name_len); } addlog("\n"); ! } else { ! log(LOG_DEBUG, SPP_FMT "pap failure, setting if down\n", SPP_ARGS(ifp)); + ifp->if_flags &= ~IFF_UP; + } /* await LCP shutdown by authenticator */ break; default: /* Unknown PAP packet type -- ignore. */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Feb 24 13:29:58 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from yoda.pi.musin.de (yoda.pi.musin.de [194.246.250.12]) by hub.freebsd.org (Postfix) with ESMTP id 8962C1157C for ; Wed, 24 Feb 1999 13:28:48 -0800 (PST) (envelope-from sec@yoda.pi.musin.de) Received: (from sec@localhost) by yoda.pi.musin.de (8.9.2/8.9.1) id QAA03574 for freebsd-isdn@FreeBSD.ORG; Wed, 24 Feb 1999 16:12:46 +0100 (CET) (envelope-from sec) Date: Wed, 24 Feb 1999 16:12:46 +0100 From: Stefan `Sec` Zehl To: freebsd-isdn@FreeBSD.ORG Subject: dial on demand & hangup Message-ID: <19990224161245.A97495@yoda.pi.musin.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Kai.Grossjohann@CS.Uni-Dortmund.DE on Thu, Feb 11, 1999 at 12:33:55PM +0100 I-love-doing-this: really X-URL: http://sec.42.org/ Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I just upgraded our test-isdn box from 2.2-STABLE & bisdntest-3 to 3.1-STABLE and i4b. I must say that I'm happy to see how easy everything got. It was really easy to set up (compared to bisdn). A big thank you to everybody who made i4b what it is now. One small problem (which we already had in bisdn) still remains. I use syncppp via the isp0 device. If I use dial on demand (ifconfig isp0 link1). It dials at the sign of the first packet, like it should. However it doesn't hangup, which I think is because the remote end 'lcp-ping's us every now and then. isp0 ifconfig'd with debug says: isp0: lcp input(opened): isp0: lcp output every 20 seconds or so. Is there a way to make automatic hangup work (easily) with i4b? CU, Sec -- Komme wieder To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Feb 24 14:53:42 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id ACF4411287 for ; Wed, 24 Feb 1999 14:53:24 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id XAA30802 for ; Wed, 24 Feb 1999 23:53:00 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: freebsd-isdn@FreeBSD.org Subject: Re: Problems with PAP authentication In-reply-to: Your message of "Wed, 24 Feb 1999 22:15:53 +0100." <199902242115.WAA01926@rumolt.teuto.de> Date: Wed, 24 Feb 1999 23:53:00 +0100 Message-ID: <30800.919896780@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The sppp implementation is seriously broken in many corners. I have been trying to architect something which would allow us to use the "userland ppp" as controller for both leased lines & ISDN PPP lines, without having to pull the packets out of the kernel and stick them back in again. So far it is only a rough draft. If anybody wants to lend a hand to this, please get in touch with me. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Feb 24 21:39: 5 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 29EE71504C for ; Wed, 24 Feb 1999 21:39:00 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id VAA26244; Wed, 24 Feb 1999 21:34:38 -0800 (PST) From: Archie Cobbs Message-Id: <199902250534.VAA26244@bubba.whistle.com> Subject: Re: Problems with PAP authentication In-Reply-To: <30800.919896780@critter.freebsd.dk> from Poul-Henning Kamp at "Feb 24, 99 11:53:00 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Wed, 24 Feb 1999 21:34:38 -0800 (PST) Cc: freebsd-isdn@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Poul-Henning Kamp writes: > The sppp implementation is seriously broken in many corners. I have > been trying to architect something which would allow us to use the > "userland ppp" as controller for both leased lines & ISDN PPP lines, > without having to pull the packets out of the kernel and stick them > back in again. > > So far it is only a rough draft. > > If anybody wants to lend a hand to this, please get in touch with me. What about netgraph? :-) New release of mpd coming soon (I'll give you a pre-release copy if you want).. still uses /dev/tun though. The next step is to use a netgraph interface node instead. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 25 13:39: 2 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (Postfix) with ESMTP id ED8FB14DA2 for ; Thu, 25 Feb 1999 13:38:58 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id WAA17677; Thu, 25 Feb 1999 22:04:55 +0100 (CET) Message-Id: <199902252104.WAA17677@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: Problems with PAP authentication Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 24 Feb 1999 23:53:00 +0100." <30800.919896780@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Feb 1999 22:04:55 +0100 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Poul-Henning Kamp writes: > >The sppp implementation is seriously broken in many corners. I have >been trying to architect something which would allow us to use the >"userland ppp" as controller for both leased lines & ISDN PPP lines, >without having to pull the packets out of the kernel and stick them >back in again. > >So far it is only a rough draft. > >If anybody wants to lend a hand to this, please get in touch with me. > Eivind Ecklund has been working on something like this for a looooong time now. He'd be a good contact. I'd also be willing to lend a hand. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 25 14: 5:32 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (Postfix) with ESMTP id 6C28E14E11 for ; Thu, 25 Feb 1999 14:05:12 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id WAA17745; Thu, 25 Feb 1999 22:42:38 +0100 (CET) Message-Id: <199902252142.WAA17745@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: Stefan `Sec` Zehl Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: dial on demand & hangup Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 24 Feb 1999 16:12:46 +0100." <19990224161245.A97495@yoda.pi.musin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Feb 1999 22:42:38 +0100 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Stefan `Sec` Zehl writes: >Hi, > >I just upgraded our test-isdn box from 2.2-STABLE & bisdntest-3 to >3.1-STABLE and i4b. I must say that I'm happy to see how easy everything >got. It was really easy to set up (compared to bisdn). A big thank you >to everybody who made i4b what it is now. > >One small problem (which we already had in bisdn) still remains. > >I use syncppp via the isp0 device. If I use dial on demand (ifconfig >isp0 link1). It dials at the sign of the first packet, like it should. >However it doesn't hangup, which I think is because the remote end >'lcp-ping's us every now and then. > >isp0 ifconfig'd with debug says: > >isp0: lcp input(opened): >isp0: lcp output > >every 20 seconds or so. > >Is there a way to make automatic hangup work (easily) with i4b? > Not as long as there is traffic being exchanged. That will continously reset the timer in the kernel so that the idle hangup timeout will never be triggered. The timer is (indirectly) set in i4b_bchan.c and i4b_hscx.c by calling the bch_activity routine. This actually points at routines in i4b_ipr.c, i4b_isppp.c, i4b_rbch.c or i4b_tel.c. The respective routines basically set the last_active_time timer to the current time. The last_active_time timer is the heart of the idle timeout routine. The timer is updated at such a low level that there is no easy way of circumventing it. ANY traffic on the B-channel, incoming or outgoing, resets the timer. Well, there is 1 one exception, but it does not apply to isppp (or ipr or tel). --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Feb 26 3:24:36 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id DCBCB14F29 for ; Fri, 26 Feb 1999 03:24:13 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id MAA22447; Fri, 26 Feb 1999 12:23:59 +0100 (MET) (envelope-from kuku) Message-ID: <19990226122358.A22442@gil.physik.rwth-aachen.de> Date: Fri, 26 Feb 1999 12:23:58 +0100 From: Christoph Kukulies To: freebsd-isdn@freebsd.org Subject: [crypt1@ba.blitz.net: Re: Init Strings For ISDN] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can anyone help this guy? I don't know about cfos and that stuff. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de ----- Forwarded message from harrell ----- Received: from hermes.blitz.net (hermes.blitz.net [195.30.20.18]) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) with ESMTP id MAA22396 for ; Fri, 26 Feb 1999 12:11:47 +0100 (MET) (envelope-from crypt1@ba.blitz.net) Received: from harrell.ba.blitz.net (harrell.ba.blitz.net [195.30.20.71]) by hermes.blitz.net (8.8.5/8.7.3) with SMTP id MAA23770 for ; Fri, 26 Feb 1999 12:11:29 +0100 Message-ID: <003201be6170$57e66160$47141ec3@harrell.ba.blitz.net> Reply-To: "harrell" From: "harrell" To: "Christoph Kukulies" Subject: Re: Init Strings For ISDN Date: Fri, 26 Feb 1999 12:10:01 +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.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Here's my Question (Rephrased): Do you know any initializations strings that I could use for my Fritz Card. I am using cfos (com port emulation) for the ISDN card. My problem is I do not know how to tell the BBS (Based Bulletin Board Service) that's ready to go online, which MSN to answer. this is don through the init string. the msn or telephone number has to be placed somewhere in the string and I don't know where. I hope you or someone out there in cyberspace can help. I am Stuck Thanks For Listening Again :--) THE CRYPT KEEPER crypt1@ba.blitz.net ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Feb 27 13:39:21 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from eh.est.is (eh.est.is [194.144.208.34]) by hub.freebsd.org (Postfix) with ESMTP id D8D8715160 for ; Sat, 27 Feb 1999 13:39:17 -0800 (PST) (envelope-from totii@est.is) Received: from gateway.toti.est.is (toti.est.is [194.144.208.13]) by eh.est.is (8.8.8/8.8.8) with ESMTP id VAA05984 for ; Sat, 27 Feb 1999 21:39:04 GMT (envelope-from totii@est.is) Received: from asus (asus.toti.est.is [192.168.255.2]) by gateway.toti.est.is (8.9.2/8.9.1) with ESMTP id VAA34145 for ; Sat, 27 Feb 1999 21:38:58 GMT (envelope-from totii@est.is) Message-ID: <36D8D654.DC06FD98@est.is> Date: Sat, 27 Feb 1999 21:38:28 -0800 From: Thordur Ivarsson Reply-To: thivars@est.is X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: "freebsd-isdn@FreeBSD.ORG" Subject: Authenticate with passwd file? X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is it possible to use passwd file as password database as in kernel ppp or even with radius or ??? Thivars To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message