From owner-freebsd-stable Mon Jan 14 11:23:15 2002 Delivered-To: freebsd-stable@freebsd.org Received: from newtrinity.default-network.net (newtrinity.default-network.net [62.159.128.162]) by hub.freebsd.org (Postfix) with ESMTP id D6B9937B402 for ; Mon, 14 Jan 2002 11:23:08 -0800 (PST) Received: (from corex@localhost) by newtrinity.default-network.net (8.11.3/8.11.3/DEFAULT-NETWORK.NET) id g0EJ31N04784; Mon, 14 Jan 2002 20:03:01 +0100 (CET) (envelope-from corex) Date: Mon, 14 Jan 2002 20:03:01 +0100 From: marius@alchemy.franken.de To: Martin Kraemer Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ISDN4BSD not ready for prime time in 4.5-RC ? Message-ID: <20020114200301.A99739@newtrinity.default-network.net> References: <20020111164810.A568@deejai2.mch.fsc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020111164810.A568@deejai2.mch.fsc.net>; from Martin.Kraemer@Fujitsu-Siemens.com on Fri, Jan 11, 2002 at 04:48:10PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > In 4.5-RC (more exact, since ~October), I cannot succeed in using > ISDN any more. Yes I changed the cable, and I asked a friend to use > ISDN on the same NTBA (from Win2k), to the same provider I use; > he had no problems. > did he use the same s0/pri socket as you did? i saw something similar recently, causing nearly the same system messages, it turned out to be a broken NTBA; the two internal sockets worked but we did get no connection but the error messages when using an additional s0/pri socket connected to the NTBA (yes, it was/is terminated correctly), although an isdn-phone worked on the later... exchanging the NTBA solved the problem just a guess... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message