From owner-freebsd-isdn Sun Nov 26 1:10:42 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by hub.freebsd.org (Postfix) with ESMTP id 181D837B4CF for ; Sun, 26 Nov 2000 01:10:40 -0800 (PST) Received: from fwd01.sul.t-online.com by mailout06.sul.t-online.com with smtp id 13zxpW-0005ET-00; Sun, 26 Nov 2000 10:10:38 +0100 Received: from night-porter.duskware.de (520038743430-0001@[62.155.250.99]) by fmrl01.sul.t-online.com with esmtp id 13zxpL-0K2v3oC; Sun, 26 Nov 2000 10:10:27 +0100 Received: (from martin@localhost) by night-porter.duskware.de (8.11.1/8.11.0) id eAQ9AMX00502; Sun, 26 Nov 2000 10:10:22 +0100 (MET) From: Martin Husemann Message-Id: <200011260910.eAQ9AMX00502@night-porter.duskware.de> Subject: Re: No connection with isdnmonitor In-Reply-To: "from Stefan Walter at Nov 25, 2000 03:48:47 pm" To: Stefan Walter Date: Sun, 26 Nov 2000 10:10:22 +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 > Well, yes: it doesn't work, either. ;) I did try it, but the > socket is not created by isdnd. Additionally - although I'm not > quite a newbie to UNIX systems any more -, I know next to nothing about > sockets; just enough to make sure it doesn't work, either. Please try this: shut down isdnd, start it again manually. Then look at the place where it should have created its socket (i.e. /var/run/isdn-monitor). If it's there, then probably your isdnd is started too early at boot time and the socket is removed by /var/run cleanup later. You could also see this from netstat: it would list the socket, even if its not in the filesystem. > netstat says there's nothing listening on port 451 at any of my IPs. I > tried 127.0.0.1 as well as the IP of my NIC, plus the local domain > socket. That's why I was asking, everything seems well-configured... So, either you don't have montior support (or TCP/IP montior support) compiled into your isdnd (check for I4B_EXTERNAL_MONITOR and I4B_NOTCPIP_MONITOR on the cc command line when compiling isdnd), or your isdnd should have loged all socket relevant errors when starting up. Or: something in your config file is wrong (or a bug in the parser reads it wrong) and therefore isdnd doesn't even try create a monitor socket. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message