From owner-freebsd-isdn Sat May 8 7:12: 0 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 D00631563C for ; Sat, 8 May 1999 07:11:47 -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 QAA33284 for ; Sat, 8 May 1999 16:10:55 +0200 (CEST) Message-Id: <199905081410.QAA33284@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-isdn@freebsd.org Subject: Re: irritating messages in all ttyv's Reply-To: Gary Jennejohn In-reply-to: Your message of "Sat, 08 May 1999 13:12:03 +0200." <4.1.19990508130110.0095d990@pop.roberts.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 May 1999 16:10:55 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Luke Roberts writes: >Hi, > >I've had ib4 0.71 running on our FreeBSD ISDN gateway Machine running for >about a week now and I've finally found some time to do the finishing touches. > >First of all I run isdnd with it's own virtual console ttyv4 and I must say >the interface is exacly the way I like it. Great! Unfortunatly though I >still get a lot of messages in the other virtual consoles when the line >goes up and down. These messages are from the kernel(?) like: >May 8 12:59:09 dilis /kernel: i4b-L1-timer4_expired: state = F3 Deactivated >May 8 12:59:09 dilis /kernel: i4b-L1-timer4_expired: state = F3 Deactivated > >1. Why does it tell me this twice? because you're logged in as root and the messages go to all vty's where root is located as well as to the console. >2. How can I get rid of these messages? (pain in the you know what when >you're vi-ing a script and all of a sudden you cant see what you're editing >because of the overlying new text from i4b ) > turn off debugging using isdndebug. >Further I also have the same problem as Wilco does. (ISDN connection to >provider is opened as soon as isdnd runs. > >If I specify: > >ifconfig isp0 0.0.0.0 0.0.0.1 link1 up >ifconfig isp0 down > >Then I CAN'T connect to our provider at all. > >I run all the isdn commands from a simple script that is run last when >booting the machine. > of course not, when the interface is down. Since you config the interfaces late, as I do, there's probably something else happening, such as DNS or mails in the spool directory. The only time I get dialouts on reboot is when I've left a mail lying around. --- 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