From owner-freebsd-questions Tue Jul 13 13:15:15 1999 Delivered-To: freebsd-questions@freebsd.org Received: from snake.supranet.net (snake.supranet.net [205.164.160.19]) by hub.freebsd.org (Postfix) with ESMTP id 19B0314FF2 for ; Tue, 13 Jul 1999 13:15:09 -0700 (PDT) (envelope-from john@arnie.jfive.com) Received: from snake.supranet.net (snake.supranet.net [205.164.160.19]) by snake.supranet.net (8.8.8/8.8.8) with SMTP id PAA29416 for ; Tue, 13 Jul 1999 15:24:52 -0500 (CDT) (envelope-from john@arnie.jfive.com) Date: Tue, 13 Jul 1999 15:24:51 -0500 (CDT) From: John Heyer X-Sender: john@snake.supranet.net To: freebsd-questions@freebsd.org Subject: Problems with TCP Wrappers in 3.2 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having some troubles with TCP wrappers in 3.2, and was wondering if there are any known bugs/patches, etc. My hosts.allow file looks like - popper : ALL Then in hosts.deny - ALL : ALL EXCEPT ournetwork/mask : twist /bin/echo "acess to %d not allowed" Everything works fine - with the exception of pop3 which is wide open, all other connections are allowed/denied by the IP address range I've specified. The problem is that after a few day of uptime, TCP wrappers seems to "break" suddenly. In /var/log/messages, I see things like Jul 13 14:44:55 horse inetd[25034]: twist dialup.somewherelse to /bin/echo Note that %d is null, and the dialup user who should have access to the popper is denied. I run "kill -9 `cat /var/run/inetd.pid'; inetd" and everything's back to normal and working fine. We have a similar setup on our web server, which lets ftpd open since we use an ftpaccess file for security instead. I've observed the problem on another 3.2 machine was well. Anybody seen this where %d ends up being null? -- "Your illogical approach ... does have its advantages." -- Spock, after being Checkmated by Kirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message