From owner-freebsd-isdn Mon Feb 15 08:35:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27232 for freebsd-isdn-outgoing; Mon, 15 Feb 1999 08:35:52 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from mmadb.no ([195.41.82.90]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA27227 for ; Mon, 15 Feb 1999 08:35:49 -0800 (PST) (envelope-from digitech@mmadb.no) Date: Mon, 15 Feb 1999 17:31:51 +0100 Message-Id: <199902151731.AA395968716@mmadb.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: "Jon Lech Johansen" Reply-To: To: hm@hcs.de CC: freebsd-isdn@FreeBSD.ORG Subject: Re: Asuscom isdn card :( X-Mailer: Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I don't think the driver is working correctly with the asuscom card, because: a) I can't dial my isp (this is probably just my fault somehow, maybe) b) lots of error msgs going through syslogd I get this during bootup: i4b-L1-isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow and here are some other errors from /var/log/messages, which appear every now and then: Feb 15 17:10:08 router /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error Feb 15 17:10:08 router /kernel: i4b-L1-isic_isac_irq: unit 0: Receive Aborted error Feb 15 17:10:09 router /kernel: i4b-L1-timer4_expired: state = F3 Deactivated but what I find really really strange, is that when isdntrace reports all activeties correctly, and isdnd (in fullscreen mode) reports incoming calls (which isdntrace also does), you'd expect that the driver was working correctly, right. At least, I would. I've also been trying to connect to my isp (without luck): spppcontrol isp0 myauthproto=pap myauthname=username myauthsecret=pwd hisauthproto=none Command executes without errors :) ifconfig isp0 inet 0.0.0.0 0.0.0.1 link1 debug Command executes with error: 'ifconfig: ioctl (SIOCAIFADDR): File exists Here's the output from 'ifconfig -a': ==================================================== ...removed.... isp0: flags=2815 mtu 1500 inet 0.0.0.0 --> 0.0.0.1 netmask 0xff000000 ...removed.... ====================================================== route add default 0.0.0.1 executes correctly-> add net default: gateway 0.0.0.1 I should be online now, shouldn't I ? Well, I'm not :( When I switch over to isdnd (fullscreen mode on one of the ttys) there's nothing on the top that indicates any outgoing calls (isdn controller channel state). Any suggestions? - Jon rc.isdn ************************************************ LDIR=/usr/local/bin out_dev=/dev/ttyv3 out_typ=pcvt25h debug_level=0x1f9 isdn_trace=YES trace_file=/var/tmp/isdn.trace trace_opts="-i" echo '---------- enter /etc/rc.isdn ----------------------' # start the isdn daemon if [ -x $LDIR/isdnd ] then echo 'isdn4bsd: starting the ISDN management daemon ...' $LDIR/isdnd -d $debug_level -dn -f -r $out_dev -t $out_typ else echo 'isdn4bsd: ERROR, could not find $LDIR/isdnd!' exit 1 fi if [ -x $LDIR/isdntrace -a X${isdn_trace} = X"YES" ] then echo 'isdn4bsd: starting ISDN protocol tracing ...' nohup $LDIR/isdntrace $trace_opts -f $trace_file >/dev/null 2>&1 & fi echo '---------- exit /etc/rc.isdn -----------------------' ************************************************ isdnd.rc ************************************************ system acctall = on acctfile = /var/log/isdnd.acct useacctfile = yes rtprio = 25 entry name = tele2 usrdevicename = isp usrdeviceunit = 0 isdncontroller = 0 isdnchannel = -1 local-phone-incoming = xxxxxxxx remote-phone-incoming = xxxxxxxx local-phone-dialout = xxxxxxxx remote-phone-dialout = xxxxxxxx remdial-handling = first dialin-reaction = accept dialout-type = normal b1protocol = hdlc idletime-incoming = 240 idletime-outgoing = 30 ratetype = 0 unitlength = 90 unitlengthsrc = rate dialretries = 3 dialrandincr = on recoverytime = 25 usedown = off downtries = 2 downtime = 30 ************************************************ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message