From owner-freebsd-questions Fri Sep 6 08:22:09 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA00573 for questions-outgoing; Fri, 6 Sep 1996 08:22:09 -0700 (PDT) Received: from recruiter.on.ca (recruiter.on.ca [198.53.146.49]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA00566 for ; Fri, 6 Sep 1996 08:22:07 -0700 (PDT) Received: (from vam@localhost) by recruiter.on.ca (8.6.12/8.6.12) id LAA00334; Fri, 6 Sep 1996 11:21:17 -0400 Date: Fri, 6 Sep 1996 11:21:17 -0400 (EDT) From: Vic Metcalfe To: questions@freebsd.org Subject: Firewall disables inetd? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks to Hal I've got the firewall working great here. My only remaining problem seems to be inetd. When I boot with the firewall option enabled in the kernel (no logging or accounting), inetd does not work until it receives a SIGHUP. The behaviour is the same whether I run ipfw during startup or not. Immediately after booting and establishing a connection with my ISP, I try to telnet myself, from myself and get "Connection refused". If I then send a SIGHUP to it, which causes it to re-read its configuration, it works fine. Changing rc to run inetd -l doesn't create a log that I can find anywhere. Nothing to the /var/log/messages file anyway. I can't figure out a way to run it with the -d switch from rc, and if I run in interactively it works. In the worst case I'll write a program to detect if it is working or not and SIGHUP it if it isn't going, and run that in a cron job, but if anyone has any better ideas, I'd love to year from you. Thanks again, Vic.