From owner-freebsd-isdn@FreeBSD.ORG Tue Jan 27 08:44:45 2004 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D31616A4CE for ; Tue, 27 Jan 2004 08:44:45 -0800 (PST) Received: from jane.inty.net (jane.inty.net [195.224.93.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEEDB43D41 for ; Tue, 27 Jan 2004 08:44:12 -0800 (PST) (envelope-from andy@inty.com) x-previous-hop: 212.50.178.178 Received: from inty.hq.inty.net (inty-untrusted-aztec-west.inty.net [212.50.178.178]) by jane.inty.net (8.12.9/8.12.9) with ESMTP id i0RGhZBq030863 for ; Tue, 27 Jan 2004 16:43:36 GMT Received: from inty.com ([10.0.1.19]) (authenticated bits=0) by inty.hq.inty.net (8.12.1/8.12.1) with ESMTP id i0RGhY6I047055 for ; Tue, 27 Jan 2004 16:43:34 GMT Message-ID: <40169536.4010201@inty.com> Date: Tue, 27 Jan 2004 16:43:34 +0000 From: Andy Gale User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20031209 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-isdn@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Sender-IP: 10.0.1.19 X-INT-DeliveryDone: i0RGhY6I047055 X-suppress-rcpt-virus-notify: yes X-Virus-Checked: 59527 X-Skip-Virus-Check: yes Subject: AVM ISDN Fritz 2.0 PCI card X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2004 16:44:45 -0000 Hello all, Previously we've been using the internal, passive AMV Fritz PCI 1.0 card. This works perfectly with my system (4.7-RELEASE, i4b and user land PPP) and I've had no problems. I am now forced to upgrade to the version 2 PCI card. According to the kernel config, the card is supported so this should not of presented a problem. I recompiled my 4.7-RELEASE kernel, including the ipfi2 (in quotes) device and although initially the ISDN connection was established, my box soon locked up and stopped responding to key presses - requiring a reboot. I then built a 4.9-RELEASE box from scratch, recompiled the kernel to include i4b, ipfi2 etc, setup PPP, isdnd and attempted to dial up with my ISDN line. Once again the box locked up, failed to respond to key presses and required a reboot. Is anyone using the version 2.0 Fritz ISDN card with any reliability? If so could you offer my some pointers as to how to get a setup that will work reliably with this card? Best Regards, Andy -- Andy Gale Developer, intY Ltd, Bristol, UK e: andy@inty.com w: www.inty.com t: +441454640500 The information contained in this e-mail message and any files transmitted with it is confidential and may be legally privileged. It is intended only for the addressee and others authorised to receive it. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient you are advised that you have received the e-mail in error and that any disclosure, copying, distribution or action taken in reliance on the contents of the e-mail and its attachments is strictly prohibited and may be unlawful. Please advise the sender immediately if you are not the intended recipient. intY has scanned this email for all known viruses (www.inty.com) From owner-freebsd-isdn@FreeBSD.ORG Tue Jan 27 12:49:56 2004 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4629516A4F7 for ; Tue, 27 Jan 2004 12:49:56 -0800 (PST) Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD12243D7B for ; Tue, 27 Jan 2004 12:49:20 -0800 (PST) (envelope-from garyj@jennejohn.org) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout1.freenet.de with asmtp (Exim 4.30) id 1Ala7Z-0005ud-VI; Tue, 27 Jan 2004 21:47:41 +0100 Received: from gef79.g.pppool.de ([80.185.239.121] helo=peedub.jennejohn.org) by mx3.freenet.de with esmtp (TLSv1:AES256-SHA:256) (Exim 4.30 #3) id 1Ala7Z-0002KO-71; Tue, 27 Jan 2004 21:47:41 +0100 Received: from peedub.jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.12.10/8.11.6) with ESMTP id i0RKldFw006234; Tue, 27 Jan 2004 21:47:39 +0100 (CET) (envelope-from garyj@peedub.jennejohn.org) Message-Id: <200401272047.i0RKldFw006234@peedub.jennejohn.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: Andy Gale In-reply-to: Your message of "Tue, 27 Jan 2004 16:43:34 GMT." <40169536.4010201@inty.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Jan 2004 21:47:39 +0100 From: Gary Jennejohn cc: freebsd-isdn@freebsd.org Subject: Re: AVM ISDN Fritz 2.0 PCI card X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gary Jennejohn List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2004 20:49:56 -0000 Andy Gale writes: > Is anyone using the version 2.0 Fritz ISDN card with any reliability? If > so could you offer my some pointers as to how to get a setup that will > work reliably with this card? > I've always used it under whatever may be -current at any given time and have NEVER experienced lockups. I'm just installing a 4.9 box and will give it a try with that. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de From owner-freebsd-isdn@FreeBSD.ORG Wed Jan 28 03:41:26 2004 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EADAE16A4CE for ; Wed, 28 Jan 2004 03:41:26 -0800 (PST) Received: from smtp-out2.xs4all.nl (smtp-out2.xs4all.nl [194.109.24.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBED843D31 for ; Wed, 28 Jan 2004 03:41:24 -0800 (PST) (envelope-from fjaspers@xs4all.nl) Received: from xs1.xs4all.nl (xs1.xs4all.nl [194.109.21.2]) by smtp-out2.xs4all.nl (8.12.10/8.12.10) with ESMTP id i0SBfKO8040616 for ; Wed, 28 Jan 2004 12:41:20 +0100 (CET) Received: from xs1.xs4all.nl (fjaspers@localhost.xs4all.nl [127.0.0.1]) by xs1.xs4all.nl (8.12.10/8.12.9) with ESMTP id i0SBfKBT070575 for ; Wed, 28 Jan 2004 12:41:20 +0100 (CET) (envelope-from fjaspers@xs4all.nl) Received: (from fjaspers@localhost) by xs1.xs4all.nl (8.12.10/8.12.9/Submit) id i0SBfKTW070574 for freebsd-isdn@freebsd.org; Wed, 28 Jan 2004 12:41:20 +0100 (CET) (envelope-from fjaspers) Date: Wed, 28 Jan 2004 12:41:20 +0100 From: fjaspers@xs4all.nl To: freebsd-isdn@freebsd.org Message-ID: <20040128114120.GA70001@xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: RE: AVM ISDN Fritz 2.0 PCI card X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2004 11:41:27 -0000 Hi I'm using a AVM Fritz!Card PCI Version 2 on my FreeBSD 5.0 RELEASE box. It's more or less stable. sometimes when connecting it gives messges like: i4b-L1 ifpi2_isacsx_exir_hdlr: EXIRQ Rx Frame Overflow i4b-L1 ifpi2_isacsx_irq: unit 0: Data Overrun error i4b-L2 i4b_T202_timeout: unit 0, N202 = 3 I just have to connect again in that case. I experienced some lockups too, however that was when running my machine under linux. Here is my isdnd.conf it is setup for working with userland ppp, and for receiving and answering incoming. Maybe this helps you. Do u have any log messages? Frans. (fjaspers@xs4all.nl) isdnd.conf: #============================================================================== # SYSTEM section: isdnd global configuration parameters #============================================================================== system monitor-allowed = no # global switch: monitor on/off monitor = "/var/run/isdn-monitor" monitor-access = fullcmd # all commands. ratesfile = /etc/isdn/isdnd.rates # name & location of rates file regexpr = "[Cc]all from .* to Frans Jaspers" regprog = isdntel.notify aliasing = on # Aliasing. aliasfile = /etc/isdn/isdntel.alias # Alias file. # prefixes voor incoming calls. add-prefix = on prefix-national = "0" prefix-international = "+31" beepconnect = on extcallattr = on isdntime = on rtprio = 25 #=========================================================================== # controller section #=========================================================================== controller protocol = dss1 #============================================================================== # entry section. Userland ppp device 0. #============================================================================== entry name = userppp0 usrdevicename = rbch usrdeviceunit = 0 isdncontroller = 0 isdnchannel = 1 local-phone-dialout = 1234567 # This *MUST* be your local number remote-phone-dialout = 1234567 # ppp(8) will override this local-phone-incoming = 1234567 # this is my number remote-phone-incoming = * # i call this remote number remdial-handling = first dialin-reaction = ignore dialout-type = normal b1protocol = hdlc idletime-incoming = 900 # Should be larger than ppp's timeout idletime-outgoing = 900 # Should be larger than ppp's timeout unitlength = 0 unitlengthsrc = conf dialretries = 1 dialrandincr = on recoverytime = 1 # Should be smaller than ppp's redial usedown = off downtries = 2 downtime = 30 #============================================================================== # entry section. Userland ppp device 1. #============================================================================== entry name = userppp1 usrdevicename = rbch usrdeviceunit = 1 isdncontroller = 0 isdnchannel = 2 local-phone-dialout = 1234567 # This *MUST* be your local number remote-phone-dialout = 1234567 # ppp(8) will override this local-phone-incoming = 1234567 # this is my number remote-phone-incoming = * # i call this remote number remdial-handling = first dialin-reaction = ignore dialout-type = normal b1protocol = hdlc idletime-incoming = 900 # Should be larger than ppp's timeout idletime-outgoing = 900 # Should be larger than ppp's timeout unitlength = 0 unitlengthsrc = conf dialretries = 1 dialrandincr = on recoverytime = 1 # Should be smaller than ppp's redial usedown = off downtries = 2 downtime = 30 #============================================================================== # entry section. Telephony. #============================================================================== entry name = i4btel # name in logfiles. usrdevicename = tel # the device the data traffic # should be routed to. usrdeviceunit = 0 # unit number isdncontroller = 0 # the ISDN controller number to be used. isdnchannel = -1 # channel(1/2) to use or 0 or -1 for any direction = inout # in, out, inout local-phone-incoming = 1234567 # this is my number remote-phone-incoming = * # i call this remote number local-phone-dialout = 1234567 # My number. remote-phone-dialout = * # I call this number. dialin-reaction = answer # what happenes if someone dials in: answerprog = isdntel.sh # Program when someone dials in. b1protocol = raw # type of protocol on the B-channel. alert = 15 idletime-incoming = 5 ------------------------------------------------------------------------------- End of isdnd.conf From owner-freebsd-isdn@FreeBSD.ORG Thu Jan 29 13:11:09 2004 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3823F16A4CE for ; Thu, 29 Jan 2004 13:11:09 -0800 (PST) Received: from mailout01.sul.t-online.com (mailout01.sul.t-online.com [194.25.134.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id F333D43D46 for ; Thu, 29 Jan 2004 13:11:06 -0800 (PST) (envelope-from Holger.Eitzenberger@t-online.de) Received: from fwd04.aul.t-online.de by mailout01.sul.t-online.com with smtp id 1AmJRK-0007PC-00; Thu, 29 Jan 2004 22:11:06 +0100 Received: from kruemel.eitzenberger.name (b7JWcMZTrePC2KkWNFiSvBt4QXERhHLo-yNxW7fMX--59psUdBVZoi@[217.0.132.90]) by fwd04.sul.t-online.com with esmtp id 1AmJR0-13TZ1E0; Thu, 29 Jan 2004 22:10:46 +0100 Received: from [192.168.10.10] (helo=jonathan.eitzenberger.name) by kruemel.eitzenberger.name with esmtp (Exim 4.12) id 1AmJPR-0000CD-00 for freebsd-isdn@freebsd.org; Thu, 29 Jan 2004 22:09:09 +0100 Received: from holger by jonathan.eitzenberger.name with local (Exim 3.35 #1 (Debian)) id 1AmJPZ-00050d-00 for ; Thu, 29 Jan 2004 22:09:17 +0100 Date: Thu, 29 Jan 2004 22:09:17 +0100 To: FreeBSD ISDN Message-ID: <20040129220917.A19246@eitzenberger.name> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i From: Holger.Eitzenberger@t-online.de (Holger Eitzenberger) X-Seen: false X-ID: b7JWcMZTrePC2KkWNFiSvBt4QXERhHLo-yNxW7fMX--59psUdBVZoi Subject: Q: Fritz!Card PCI 2.1 X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2004 21:11:09 -0000 Hi, I have a problem when running the above mentioned card. My logs are full of msgs like 21:00:11 kruemel /kernel: ifpi2_recover 0 21:00:13 kruemel /kernel: i4b-L1 ifpi2_ph_data_req: still in state F3! 21:00:13 kruemel /kernel: isp0: pap failure 21:00:15 kruemel /kernel: i4b-L1 timer3_expired: state = F4 Awaiting Signal 21:00:15 kruemel /kernel: ifpi2_recover 0 21:00:15 kruemel /kernel: i4b-L2 i4b_mph_status_ind: unit 0, cannot access S0 bus! 21:00:15 kruemel /kernel: i4b-L3 i4b_mdl_status_ind: STI_NOL1ACC: unit 0 no outgoing access to S0 21:00:20 kruemel /kernel: i4b: unit 0, assigned TEI = 77 = 0x4d 21:00:21 kruemel /kernel: isp0: pap failure My hardware is VIA Epia 5000 Mini-ITX with two PCI-Cards sharing one PCI-Slot (Fritz!Card PCI 2.1, Netgear MA311 WLAN) through a 2x Riser-Card, so my situation is somewhat "special" because these two cards share one interrupt. Though the problem arises also if only the Fritz!Card is plugged. An ELSA QuickStep 1000pro works nicely. Thanks in advance. /Holger -- ++ GnuPG Key -> http://www.t-online.de/~holger.eitzenberger ++ From owner-freebsd-isdn@FreeBSD.ORG Tue Feb 3 06:01:57 2004 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 672AF16A4CE for ; Tue, 3 Feb 2004 06:01:57 -0800 (PST) Received: from smtp-out6.xs4all.nl (smtp-out6.xs4all.nl [194.109.24.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04B3943D39 for ; Tue, 3 Feb 2004 06:01:56 -0800 (PST) (envelope-from jorrith@buyways.nl) Received: from waldorf.buyways.nl (gwbw.xs4all.nl [213.84.100.200]) by smtp-out6.xs4all.nl (8.12.10/8.12.10) with SMTP id i13E1siU074056 for ; Tue, 3 Feb 2004 15:01:54 +0100 (CET) Date: Tue, 3 Feb 2004 15:01:53 +0100 From: Jorrith Schaap To: freebsd-isdn@freebsd.org Message-Id: <20040203150153.59acdc55@waldorf.buyways.nl> Organization: Buyways X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: PCMCIA ISDN card question X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2004 14:01:57 -0000 Hi, I'm looking for a PCMCIA ISDN card that's supported by FreeBSD. So far, the AVM Fritz!Card PCMCIA looks most promising. Is this card fully supported? Are there any other cards that are known to work? Anyone has experience with PCMCIA ISDN on FreeBSD? Thanks, Jorrith Schaap -- jorrith@buyways.nl http://www.buyways.nl From owner-freebsd-isdn@FreeBSD.ORG Fri Feb 6 07:42:38 2004 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A0AD16A4CE for ; Fri, 6 Feb 2004 07:42:38 -0800 (PST) Received: from bhenrich.dov.nq.net (bhenrich.dov.nq.net [210.11.152.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3624B43D53 for ; Fri, 6 Feb 2004 07:42:35 -0800 (PST) (envelope-from bhenrich@deschutes.no-ip.com) Received: from IBM74E4B9692C8 (unknown [192.168.1.253]) by bhenrich.dov.nq.net (Postfix) with ESMTP id 739B3110EDC4 for ; Sat, 7 Feb 2004 01:42:33 +1000 (EST) From: "Brett Henrich" To: Date: Sat, 7 Feb 2004 01:42:33 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcPsx9Zj7zNDOtkKTZeKZIqkkuSd6w== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-Id: <20040206154233.739B3110EDC4@bhenrich.dov.nq.net> Subject: Bandwidth on (manual) demand with i4b X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2004 15:42:38 -0000 Hello, I'm a Linux user looking at migrating my ISDN router over to BSD after finally having enough with the problems with ISDN4Linux (hard lockups, MPPP issues, the fact it doesn't work with Linux 2.6 among others) and there is one question I can't seem to find an answer to: If I have a 128Kbps Synchronous PPP ISDN connection, is it possible to manually dial and hangup the "slave" channel to switch between a 64 and a 128Kbps link. The reason being is that during the day (this is a home ISDN connection) I need the second channel open to receive phone calls. At night, I can bring up both channels and run the connection at 128Kbps. I have a cron job at the moment that dials the slave channel at 10pm and brings it down at 7am. Under Linux (ISDN4Linux) this is performed by issuing the command "isdnctrl dial ippp1" (dial second channel) and "isdnctrl hangup ippp1" respectively. This function is critical if I'm going to switch over to BSD for Linux. I'm in Australia too. ISDN (DoV) is untimed but there is a per-call charge (18 cents) so I want basically to run 64K all the time, bursting to 128K at night. Thanks for your time, and yes, I'm a newbie. Brett.