From owner-freebsd-isdn Fri Nov 24 13: 8:15 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mailout01.sul.t-online.com (mailout01.sul.t-online.com [194.25.134.80]) by hub.freebsd.org (Postfix) with ESMTP id 1B91937B4CF for ; Fri, 24 Nov 2000 13:08:08 -0800 (PST) Received: from fwd04.sul.t-online.com by mailout01.sul.t-online.com with smtp id 13zQ4g-0007zw-01; Fri, 24 Nov 2000 22:08:02 +0100 Received: from night-porter.duskware.de (520038743430-0001@[62.158.126.218]) by fmrl04.sul.t-online.com with esmtp id 13zQ4a-1m8MT2C; Fri, 24 Nov 2000 22:07:56 +0100 Received: (from martin@localhost) by night-porter.duskware.de (8.11.1/8.11.0) id eAOL7ed05571; Fri, 24 Nov 2000 22:07:40 +0100 (MET) From: Martin Husemann Message-Id: <200011242107.eAOL7ed05571@night-porter.duskware.de> Subject: Re: No connection with isdnmonitor In-Reply-To: "from Stefan Walter at Nov 24, 2000 07:44:48 pm" To: Stefan Walter Date: Fri, 24 Nov 2000 22:07:40 +0100 (MET) Cc: freebsd-isdn@freebsd.org X-Mailer: ELM [version 2.4ME+ PL78 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Sender: (null).520038743430-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Try netstat -a to determine if your guess is correct. > It was indeed correct. However, I will do as Hellmuth said and upgrade. Is there a special reason you don't use the local domain socket (i.e. doing "isdnmonitor -l /var/run/isdn-monitor")? Does netstat show the configured port being listened on at all? Maybe it's just not listening on 127.0.0.1:451, but instead your "real" IP (this depends on how "localhost" is resolved on your system, assuming you put that into your config file; you might try configuring with dotted-quad IP numbers instead of names) Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message